0 Members and 1 Guest are viewing this topic. Read 2392 times.
Mode 1: Synchronous word-clockThe source device must have a word-clock input, such as some high-end transports, some PCI cards such as the Lynx AES16 or the Transporter. A word-clock cable is connected between the Pace-Car USB and the source device. The customer provides two digital cables.Mode 2: Synchronous master-clockThe source device must have a slave-clock input to use this mode. This can be added to Sonos, Squeezebox, Duet, Tascam US-144, EMU 0404 and other devices with a small modification by Cullen Circuits to add the Slave-Clock input. A master/slave-clock cable is connected between the Pace-Car USB and the source device.Mode 3: AsynchronousThe Pace-Car USB is tuned to the source computer or device and tracks the rate of the incoming digital stream. Mode 4: USB
Studio master clocks are not the same as how my products work. They are generally used for synchronizing events for editing. They are generally not used for playback. His article confuses the word-clock with the frequency I call master clock, which is generally 128 or 256 times the word-clock. Some of the things he says about master clocks are true, like with the A/D converter. However, all of the "master-clocks" that he tests are actually word-clock generators. The reason that I use the term "master-clock" is that this is the term that is used at the D/A chip. Unfortunately, the word also describes a system word-clock in a studio environment. Totally different. The tests that he performs are interesting primarily for studios. IMO, providing even a superb low-jitter word-clock is not very effective for reducing system jitter. The clocks need to be low-jitter true master clocks at 256X the word-clock frequency. This is how my devices work. When you provide only word-clocks, then the device must synchronize its internal clock to this and then the jitter is a function of the internal high-frequency clock, not so much the external word-clock.