alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Gabriel M. Beddingfield" <gabrbedd@gmail.com>
To: Daniel Mack <daniel@zonque.org>
Cc: Alsa-devel <alsa-devel@alsa-project.org>,
	Antonio Ospite <ao2@amarulasolutions.com>
Subject: Re: caiaq driver: audio 4 dj and jackd
Date: Wed, 04 Dec 2013 20:11:51 -0800	[thread overview]
Message-ID: <529FFD07.5040408@gmail.com> (raw)
In-Reply-To: <529CAE8D.6020003@zonque.org>

On 12/02/2013 08:00 AM, Daniel Mack wrote:
>>> Technically yes, but changing that would mean breakage for all other
>>> users, and making it configurable would result in yet another moving
>>> part which makes things even more complex.
>>
>> How would this cause breakage?  Users that use 2 stereo substreams could
>> still work normally.
>
> Yes, unless you opened the first subdevice with more than 2 channels.
> Then an existing user for the second stream breaks. IOW: the possible
> configuration and usage for subdevice 1 changes depending on that of
> subdevice 0.

Suppose a 2nd PCM device is added that would allow 1-4 channel 
playback/capture (call it "Multichannel Audio" or something).  This pcm1 
would be mutually exclusive with pcm0 (I.e. while one is open you can't 
use the other).

Existing applications using hw:n,0,0 and hw:n,0,1 see the exact same 
interface/behavior.  The only failure mode is if the multichannel PCM is 
in use.

Applications using multichannel work-flows would use hw:n,1.

While it's not a "just works" solution -- directing users to hw:n,1 is a 
whole lot better than teaching them how to set up a multi plugin.

-gabe

  parent reply	other threads:[~2013-12-05  4:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02  3:02 caiaq driver: audio 4 dj and jackd Gabriel M. Beddingfield
2013-12-02  9:59 ` Daniel Mack
2013-12-02 15:15   ` Gabriel M. Beddingfield
2013-12-02 16:00     ` Daniel Mack
2013-12-02 16:14       ` Gabriel M. Beddingfield
2013-12-02 19:48         ` Alan Horstmann
2013-12-02 21:22           ` Gabriel M. Beddingfield
2013-12-05  4:11       ` Gabriel M. Beddingfield [this message]
2013-12-10  2:27         ` Gabriel M. Beddingfield
2013-12-10 10:39           ` Daniel Mack

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=529FFD07.5040408@gmail.com \
    --to=gabrbedd@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ao2@amarulasolutions.com \
    --cc=daniel@zonque.org \
    /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).