All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: "Gabriel M. Beddingfield" <gabrbedd@gmail.com>
Cc: Alsa-devel <alsa-devel@alsa-project.org>,
	Antonio Ospite <ao2@amarulasolutions.com>
Subject: Re: caiaq driver: audio 4 dj and jackd
Date: Mon, 02 Dec 2013 17:00:13 +0100	[thread overview]
Message-ID: <529CAE8D.6020003@zonque.org> (raw)
In-Reply-To: <529CA3FC.1040301@gmail.com>

On 12/02/2013 04:15 PM, Gabriel M. Beddingfield wrote:
> On 12/02/2013 01:59 AM, Daniel Mack wrote:

> Jack has always opened only one PCM device... which is the Right Thing 
> for most recording sound cards (e.g. ice1712, hammerfall, etc.). This is 
> the first "pro-sumer" device I've ever seen with multiple substream devices.

I was also uncertain when I wrote the driver which way is better. But
given that there are ways in ALSA to synchronously start separate
streams, I eventually went the stereo pairs way.

>> After all, the streams are guaranteed
>> to be synchronous, as they share the same clock in hardware.
> 
> TBH, the whole substream concept is lost on me.  Where does this 
> guarantee come from?  From the substream concept or from intimate 
> knowledge of this device? 

Both :)

> (I.e. how would JACK know about the clock 
> guarantee?)

snd_pcm_info_get_sync() should return the same clock id for both
interfaces in that case. But I must admit I haven't tried this in awhile.

>> 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.

> But, FULL ACK on the moving parts.  That would indeed make the driver a 
> little gross on the inside.

What are your results with the multi plugin? Is that something you can
live with?


Daniel

  reply	other threads:[~2013-12-02 16:00 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 [this message]
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
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=529CAE8D.6020003@zonque.org \
    --to=daniel@zonque.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ao2@amarulasolutions.com \
    --cc=gabrbedd@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.