SuperG
Having formerly worked as an engineer with communication protocols, I get peeved when I sense a lack of accuracy when describing such... Too many hours coding to the wrong specification can do that to you...
...
Bits are bits.
True. As long as all of the bits get from one end to the other.
After two years working as an asst. crew chief on the Neutrino beam line at Fermilab National Accelerator Laboratory, I spent the next 20 years doing SCADA (Supervisory Control And Data Acquisition) over radio. I designed solar-powered master and remote telemetry units (MTUs and RTUs), and then went on to run the systems engineering department.
One day, while walking down the hall, I observed two design engineers with their hands in their pockets, staring at the prototype of a custom RTU they were developing for Amoco Pipeline Co (after having been given $750K to do the work). They had a signal analyzer hooked up to it, but their eyes were as blank as the analyzer's display. I stepped in and asked them "what's up?". Well, apparently, they had signal on one card, but not the other that was connected to it by a 40-pin ribbon cable. They just couldn't understand why there was no signal on the far side of the cable.
I took one look at their schematic, started laughing, walked out and headed to my old boss' office to tell him he had two morons working for him.
They were trying to drive the address and memory busses directly from the CPU chip with no buffering drivers.
Cables and connectors can act like chokes (inductors). Square wave (ones and zeros) in. Tiny little rounded bumps out.
For a bit to be a bit, it's got to get to the far side in such a condition that it can be decoded correctly.
If you've got a crappy cable, it's just not going to work...and you'll know it, no problemo.
I don't need a USB audio conditioner. I need a DAW audio improver!