Thank you for your post. We’ve pulled diagnostic logging to investigate the dropouts you’ve described. Here’s what we can conclude:
While Roon is distributing audio to the Bluesound and Arcam endpoints, both as a grouped Zone or independent endpoints, two things are occurring in logs.
First, the buffer from Tidal encounters bandwidth restriction and slows down. RoonServer isn’t receiving the file fast enough to distribute it to the endpoints because it doesn’t have sufficient network connection to Tidal’s servers.
Second, the endpoints report sample dropouts during the stream. Packet loss occurs in between the internet, RoonServer, and the Bluesound/Arcam endpoint, and it eventually overwhelms the stream. This is downstream evidence of the bandwidth issue with buffering described above.
How is RoonServer connecting to the internet? Please list any hardware and software involved, including network switches, access points, mesh nodes, and second routers.
Roon server is on a mac mini, wired corrected to a switch which is connected wired to the router.
both end points are wired connected the arcam to the same swith, the blusound directly to the router.
A simple but often effective next step here would be to bypass the switch temporarily. See if you can get a direct ethernet connection to both your Roon Server as well as your arcam, reboot the router, and see if you can reproduce the issue.
If you can, share the name of track you had the issue with and we’ll take another look. Thank you!
I am having similar issues since the most recent update. I have 1GB fiber to the house which measures close to advertised speeds. I also have a very high performance in-house network with wired connections. It is a red herring to focus on your network (IMO), this is an issue which has arisen since the last update and is clearly a defect introduced into the Roon platform. The sooner Roon takes this as a bug rather than a customer config issue, the sooner it will be fixed.
Additional information - the problem grows worse the longer it’s been since a cold restart. This is often manifest as a long delay between the start of a new track on a playlist - particularly the new Smart Playlists.