Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Internal streamer (Devialet Expert) at the end of 2016
#40
(15-May-2016, 16:59)arcam Wrote:
(15-May-2016, 13:36)iamwappie Wrote: But..... If the TCP protocol is used it is assured that all network packages are received correctly. Put them in a buffer in the receiving device and once full enough stream and play them. So with that reasoning I though bit perfect is bit perfect....

You don't want to use TCP for streaming (due to latency), but RTP/UDP. Retransmission is typically handled in the RTP stack. Different retransmission strategies can be put in place. For example, for video, you don't need to retransmit past frames since they would arrive past their display time. For audio, you don't want to miss any packet or else you will hear glitches.

Latency is a non issue for non-broadcast music replay (in the home setting, not studio's) and asynchronous protocols that typically perform buffering. The only exception I can think of is when a single source is streaming to multiple and/or different receivers/endpoints.
PS Audio P3, Shunyata ΞTRON Alpha Digital and HC/Furutech power cables, Paul Hynes SR7EHD-MR4, DIY Roon Server & Roon Endpoint running AudioLinux Headless, Phasure Lush^2 USB cable, Audioquest Diamond RJ/E ethernet, Uptone Audio etherREGEN, Mutec MC-3+ USB, Shunyata ΞTRON Anaconda Digital XLR AES/EBU, Devialet Expert 250 Pro CI, Nordost Tyr Reference LS cables, Von Schweikert VR-5 SE Anniversary Edition, Anti-Mode Dual Core 2.0, JL Audio Fathom F112. More detail here.

The Netherlands
Reply


Messages In This Thread
RE: Internal streamer (Devialet Expert) at the end of 2016 - by Antoine - 15-May-2016, 17:10

Forum Jump:


Users browsing this thread: 1 Guest(s)