From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/3] alsa-lib - improve surround 2.1 support
Date: Fri, 21 Feb 2014 16:50:59 +0100 [thread overview]
Message-ID: <s5htxbstqfw.wl%tiwai@suse.de> (raw)
In-Reply-To: <1392996262-27970-1-git-send-email-david.henningsson@canonical.com>
At Fri, 21 Feb 2014 16:24:19 +0100,
David Henningsson wrote:
>
> So, in order to support 2.1 surround on both 4-channels (e g FL FR LFE LFE,
> on internal subwoofer) and 6-channels (e g FL FR RL RR C LFE, on desktops
> with 5.1 out), I needed to make the route plugin more chmap aware.
>
> This also included allowing a new syntax for the ttable, which I think is
> quite nice. The new syntax also falls back to ALSAs standard chmap in case
> the hardware does not support it.
The idea looks great, a nice improvement.
Spotted a few trivial things I posted individually, but in general
it's in a good shape.
thanks,
Takashi
>
> David Henningsson (3):
> route: Allow chmap syntax for slave channels in ttable
> route: Select slave chmap based on ttable information
> conf: Allow 2.1 surround to use different number of channels
>
> src/conf/pcm/surround21.conf | 7 +-
> src/pcm/pcm_route.c | 304 ++++++++++++++++++++++++++++++++++++++-----
> 2 files changed, 271 insertions(+), 40 deletions(-)
>
> --
> 1.9.0
>
prev parent reply other threads:[~2014-02-21 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 15:24 [PATCH 0/3] alsa-lib - improve surround 2.1 support David Henningsson
2014-02-21 15:24 ` [PATCH 1/3] route: Allow chmap syntax for slave channels in ttable David Henningsson
2014-02-21 15:42 ` Takashi Iwai
2014-02-21 15:24 ` [PATCH 2/3] route: Select slave chmap based on ttable information David Henningsson
2014-02-21 15:49 ` Takashi Iwai
2014-02-21 15:24 ` [PATCH 3/3] conf: Allow 2.1 surround to use different number of channels David Henningsson
2014-02-21 15:50 ` Takashi Iwai [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5htxbstqfw.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox