DACs and sources simply need to do a checksum cross reference to ensure that the data stream is bit perfect...it adds latency and overhead processing to the mix, but that's a small cost to pay. It is standard tech in computing, it is what my external drives, NAS, etc. do in order to ensure data integrity of files I transfer over the network, USB, etc..
I assure you, they do not need to do this at the session/application layer. There is no data corruption until it's obvious, even with isochronous transfers. All USB data packets have a CRC, so an error can be detected even with isochronous transfers, it's just that there is no retry or guarantee of delivery. Please, do some research before further adding to the confusion. Your external drives use this very CRC, the only difference is they operate via bulk transfers not isochronous, and so they will retransmit. There is no point to retransmitting audio packets/frames. If the link has degraded to the point you are getting audible errors, the only thing retries will do is delay the audio you do hear between pops and clicks. It may be that some USB devices don't do anything if the CRC is bad, but about the only useful thing they could do is light up an error LED.
The bottom line is that if you don't hear pops/clicks/dropouts, you don't have a data integrity issue.
Last edited: