It's a cable. It can't do anything weird to the data. If it gets through intact, it will be identical.

Factors like attenuation and shielding matter in certain circumstances, but not for a meter of USB.

I'm not really talking about the cable, but the idea that digital interfaces like SPDIF/USB Audio/HDMI are "bit perfect." The digital phenomenon of bit perfection, as programmers see it, is a fiction created by buffering, retry, and error-correction. SPDIF doesn't do any of these, and USB Audio doesn't do all of these in all modes. SPDIF receivers (and depending on the mode, USB Audio receivers) will recover the clock signal from the input signal, and use that clock signal to drive a DAC. So it's not just the sequence of ones and zeros that is relevant (a digital phenomenon), but the timing of their appearance on the cable (an analog phenomenon). Variation from the ideal timing will cause a distorted clock to be recovered by the receiver, which will cause distortion in the analog signal produced by the DAC. Whether or not these distortions are audible, they are certainly measurable.

In over 100 audiophile bashing posts, at last someone who actually understands the issues. USB cables have an 'eye pattern' which affects the timing of the signal presented to the DAC.

If USB cables make a difference, then there is probably an argument for doing something else (not ignoring the problem because USB cables must be 'perfect'). Like putting the DAC and computer driving the DAC in the same box and connected by I2S with the DAC as the master.

There are some good articles on the Audiostream site about why 'bit perfect' doesn't cut it in the context of audio:

http://www.audiostream.com/category/industry-voice

What kind of insane hardware depends on CPU timings and doesn't have a hardware buffer that always plays at the same speed? Jitter in the intermediate steps doesn't matter when you're moving digital data from one place to another, as long as the buffers are larger than the amount of jitter.

DAC is hard. Moving a couple megabits of data five feet over a cable with multi-millisecond buffers is not hard.

I don't think it's even possible to use USB for 100%-throughput unbuffered data. I call bullshit on the eye pattern affecting playback.

Just because a difference technically exists in some circumstances with an oscilloscope does not mean it makes a difference in normal use cases.

Also wow that site called wireless a 'potential long-term health risk'.

What you're describing isn't as easy as it sounds. In order to have a "hardware buffer that always plays at the same speed" you need a high-quality locally generated clock, plus a decent amount of local buffering. But in a USB audio device or SPDIF device, you can't run a totally independent clock, because it will get out of sync with the clock on the host device sending the data. There are various tricks to get around this (e.g. having a feedback loop using a sideband), but it's actually a non-trivial problem. See: http://www.cypress.com/?docID=45044 for one approach. Most USB audio devices don't even attempt to do this. They try and recover the host machine's playback clock using the timing of USB SOF packets (which are sent every millisecond-ish) plus the timing of the USB audio data packets it receives.

Yes, sure, those things are hard, and they have nothing whatsoever to do with the quality of passive components like cables, as long as they are not in the failure range. Or anything to do with working-transceiver quality except when it comes to the clocks that the transceivers are using.

When you talk about jitter introducing significant distortion based on packet timing, that's something that can only happen in two ways: either the audio receiver is using an absolute garbage clock, or it's using an absolute garbage and shortsighted algorithm for adjusting its clock rate, and not trying for a stable sync. The quality of transceiver and cable components is not a factor.

Unless your cable is broken, there will be no retrying or high level error correction going on. And buffering will be independent of the cable chosen.

A passive cable can't change timing. The only question is whether the signal gets through in an intact form and can be locked onto. Any kind of difference you can have from working-cable construction is completely overshadowed by things like cable length.

I'm not saying that the cable can change timing. My post really wasn't about the cable. It was about the more general misconception that people have that digital audio/video interconnects (the whole system, cable + transceivers) are somehow "bit perfect."

> Can you hear it? Who knows.

There's no "who knows" about it. The change in output due to changes to the signal on the cable is well understood.

The reason this sort of thing is considered to be ridiculous is not because the signal on the cable can't change. As you say, it's all analog at the bottom. However, with a digital system, any change is either corrected in the receiver or shows up as a massive error. That is to say, you never get subtle errors. You either get perfect data transmission, or you get a horrible glitch that even the most tone deaf person can hear.

Digital interconnects generally do not have error correction. Signal degradation with digital interconnects generally shows a cliff effect, but it's a myth that you get either a perfect picture or no picture. At some point the receiver loses lock, but before that you get a gradual escalation in bit errors that may or may not be obvious: http://www.audioquest.com/resource_tools/downloads/whitepape... (see page 6).

And with audio, errors caused by digital transmission, mainly clock jitter, can be quite subtle: introducing low-amplitude unwanted signals into the analog reconstruction.

I'm well aware that there are intermediate states between perfect and no picture. My point is that the errors are always going to be obvious, not that they'll destroy everything. If any errors at all are happening on your HDMI cable, you'll see obvious errors in the picture. If errors are happening in a digital audio cable, you'll hear obvious errors in the sound. If you can't hear or see any errors, then there aren't any. Not every error will produce a discernible visual or audio artifact, but if they're happening with any regularity, then you'll occasionally get one in a high-order bit instead of a low-order bit that will make its presence obvious. It's not possible for the errors to only show up in the low-order bits.

Clock jitter is an interesting point, but I can't see how the effect could possibly be perceptible, given that the clock in question is running at an order of magnitude or two faster than the audio sample rate, and any jitter in the signal due to the physical cable will be orders of magnitude smaller than that. Those "low-amplitude unwanted signals" would surely be in the megahertz range, far beyond any possible human perception.