From: Damien Zammit <damien.zammit@gmail.com>
To: alsa-devel@alsa-project.org
Subject: - snd-usb-audio - SPDIF clock source mixer control for Digidesign Mbox
Date: Wed, 29 Oct 2014 21:21:29 +1100 [thread overview]
Message-ID: <5450BFA9.1090908@gmail.com> (raw)
Hi all,
As some of you may remember, the Digidesign Mbox has a multiple endpoint
interface and does not follow the standard USB audio spec.
I am pretty sure that the first interface 0 is for firmware upgrades
only, and the second interface has 2 endpoints one for playback and one
for capture.
I have heard that the SPDIF output is always on, but there is a special
command to change the clock source to external sync with SPDIF.
I think I have found the correct USB command for changing the clock
source of the device to SPDIF external sync. I tried to use a pair of
the devices in JACK using a pcm_multi configuration and syncing one of
them to the other with a RCA cable, but unfortunately I get lots of
XRUNs in JACK and I am wondering if there is a reason for this?
Can someone who knows about the pcm_multi stuff shed some light on why I
might be getting thousands of XRUNs when I use two identical USB
soundcards that are (hopefully) synced to each other?
I have written a non-standard mixer control for this so alsamixer can
select the external clock source.
Basically, the command to set SPDIF sync seems to include a sample rate
command, but the sample rate is set to zero for SPDIF sync. Could JACK
be resetting the sample rate and overriding my command perhaps? How
would I override the ALSA driver code so that the sample rate is not
reset by JACK to 48000 instead of 0 but only when the mixer control sets
the flag?
Damien
reply other threads:[~2014-10-29 10:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5450BFA9.1090908@gmail.com \
--to=damien.zammit@gmail.com \
--cc=alsa-devel@alsa-project.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 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.