From: sylvain.bertrand@gmail.com
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: USB-Audio.conf routing and dmix
Date: Wed, 13 May 2015 11:32:15 +0000 [thread overview]
Message-ID: <20150513113215.GA569@freedom> (raw)
In-Reply-To: <55531850.1020208@ladisch.de>
On Wed, May 13, 2015 at 11:24:32AM +0200, Clemens Ladisch wrote:
>>> I linked the surround51 and surround71 pcms with the 'disable-able' dmix
>>> section from the default pcm.
>
> These devices are not supposed to use plug or dmix.
Ok. Then, there is no pcm to output 5.1 sound with dmix.
Does it mean that the application is in charge to build a alsa-lib pipeline
with dmix pcm and surround51 pcm, in order to let other applications output 5.1
sound at the same time?
regards,
--
Sylvain
next prev parent reply other threads:[~2015-05-13 11:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 0:20 USB-Audio.conf routing and dmix sylvain.bertrand
2015-05-11 19:57 ` sylvain.bertrand
2015-05-13 9:24 ` Clemens Ladisch
2015-05-13 11:32 ` sylvain.bertrand [this message]
2015-05-15 2:07 ` sylvain.bertrand
2015-05-15 5:53 ` Alexander E. Patrakov
2015-05-15 5:58 ` Alexander E. Patrakov
2015-05-15 8:13 ` Raymond Yau
2015-05-15 13:16 ` sylvain.bertrand
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=20150513113215.GA569@freedom \
--to=sylvain.bertrand@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.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