Jitter and 75ohm cable length


I have read a number of papers on how cable length plays a role in Jitter between transport and DAC. After all of the dust settled I arrived at no sound conclusion, on paper, so I decided to use the ears of my 17 year old budding Audiophile to settle this by LISTENING! My transport is a Wadia 171i (WAV/LossLess files)and my DAC is a Cambridge AZURE 840C. I had three cables in my test, my 1M Kimber D-60 illuminations, a 3' HAVE/Canare and a 6' HAVE/Canare. All three cables sounded good, but in the end the victory landed on the 3' HAVE/Canare by a fair margin followed by the Kimber and last the 6'HAVE/Canare. In my readings I came across a number of articles saying you should use at least 1.5M of cable to reduce reflections in the cable so as to not harm the clock signal, yet an RF engineer said this was a bunch of "Bunk" and 1M would be better, in fact he said the shorter the better. So, forgive my verbosity, what are your thoughts and experience in this area? My 3' $25 HAVE/Canare beat up my $390 Kimber, I believe due to proper honest 75ohm terminations vs standard RCA connectors, and as far as length goes, at least in my system, 3' was by far the best. Thanks!
Rpg
rpg
If one suspects they have a Jitter problem with their system, how might it manifest it's impact on the analog output.
I second Kijanki's excellent comments, and I would add the following thoughts, which I composed before seeing his response:

IMO it's very unpredictable, and the symptoms will vary widely depending on the spectral characteristics of the jitter, which can be expected to be a very complex mix of discrete frequency components and broadband noise-like components. Some of those components will be correlated with the values of the 1's and 0's defining the music data (which is different than being correlated with the music itself), and some will not be.

Perhaps essentially all that can be said is that there will be a loss of clarity, and an increase in distortion.

The following papers may be helpful. The second one, although highly technical, conveys a sense of how complex it all is, and by implication (as I see it) that the effects of digital cables and digital interfaces should not be thought of in the same kinds of ways that we use in describing the effects of audio frequency analog cables, e.g., "overly warm" (notwithstanding the fact that a given cable may create that perception in a given specific system):

http://www.positive-feedback.com/Issue43/jitter.htm

http://www.scalatech.co.uk/papers/aes93.pdf

Regards,
-- Al
Let me add to Al's great post. As he stated, typical transport has transition times in order of 25ns. Threshold resides most likely at the half of that - 12.5ns while impedance boundary, that causes reflection will reside on the other end of the cable. Sharpest slew rate change, causing reflection, is usually at the very beginning (knee). From that point signal travels forth and back (reflection) over distance of 2x1.5m=3m with speed of about 60-70% of light speed - let say 0.2m/ns. Reflection will return in 15ns missing time-wise threshold point. I would use 1.5m-2m length or less than a foot where transmission line effect is non-existent yet. Rule of thumb says that we're dealing with transmission line when transition time is less than 8 times propagation delay (one way). It would imply that typical 25ns transport digital cable becomes transmission line when propagation is longer than about 3ns being equal to about 0.6m. It sounds strange but good cable should be very short or 1.5m-2m. When transitions are slow we don't have much of reflection induced jitter problem but rather noise induced jitter (noise affecting threshold point). When transport has fast transitions noise induced jitter is reduced but reflection induced jitter is dominant requiring very good cable. Long cables in addition add to noise pickup so whole thing becomes system dependent. Same cable might sound great with one system but no so great with the other. Many people report better results with Toslink, in spite of slow transitions, perhaps because of noisy environment or ground loops that coax might create.

Magfan, I commented only on Stereophile findings. AE sounds very clean in my system but I use it with Benchmark DAC1 that is jitter suppressing. It is possible that your AE is bad but it is also possible that one sent for evaluation to Stereophile was extremely good (selected?). It is even possible that Stereophile measured wrong - who knows.
Apparently, the AE/840c jitter 'thing' was a known issue. CA issued a software update, which I've got here.......somewhere, but have been too Chicken to install.
It uses a null-modem cable and the requested OS is Windows XP, which my laptop doesn't have. The procedure sounds simple, but than again, were dealing with confusers, here.
I'm sure that CA would be thrilled if I 'bricked' my player. Also, CA no longer sends out the update to individuals, or so I've heard. That COULD be because too many people failed in the update and were really....angry.
I like the AE, even the analogue output. Using my iPod Touch as a remote is just icing on the cake.
You write about jitter induced at the impedance boundry, but what about a simply poorly clocked system? Shouldn't that be added in to the total system jitter? Or perhaps multiplied. if you are sending out a poorly clocked signal into the cabling with the reflections, it sounds like you are compounding the problem.....
Magfan, CD data stream is asynchronous. It is also jittery because of less than perfect CD printing and reading plus quality of the transport and system noise. What is needed to reduce jitter is either to create stable clock for D/A converter based on average datastream rate locking both with PLL (Phase Lock Loop) - solution used in most CDP or ignore completely datastream rate and reclock it with fixed stable clock in Asynchronous Rate Converter (Benchmark DAC1).

We can add to this jitter introduced in A/D process, that cannot be removed no matter what you do. At the very beginning a lot of analog recordings got digitized with less than perfect (jittery) clock and the only way out is to digitize it again if analog master tapes still exist.

The cable length of 0.6m without transmission line effect, that I calculated, applies to 25ns transition time assuming that driver delivers constant slew rate. There are drivers that do that but very often leading "knee" has higher slew rate. Because of that I would perhaps limit such cable to half of that (0.3m). Above that careful matching of characteristic impedance is recommended. This characteristic impedance has very strange definition. It is impedance of infinite cable or finite cable terminated with its own characteristic impedance - which sounds a little like Catch22. For all practical purpose it is simply SQRT(L/C) implying particular geometry.

I'm not sure what happens with balanced cables. Impedance is 110 ohm and voltage levels are much higher but at the same time slew rate is likely higher and reflection induced jitter taking over noise induced jitter. Maybe Al can help here?
I'm not sure what happens with balanced cables. Impedance is 110 ohm and voltage levels are much higher but at the same time slew rate is likely higher and reflection induced jitter taking over noise induced jitter. Maybe Al can help here?
I'm not sure either, mainly because I don't have any specific knowledge of what risetimes/falltimes/slew rates tend to be for typical AES/EBU outputs. My suspicion is the same as yours, though, that those parameters are likely to be faster than for typical S/PDIF outputs.

Also, while on the one hand the higher AES/EBU voltage levels (assuming the particular equipment in fact conforms to the AES/EBU voltage standards) and the balanced operation would seem likely to help with respect to noise-induced jitter, on the other hand I would expect that in many or most cases balanced digital cables will provide less accurate control of characteristic impedance than a good 75 ohm coax will typically provide.

Excellent elaboration in your posts, btw, on the distinction between noise-induced jitter and reflection-induced jitter, and the competing tradeoffs that result.

Best regards,
-- Al