In previous versions of Roon i have always had the impression that a stream from Qobuz/Tidal was cached in the Roon Server as fast as possible, and then delivered in a more or less real time fashion to the endpoint(s).
This seem to have changed, either due to Roon restructuring or perhaps Qobuz changes in their CDN’s previously.
Looking at Performance Monitor in Windows (my server choice), this snapshot is from a couple of minutes into the song playing. (Birds- Dominique Fils Aime, 5th Element 24B-88.2K)
Note the Receive column, at around 800Kbps… This has previously been done within 10Seconds of a song chnage/initialization.
My Internet speed is not significant, but 100Mbps should be fine to stream this kind of material, at least 20 times in in parallell!
Any reflections on the subject from other observant users?
I’m seeing exactly the same with local flac files. Constant data transfer from my Roon Server to my endpoint throughout all parts of every track. This is a new thing, as far as I can tell. Do you want to move the thread to Feedback so that Roon staff can see this?
I should take some measurements, but if so, this is not a bad thing.
Edit: I’m still seeing rather bursty audio delivery from Roon Server to Roon Bridge.
For this reason, I’m successfully using the Diretta protocol downstream of Roon Bridge to smooth out network audio delivery before it reaches the transport that feeds the DAC.
No, the server->endpoint behaviour is not new, it has always been like that.
The RAAT protocol is working with a low buffer, but it is “bursty” as @David_Snyder also points out.
My feeling is that the buffering from Qobuz (in my case) is throttled and seem to take much longer time than in “the olden days”.
The incoming traffic does stop eventually, but usually after half a song or so (hirez).
