From: Doug McLain <doug@nostar.net>
To: John Rigg <ad@sound-man.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Multi Delta 1010 sync
Date: Tue, 07 Feb 2006 15:27:26 -0500 [thread overview]
Message-ID: <43E902AE.1000804@nostar.net> (raw)
In-Reply-To: <20060205161525.GA2691@localhost.localdomain>
Yesterday I set the master 1010LT to 96000 Internal, and the slave card
to SPDIF In (with an rca cable connecting SPDIF Out to SPDIF In), ran
jack at 96Khz, and fired up xmms and ran an mp3 in repeat mode for the
last 24 hours, with its outputs connected to all 16 outputs, and all 16
inputs connected to my mixer, with no xruns.
Doug
John Rigg wrote:
> After some reverse engineering I've found out why I was having trouble
> syncing my two Delta 1010s at high sample rates using the word clock inputs.
>
> The Delta 1010 uses a 74HC4046 phase-locked loop (PLL) to lock onto the word
> clock input signal. This is used in a feedback loop with a /256 counter to
> produce a frequency that's multiplied by 256x at the output of the PLL
> oscillator. With a 48kHz input this gives a PLL frequency of 12.288MHz.
>
> According to the 74HC4046 data sheet, the maximum frequency it can
> work at is 13MHz. In other words, even a 48kHz clock is close to the
> specified limit, so forget about higher frequencies. (I didn't discover
> this until after I'd built a 96kHz word clock :-(. )
>
> 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.
>
> My conclusion is that the only way to sync these cards reliably
> at all frequencies is to clock them both from an external S/PDIF device,
> and to make sure both cards are receiving the clock signal directly from the
> master device (ie. not going through the S/PDIF circuitry of the first card on
> the way to the second card).
>
> 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
prev parent reply other threads:[~2006-02-07 20:27 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
2006-02-07 20:27 ` Doug McLain [this message]
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=43E902AE.1000804@nostar.net \
--to=doug@nostar.net \
--cc=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