Killcomic
100+ Head-Fier
I've been working on computers for decades. Mine is an educated guess as opposed to one formed by marketing material. May I point out you dont have data either?Sure, but in our defense that's only because that's not true. Mostly that's likely due to the USB audio spec (as opposed to the USB bulk spec) guaranteeing bandwidth but no error correction, thus errored bits in a word (noise) or mis-timed bits (jitter) can get directly converted by the DAC into analogue ... but really we don't know. (no matter what the inbred groupthink would tempt you to believe)
So feel free to bust out your source-side / DAC-side data analysis showing you're right, but realize you'll have to know the XMOS or C-media USB receiver chip firmware code, which is a trade secret, so you'll likely be easily identifiable by them, and nobody here would ask you to break your contract.
Or ... you don't have that data, don't know what that code says, and you're guessing.
My bet is on the latter.
Actally, you want data? Transfer a file over usb and see how many CRC errors you get with different cables?
Hint: None.
Watch a 1080p, or even 4k, video over USB and see how much jitter and artifacts you get compared to the original file.
Hint: None.
You can transmit 1080p video, which requires a lot more bandwidth, over a simple cable that you can buy for $10.
The maximum bandwidth is determined by the host, not the cable.
USB 2 is 60 MB per second and USB 3 is 640 MB per second. The bottleneck is not the cable but the controller type.
Please tell me how you need a special USB cable to transmit music.
Last edited: