Thanks for the updates. The end_stream you cited is actually normal, not a fault
07/05 14:56:48 SENT [14]{“request”:“end_stream”}
The surrounding log shows exactly what was happening at that second: the Roon server zone (the local Douk, “HIFI DSD”) was finishing the track “Sour Times” by Portishead. Watch the buffer drain naturally as the track ends:
14:56:41: _Advance (Track) then OnToNext, LL_PlaybackStarted: fresh start
14:56:42: next track begins, [100% buf] PLAYING @ 0:01/3:56 "Shine" by Lovefreekz
The end_stream at 14:56:48 is RAAT closing out the finished track's stream as the next one starts. This is what the end of every track looks like. It is routine housekeeping, not a disconnect.
And the proof it wasn’t a stop: playback continues seamlessly. “Shine” plays through 0:01, 0:06, 0:12 … all the way to 1:15 and beyond at 100% buffer, while the Kitchen Pi simultaneously keeps playing “Light Up the Sky” without a blip. Nothing disconnects. No tcpaudiosource error, no lost client, no Retrying. The system is completely healthy across the entire window.
We do see hourly backups that could potentially be causing playback to stop, this is also expected behavior. If you haven’t yet, I’d update your server and remotes to the latest version of Roon, and see how things perform.
Hi Benjamin, I accept that in this particular instance I have spotted something that is ‘normal’ operation. But that just means I didn’t spot what actually caused it to stop even though I started from the end of the log file working backwards in time. So what did cause it to stop this time?
This random stopping has been going on for well over a year. Every time a potential cause is identified I try the fix. But it just seems to shift the random stopping to a different alleged problem.
So far I have swapped out Apple Mac minis as Endpoints for Raspberry Pies running RoPieee, checked all my Ethernet cables, rewired, double checked the cables, changed Ethernet hubs for new switches, restructured the topology, swapped over Douk USB to S/PDIFF adapters etc, etc, etc. And the dropouts persist, allegedly for a new cause every time.
And yes, every time a new release of ROON, Rock, Roon Bridge or RoPiee comes out my system is instantly updated.
I am an electronics/software/systems engineer with 40 odd years of experience. What this experience tells me is that either there are many individual faults in Roon that maybe are slowly getting fixed or there is a single underlying structural problem that keeps manifesting in different ways when patches are applied.
I read the change log for the recent release and did not find any change that was going to explicitly fix this problem. But it’s download and running. So we will see what happens.
Just checking in on this, have you had a chance to see how build 2.70 is behaving across your devices? If you’ve noticed any changes on Roon Remote, Roon Server, or ARC since the update, let us know what you’re seeing. Please reply with any updates or questions so we can keep this moving.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.