The OP focus is on the network Ethernet cable. You are focusing on the DAC.
We agree data packets transmitted over the Ethernet can be corrupted. The bits travel on an electric current and any electrical anomaly can cause corruption. Think of streaming television where, in an electrical disturbance you can have screen dropouts.
What I continue to stress is that Ethernet protocols are robust with built-in error detection such as CRC (Cyclic Redundancy Check) and imbedded check code sequences that flag an error. The Ethernet protocol will simply request that packet again. Streamers and DACs do no rely on corrupted packets; rather, they buffer until a correct, complete packet is received. So, in a well-functioning network, you won’t hear sound quality issues because the data is either correct or it’s re-requested, unless the buffer is too small or network latency is extreme, where you could have dropouts. Audio file protocols are also robust with similar redundancy checks. Therefore, audio files are bit perfect on properly designed streamers and DACs on a functioning network due to Ethernet protocols and industry digital music file protocols.
The Ethernet assures accurate data packs not timing that you are discussing, unless, as I stated before, the electrical signal over Ethernet carries RF coupled to the streamer or DAC click, where clock function is affected. Timing from an audiophile perspective is critical when the sequenced bit perfect data packages are converted to analogue. So the Ethernet has assured the streamer or DAC has received a bit perfect file in sequence. The conversion of the sequence is to be at standard timing (44.1, 96 KHz as an example). The clock assures the standard file timing is accurate at conversion. If there are timing errors in the digital data packages the resulting analogue voltage steps can jitter, which can introduce noise in the analog waveform. That jitter, in turn, can raise the perceived noise floor, blur subtle details, and reduce soundstage precision. You experienced better timing is directly proportional to sound quality when you added the external clock. My experience was different. The $500 audiophile Ethernet cable was from a very respectable audiophile cable designer/manufacturer. However, its metal connector housing was coupling RF. The well designed cheaper cable produced improved SQ because it better insulated RF.
in conclusion:
- The Ethernet can send corrupted data packages
- The redundancy in the Ethernet protocols assure data package correction and bit perfect data at the user level if the network connection is sound.
- The Ethernet protocols assure correct data sequencing, but this is different from audiophile timing concerns.
- Digital music file protocols assure bit perfect music files are timed properly at conversion to analogue.
- Therefore, the Ethernet cable does not affect jitter directly. The way the Ethernet cable can affect jitter is if it is improperly shielded and permits RF coupling affecting clock performance.
- Ethernet cables can affect sound quality simply due to physics. The degree of the effect and the benefit / cost ratio of expensive cables can continue ad nauseam.
Interesting exchange. Thanks. Have a phenomenal day and listening experience

