13-Aug-2018, 23:08
(This post was last modified: 14-Aug-2018, 07:20 by thumb5.
Edit Reason: Fixed typo
)
The errors will not be in the form of corrupted packets, because each packet has a frame check sequence; if the data in a packet are corrupted, the hardware simply drops the packet. So the typical failure modes of UDP are based on missing packets and/or (possibly) packets delivered out of order, not single-bit errors or even single-sample errors. Given a big enough buffer on the receiving end, it's not hard to imagine how sequence numbers, time-outs and re-transmission could be used to build a reliable packet stream out of UDP. And once you have a reliable packet stream, there are no other errors to consider. In other words, it does not have to be "super complex" to be as good as TCP - for this application, with this hardware.
Of course, I'm not arguing that you don't hear a difference. But I don't think you've picked on the explanation for what you hear.
Of course, I'm not arguing that you don't hear a difference. But I don't think you've picked on the explanation for what you hear.
Roon (Mac Mini), Wilson Benesch Full Circle, Expert 1000 Pro CI, Kaiser Chiara
Warwickshire, UK
