· For many months, whenever I use Roon, playing music on my Naim devices has been terrible. Songs randomly stop playing, then at various intervals, start, and stop again. Or, skip songs, with sometimes minutes of silence until another song starts playing. I have Qubuz, and read there was issues, months ago, and you were working on resolving the problem, but this is no longer tolerable.
I have this same problem. Naim equipment, Qobuz, super unreliable performance from Roon. As described in other open cases, a track will start, hang, go to the next track, and then fail altogether. It will sometimes say there’s a problem with Qobuz, but when I play the same tracks directly from Qobus, using all the same hardware and connections, only skipping Roon, it works fine
Thanks for the report. Can you please confirm the exact model of the affected Naim device and firmware version? If you can, please let us know the exact local time + date + track when this issue next occurs, we will enable diagnostics for your account and check to see if the logging has clues.
Both, Naim Unity Atom, and Mu So, latest firmware. This happens all the time, however it NEVER happens if I am not using Roon. So, from the Naim or Qobuz app, this does not happen.
same for me. I can reproduce it 100% of the time now, so you could look for example at the time stamp of my previous response, or of this one, so 4:22pm PT today, for example, or any other log activity on my account for the past several days
Thanks for the additional information. While Qobuz did fix the CDN-related issues previously, we’re still seeing lingering CDN issues here and there, and are still in communication with Qobuz on getting these final strings tied up properly.
From a fresh diagnostic report, it appears that you may be in this small bucket, still experiencing CDN-related issues, unfortunately.
Specifically, Roon Server repeatedly requests block 850 of a Qobuz stream, literally hundreds of times across several minutes, and each request comes back with blocks read: 0 and download speed: -256kbps (a sentinel value indicating nothing was actually transferred).
The Qobuz CDN responds with HTTP 206 (success), meaning the connection isn’t being refused, but the data simply never arrives.
Could you see if any of the below troubleshooting steps help minimize the issue at all:
If you haven’t recently, fully sign out of Qobuz in Roon and resign/resync your account.
In Roon > Settings > Services > Qobuz, temporarily set the streaming quality to CD Quality (16-bit/44.1kHz) rather than Hi-Res. See if the dropouts stop or significantly reduce.
Check if IGMP Snooping or IGMP Proxy is enabled on the Orbi and/or the Hitron, disable if so.
Check if the Orbi has AP Isolation or Client Isolation enabled on any band, disable it.
If you can, test out setting up a VPN tied to your server machine, and set it to somewhere outside of your current location, and see if you’re able to reproduce the issue.
I performed steps 1, and 2, but the issue persists. I do not know if Orbi has 3/4 enabled. I looked but I couldn’t see anything. I do not have a VPN to try.
I can reach out to Qobuz, but as I have mentioned, when I stream from Qobuz or Naim apps, this does not happen. This is why it seems evident that this is a long, unresolved issue with Roon. Please understand my considerable frustration with this issue, which has persisted for half a year or more and is not acceptable, let alone for such a premium service. Please, we need to get this fixed asap.
We completely understand the frustration, and we’re sorry this has dragged on for so long.
The way Roon streams from Qobuz differs technically from how native apps and Qobuz Connect work. We have identified that the issue is on Qobuz’s CDN side - their Akamai infrastructure is failing to deliver audio data in certain cases, and we are actively working with Qobuz to get this resolved.
In the meantime, having you report this directly to Qobuz as well helps - the more user reports they receive, the more pressure there is on their end. Please mention that the issue only occurs when streaming through Roon and not via Qobuz Connect or the native app.