From: Raymond Yau <superquad.vortex2@gmail.com>
To: David Henningsson <david.henningsson@canonical.com>
Cc: tiwai@suse.de,
ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v2 2/3] route: Select slave chmap based on ttable information
Date: Fri, 28 Feb 2014 21:49:57 +0800 [thread overview]
Message-ID: <CAN8cciY6OXQ2m0bU7rRfUVFGGxeeSTqZfgRraEEmVm8uRKUQEA@mail.gmail.com> (raw)
In-Reply-To: <1393574227-25732-3-git-send-email-david.henningsson@canonical.com>
2014-02-28 15:57 GMT+08:00 David Henningsson <
david.henningsson@canonical.com>:
> It means we need to initialize this order:
>
> 1) Read the ttable to figure out which channels are present
> 2) Open slave pcm and find a matching chmap
> 3) Determine size of ttable (this can now depend on the chmap)
> 4) Read ttable coefficients
> 5) At prepare time, select the matching chmap
>
Do this patch assume the slave.pcm of the route plugin must have a channel
map ?
are there any side effect when some of sound cards using route but does not
have channel map ?
e.g. ice1712,
playback.pcm {
type hooks
slave.pcm {
type route
ttable.0.8 1
ttable.1.9 1
slave.pcm {
type hw
card $CARD
}
slave.format S32_LE
slave.channels 10
}
rme9652, ....
slave.pcm {
type route
slave {
pcm {
type hw
card $CARD
}
channels 26
}
ttable.0.24 1
ttable.1.25 1
next prev parent reply other threads:[~2014-02-28 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 7:57 [PATCH v2 0/3] alsa-lib: Improve 2.1 surround support David Henningsson
2014-02-28 7:57 ` [PATCH v2 1/3] route: Allow chmap syntax for slave channels in ttable David Henningsson
2014-02-28 7:57 ` [PATCH v2 2/3] route: Select slave chmap based on ttable information David Henningsson
2014-02-28 13:49 ` Raymond Yau [this message]
2014-02-28 13:52 ` David Henningsson
2014-02-28 7:57 ` [PATCH v2 3/3] conf: Allow 2.1 surround to use different number of channels David Henningsson
2014-02-28 8:15 ` [PATCH v2 0/3] alsa-lib: Improve 2.1 surround support Takashi Iwai
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=CAN8cciY6OXQ2m0bU7rRfUVFGGxeeSTqZfgRraEEmVm8uRKUQEA@mail.gmail.com \
--to=superquad.vortex2@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).