|
|
|
|
|
|
Q:
Will feeding each piece of equipment individually from my multiple output masterclock still be the preferred best method of reducing system wide jitter?Or will the " Loop Sync " feature actually be better for removing system wide jitter than the dedicated masterclock method?
A:
Signal corruption can happen at almost any stage of the clock chain. It is impossible to tell if a multi-drop topology (one generator feeds multiple destinations) is any better than a daisy-chain topology, since so much depends on the quality of the driver and receiver electronics, the cable impedance matching, how, exactly, the daisy-chain devices pass the clock through, etc.On the 192, we made sure that there was no measurable degradation of the loop sync clock as it passed through the interfaces. We scrutinized this path and had to make several changes in development until it was just right. The net effect is essentially identical to that of a clock DA. Then, any residual jitter on the that loop sync clock is further attenuated by the local clock generator. The result is that the converters are well "shielded" from outside jitter sources. Even though the 192 will attenuate the jitter from the Nanosyncs, you'd be better off just using the HD internal clock. Its intrinsic jitter is considerably lower.
Other Popular Articles:
Setup for creating additional headphone mixes in Pro Tools LE/Digi 001. Clock options with Pro Tools|HD hardware:Can you output a 44.1/48kHz Word clock signal from the primary interface when running a session at a higher sample rate (96 or 192 kHz)? Pro Tools goes into infinite "processing" mode while trying to import tracks with plug-in settings saved to a location other than the System Folder>DAE Folder>Plug-In Settings folder. Hard reboot necessary. Physical Dimensions (both 96 and 192 I/O) DAE no longer exists as an application. What does this mean for third party support with applications such as EMagic Logic Audio? |