Re:Audiophile forum debating which versions of memcpy had th...
by eurasiantiger on Tuesday March 14, 2023 @03:31AM
(#35148371)
The issue is not constant latency, but jitter i.e. latency is changing between bits
[ Parent
| on HN ]
Re:Audiophile forum debating which versions of memcpy had th...
by Dylan16807 on Tuesday March 14, 2023 @04:13AM
(#35148608)
Jitter matters in very specific cases in very specific pieces of equipment.
Jitter on the Ethernet transferring the file will have no effect.
Re:Audiophile forum debating which versions of memcpy had th...
by whstl on Tuesday March 14, 2023 @06:43AM
(#35149528)
Like the sibling poster said, this won't cause jitter.
The audio isn't played directly from the ethernet packets. It has to be decompressed, decoded, buffered. In the end of it all the audio goes into a ring buffer and it is played very precisely by the sound card.
The playback itself is a hard-real-time process that needs time guarantees. Failure to fill the ring buffer by any reason can cause audible skips, but not jitter. But most players in practice will simply stop the playback.
Re:Audiophile forum debating which versions of memcpy had th...
by pezezin on Tuesday March 14, 2023 @07:40AM
(#35149952)
The maximum jitter allowed by the IEEE specifications is 1.4 ns for 100-megabit Ethernet and 300 ps for Gigabit Ethernet. The bit time for a 48 kHz audio signal is ~20 000 ns. It is absolutely impossible that you can hear the Ethernet jitter.