Does the issue happen with local library music, streaming service music, or both?
· *Both streaming and local* *library* music are affected.
Do you encounter any playback errors with the "System Output" Zone?
· The System Output has the same problem as my other Zone.
Is your RoonServer machine running MacOS 15 Sequoia or above?
· I still can't see my endpoints as available Zones.
Do you have a complex network setup?
· I have a *mesh network* with devices connected to multiples points
Your local network might need some re-arranging to support Roon.
· None of the suggestions have helped me. I'd like to submit a support request.
What are the make and model of the affected audio device(s) and the connection type?
· MacBook Air, McIntosh MSA5500
Describe the issue
There seems to be a problem with the play queue. Does every zone have a separate queue? When I change output (from my McIntosh amp to System Output) it looks like the whole queue changes. Sometimes when this happens I think there is a bug. For example, it says that there are 10 songs in the queue and it’s 1 hour left, but there are no tracks to be seen in the queue. And when I press play, nothing happens. If I change the output there is a different queue, still empty, and it can’t play any audio here either. The song doesn’t even start
Thank you @BlackJack! Now I understand the zones and different queues better.
I don’t know if it has to do with the play queues, that was just my guess.
But this has happened a few times now. That when I press play nothing happens. I can use the interface, browse and everything, I just can’t play music. Not in any of the zones. And the queues look like the screenshot. It’s cleared, but at the same time it says that there are several tracks queued
Thanks for writing in and welcome to the community! We’re excited to have you here - @BlackJack is 100% correct around the queues being linked to the specific zone you have enabled.
Do you get a specific error message when this happens?
We’re having a tough time connecting to your Roon Server, if you could, please reproduce the issue, share the track name you have queued up, and we’ll enable diagnostics to take a closer look.
No, there’s no error message. It’s like I don’t click the play button. Nothing happens. I’ll share everything the next time it happens. Last time was around 6 pm (swedish time) and the track I tried to play was Melody Gardot “Morning Sun” in one zone and Map.Ache “Seis” in another
It’s interesting - from a fresh diagnostic report, the track “Seis - map.ache” began playing, buffers were filling, and the endpoint entered the Playing state. But we then see the System Output zone receive a command or event that transitions it to Stopped, causing Roon to cancel pending sleep, dispose of audio streams, and call end_stream.
From logs, we’re not seeing any error or fault shown - playback stops and immediately restarts with the same track, as part of a larger playlist or queued action.
As a good next step in troubleshooting, could you test out setting up a hardwire ethernet connection and see if the same playback situation occurs?
Ok, pretty strange. It doesn’t start playing again, however many times I press play, and in every zone.
I will try that. The track I refered to was on my harddrive though, and I played it through the system output. But maybe it goes through the network anyways?
If you try to scroll up/down on the queue screen, do the tracks then appear? What happens if you try to restart the Roon UI aspect (while leaving the RoonServer instance in the task bar active), does that correct the issue, even temporarily?
@noris Hi, tried scrolling up/down when the problem happened again today. Didn’t solve it.
I restarted the UI and quit the whole app up in the taskbar and after that it worked again! The queue came back.
So hopefully, as long as this problem doesn’t happen too often, this could be an alright solution
Diagnostics show RoonServer receiving network errors from Tidal’s servers.
If you’re using any VPN, try disabling it or at least changing the geoIP if you encounter Tidal playback failures.
I would additionally ensure that the DNS server assigned is reliable, to ensure Tidal URLs can resolve without issue. This is largely procedural - the 500 error returned from Tidal mostly suggests that their own CDN for your geographic region was experiencing a service disruption that they promptly resolved.
Local library playback failures may result from RAATServer crashes if MacOS severs Roon’s access to the local network via the network interface. This can happen on the System Output, which Roon reaches via the loopback. I’d ensure that Roon has local network access on the MacOS Privacy&Security page.
We can mark this thread resolved for now, but please reach out if anything else pops up. The thread won’t auto-close for several days.
