From: John Rigg <ad@sound-man.co.uk>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Multi Delta 1010 sync
Date: Tue, 7 Feb 2006 19:06:41 +0000 [thread overview]
Message-ID: <20060207190641.GA3516@localhost.localdomain> (raw)
In-Reply-To: <20060205161525.GA2691@localhost.localdomain>
On Sun, Feb 05, 2006 at 04:15:25PM +0000, John Rigg wrote:
> The S/PDIF receiver OTOH uses its own internal PLL which works with 96kHz
> sample rate. However,I couldn't sync reliably using the S/PDIF in/outs with
> one card as master and the other as slave. At 96kHz jackd would die at random
> times with a floating point exception, so often it was unusable.
> At 48kHz this would still happen, but not often (every couple of hours).
> I'm guessing that this is due to a phase difference between master and
> slave clocks.
An update: the floating point exception was a divide-by-zero error
in jackd that only occurred sporadically.
The Delta 1010s sync perfectly well via the S/PDIF in/outs with one card
as master and the other as slave.
To summarize:
Word clock inputs work at 48kHz but not higher due to a hardware
limitation.
S/PDIF inputs can be used to sync up to 96kHz.
John
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next prev parent reply other threads:[~2006-02-07 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-05 16:15 Multi Delta 1010 sync John Rigg
2006-02-06 11:04 ` Doug McLain
2006-02-07 19:06 ` John Rigg [this message]
2006-02-07 20:27 ` Doug McLain
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=20060207190641.GA3516@localhost.localdomain \
--to=ad@sound-man.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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