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: Mon, 02 Dec 2013 08:14:46 -0800 [thread overview]
Message-ID: <529CB1F6.7070607@gmail.com> (raw)
In-Reply-To: <529CAE8D.6020003@zonque.org>
On 12/02/2013 08:00 AM, Daniel Mack wrote:
>> 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.
Thanks! I'll have to play around with that.
>> 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?
I don't actually have one of these devices and the end-user I was
helping is happy now, AFAIK.
But solving this required editing asoundrc files (ugh) and casting
several magic spells. Would be nice if it "just works."
Anyway, perhaps the solution is to get JACK to recognize the extra
substreams.
-gabriel
next prev parent reply other threads:[~2013-12-02 16:14 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 [this message]
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=529CB1F6.7070607@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).