Does the issue happen with local library music, streaming service music, or both?
· *Only streaming* music is affected.
Please select the streaming service(s) with which you're encountering playback problems.
· Qobuz
Have you tried logging out and back in again to your streaming service in Roon Settings?
· Logging out and back in had no impact, the issue remains
Do you have an approximate timestamp of when the issue last occurred?
· Recurring issue, it’s been worse past whole week worse
What are the make and model of the affected audio device(s) and the connection type?
· RoonServer running on M1 MacMini ethernet connected to Orbi router, Bluesound Powernode v2
Describe the issue
All 192/24 tracks from Qobuz are skipped at about 15-18 second mark, next tracks load and they skip as well until there are too many failures. I have no issues playing from my Roon Ready Bluesound Powernode with the same streaming service.
Describe your network setup
Wired ethernet connection from Orbi Router whichis int turn wited to Verizon FIOS 1GBps router. Bluesound Powenode ethernet connected to Orbi router as well.
Thanks for your message. I’ve activated diagnostics mode for your account and what this does is upload a log set to our servers for review. Looking over the logs, I can see that the issue is happening when your Roon Server tries to download the track from Qobuz’s servers, it appears that there is a drop in download speed.
We have seen users have a better experience in the past if they change their Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS. Can you please give this a try and let me know if it helps?
I appreciate the prompt response.
I changed the primary DNS to cloudflare on my Verizon FIOS G3100 router, but the exact same issue prevailed, anything 192/24 stops playing exactly around 13-15 seconds and skips. Meanwhile I tested the same tracks from Qobuz through my Bluesound Powernode with no issues.
I’ve had this setup for quite sometime and only had minor issues like these but last week it became impossible to play 192/24 tracks altogether.
Kindly look into the logs post DNS changes as you recommended and let me know what else is happening.
Thanks for giving that a try! We were able to review a fresh diagnostic report and continued to see failures around Qobuz and authorizations when attempting playback.
If you head into Roon Settings>Services>Qobuz>Edit can you confirm the proper file format has been selected for playback resolution?
Another area to explore could be your Mac firewall - if you temporarily disable it, do you run into the same issues?
If you haven’t yet, I’d also safely stop Roon Server from running, and then power cycle both your Mac and your router.
We have seen some of our users on Sequoia have these problems solved by making sure you’ve toggled on Local Network access for RoonServer in System Settings → Privacy & Security → Local Network. If it is already switched on toggle it off and the on again. Sometimes the toggle doesn’t accurately show if it is on.
It was on for both RoonServer and Roon, I toggled it, rebooted, audio zones reappeared, but keep disappearing and reappearing. The log continues to show connection errors. Meanwhile the 192/24 tracks keep skipping, that error has stayed consistent.
Thanks for the additional information. Based on a recent diagnostic report from your Roon Server, it looks like you’re running into a known Qobuz issue related to tracks in your library being deleted - here’s the tracking thread for this issue:
Please reboot your Mac after performing the toggle - that should stabilize things until you open and use Roon again. Unfortunetly this is another known issue related to a recent Apple update with Sequoia.
We’re seeing repeated 500 Internal Server Errors in logs, which indicates that the Qobuz API encountered an internal issue while processing the request. This could be related to the issue I’ve shared above. We’re seeing the sync_token in the API requests for Qobuz tracks might be expired, corrupted, or invalid - again potentially relating to the same issue above.
An important next step in testing, if possible - do you run into any issues when streaming the same formatted content outside of Qobuz? Do you have a local 192/24 file you could test?
More than 90% of the 192/24 tracks I play are outside of my library, getting streamed directly from Qobuz, I do not have any local ones to test at this time. This leads me to believe it’s not a library issue since the error I’m getting on the RoonServer log is constantly the same and directly related to RaatSender prebuffer and poor connection to the amp being lower than minimum threshold.
Additional problem I have faced repeatedly is scrolling any track, even lower resolution ones, they tend to either take more than 10 seconds to catch up or fail entirely.
As mentioned earlier and in my last post, I did a reboot after toggling the local network settings to no avail. When I loaded the Roon application on the server machine, the audio zone disappearing problem appears to go away though.
Is there any chance we can escalate this since I’ve been suffering with this predicament for quite some while now.
The Qobuz-related issues have already been escalated, and many have been resolved. Are you still experiencing any trouble?
We’ve also seen that updating to the latest macOS Sequoia 15.3 has helped many users with similar issues. If you haven’t updated yet, it might be worth giving that a try and seeing if it improves things! Let us know how it goes.
I’ve always been at the latest versions of both MacOS (15.3) and RoonServer as soon as they are released. I’m still experiencing massive dropouts for each and every 192/24 track I play, additionally each time I scroll forward in any track, I’m getting crashes, even for lower resolution tracks.
My RoonServer has effectively been unusable since we started this thread, things have gotten worse with connection issues to audio zones propping up even after multiple reboots.
You’ve mentioned this issue had been escalated but sadly I haven’t seen any improvements. Kindly transfer this issue where I can get prompt resolution to a myriad of problems plaguing my daily listening for months.
After escalation, the team has thoroughly parsed available diagnostic logging from the previous and current logged period (about the last four weeks cumulatively).
Unfortunately, the same two patterns emerge nearly anytime high resolution content plays on this network:
Bandwidth allocation to RoonServer isn’t sufficient to download the 192/24 file from Qobuz in time to distribute it. More specifically, the network speed allocated to Roon is dropping after requesting the file from Qobuz’s servers. With smaller files at 44.1KHz and lower, Roon can recover the download.
Audio distribution between networked endpoints fails due to accumulated sample dropouts. The network connection between RoonServer and endpoints doesn’t deliver packets as expected, intact, or within the allocated timeframe.
WiFi interference or overactive managed network software (sometimes in concert) cause the vast majority of these issues on this forum. I recommend verifying that the Orbi router has IGMP snooping and multicast forwarding enabled. If you have any mesh nodes attached to your Orbi setup, make sure you’ve followed our best practices here:
Qobuz delivers content via a separate server to their native service than to Roon, which relies on the Qobuz API. This is a separate network pathway. Roon’s uncompressed protocols will usually expose any latent wireless interference or packet re-routing within the environment, precisely because so much PCM information is distributed.
We generally recommend simplifying the network and building back components one at a time, prioritizing ethernet over WiFi, and testing from the System Output of the RoonServer itself. We’re here to support you during troubleshooting.
I haven’t been using wifi on the RoonServer box, it’s ethernet all the way, the main orbi router is directly wired to my FIOS router, the Mac mini is directly ethernet wired to the orbi router, so we can easily rule out any wifi related interference or latencies.
This issue started recently, I have been in the same setup for years and only experienced crashwhen scrolling forward 192/24 tracks, that I could ignore, but not being able to play these particular tracks is unacceptable.
We’d like to take another look at diagnostics from your machine, but it doesn’t appear to be online at them moment. Can you please let us know after you use Roon again so that we can re-check for the diagnostic package? Thanks!
We’re seeing similar stoppages in audio due to poor network conditions.
Too Many Dropouts
The log shows [zoneplayer/raat] too many dropouts. stopping stream, which typically means that Roon lost data packets too frequently and had to halt playback.
Slow Media Warning
The line [Broker:Transport] [zone Bijli Ghar] Track Stopped Due to Slow Media indicates that Roon determined the data was not arriving quickly enough to maintain playback. This could be due to a slow or unstable network connection.
Disconnection of Audio Stream
The log mentions [raat/tcpaudiosource] disconnecting, which suggests that the audio stream to the Bluesound POWERNODE 2i was interrupted, possibly due to network congestion or instability.
Bandwidth Allocation Changes
Several lines mention bandwidth allocation changes (e.g., allocated bw changed from 51200 to 0 kbps), indicating potential fluctuations in available network bandwidth, which could cause playback to stop.
What about your endpoints? Check the POWERNODE 2i’s Connection. If it’s on Wi-Fi, try switching to a wired Ethernet connection to rule out wireless instability. Temporarily connect the POWERNODE 2i directly to the router via Ethernet and see if the issue persists.
If possible, in Roon’s Device Setup, increase the “Resync Delay” for the POWERNODE 2i to give it more time to recover from network hiccups.
Bluesound Powernode 2i device has always been directly wired to the main router, there’s no delays when I play 194/24 content directly through it.
I’ve tried resync delays starting from 10ms to 2000ms to no avail, logs should clearly indicate that.
Logs indicate that both 1) the download to RoonServer from Qobuz and 2) the distribution to endpoints across the network are encountering regular sample loss.
You’ve mentioned Audio Zones disappear and reappear intermittently in your Device Settings page. Diagnostic logs corroborate that RoonServer is losing the handshake with these endpoints before it rediscovers them via a new multicast device announcement cycle.
We understand your resistance to troubleshooting the network. However, the evidence available suggests Roon can’t reliably pass content to nodes across this network, and it does not have the bandwidth to download the 192Khz files during distribution to multiple Zones. The server itself and the Qobuz API show no signs of malfunction.
There’s not a clearly identifiable performance fix for development here - unfortunately, the most expedient step is to troubleshoot the network pathways involved.
We’re happy to help and can make some suggestions. The first step is to test playback to your system output on any Roon Remote. Restrict Qobuz to the lowest sample rate in Settings → Services → Qobuz and then increase the sample rate until you encounter errors.
If you look at the earlier troubleshooting done in this thread, you’ll notice there was never any resistance to looking into network issues, we went through firewall settings, DNS adjustments, and throughout I’ve been stressing that the setup has always been simplified, straight wired ethernet for each component. All my network queries yield about 1Gbps up/down on speed tests consistently.
As per your recommendation, I have tested 192/24 tracks through the system output, starting from 48/24 all the way upto 192/24, please check the logs for these and report back promptly.
I know this is not my network as I constantly play 192/24 tracks through various channels and streaming platforms within my setup especially through the same Mac Mini that hosts RoonServer and independently for each component like the Bluesound Powernode without any dropouts whatsoever.
The disappearance of audio zones occurs soon after a reboot, it goes away when I restart RoonServer manually. Kindly let me know how this can be fixed.
