0 Members and 1 Guest are viewing this topic. Read 4269 times.
That link sends my anti-virus into spasm.Doc
I read a bunch on it when I was researching USB DAc's. The consensus was that the Belden Gold was a cheap and good one. I spent the $10 and have not looked back. Could more $ yield better sound? Sure, but the same can be said of my entire system, and I won't invest much in cables these days.
In my system the USB cable is critical to extracting the maximum performance from my DAC. With the wrong design I can cripple the the systems performance. The sound-stage turns into musical wallpaper pasted on the front wall behind the speakers. The highs and lows can be missing in action and the dynamic life has taken a hike. Scotty
Agreed. The USB cable feeding my DAC from my Mac Mini makes a noticeable difference. You have to remember that USB audio output contains no error correction (unlike USB data output from a hard drive to the computer). Sure, a file moving from a hard drive into the computer is just bits, but the data protocols for moving audio out of the computer are not the same. Also, the USB cable carries power, and it's a potential source of noise, voltage fluctuations, and disruption to the DAC. Not a technical explanation, but certainly there are reasons a USB cable can make a difference.
Actually, the data protocols are the same. The difference is in the transfer type. Audio is isochronous while copying files is bulk. Both contain error detection via cyclic redundancy checks (CRC). In a bulk transfer, data correctness is considered more important than timing so error correction is done by retransmitting after detecting a bad CRC. For isochronous, timing is assumed to be more important than receiving every packet. That is, losing a frame of video is less noticeable than a corrupted frame. So, the error detection still happens but the data is ignored and no retransmission is done.So, yes a cable can make a difference but only when comparing against a substandard cable. Anything that passes USB signal integrity testing should not experience errors. To completely remove the cable from the equation, forward error correction could be included in the data packets. Then a bad packet would be completely recoverable by the receiving device.
That's a long-winded way of confirming what I said.
1. USB audio does not correct errors. You mention error "detection" but it's not relevant that an error is identified: when there's an error, a USB audio data transfer will simply drop the packet and keep going: timing over data integrity. Very few people seem to recognize this difference. If you want to say its a difference of "transfer type" and not "data protocol" then fine. Call it "wooly wombat" for all it matters.
2. USB cables carry power as well as data. You didn't discuss this but it's equally important. Even if the DAC isn't powered from USB (although many are), the voltage fluctuations and noise over the cable can affect the DAC's power supply and affect the integrity of the data signal.
No need for quotes around detection.