Hi @Justin_McMurdo,
Thank you for the report.
We’ve activated diagnostics on your account to generate an automatic log report detailing any errors in RoonServer. Here’s what we can conclude:
In logs, RoonServer is reporting sample dropouts while attempting to stream to M10, and before that, dropouts with a group of non-Roon Ready Zones, as well. These dropouts are within the network, somewhere between RoonServer and the affected endpoints. The symptom would be a popup message staying something like “Too Many Failures,” but the Zone wouldn’t disappear.
Upstream of your RoonServer, the audio stream download from Tidal’s servers is timing out as well. This is most likely a result of bandwidth allocation or active throttling/filtering on the part of some network hardware or software. How is your RoonServer machine connected to the internet? Is it hardwired to the main upstream router?
We can also see logged failures with grouped BluOS-capable Zones on RoonReady that are consistent with an issue that the Bluesound team is co-investigating with Roon. We’re close to pinpointing the issue and you can expect that our Partners team and Bluesound will implement a solution from one side or the other soon. Updates on the resolution will eventually be posted here: NAD/Bluesound Grouped Zones out of sync, stopping playing, and/or skipping tracks [Investigating]
The symptom of disappearing and regenerating Zones is more consistent with a RoonServer crash loop. Do you ever encounter a “Waiting for RoonServer” screen or any other indication that the server is offline when these Zones disappear? Do you encounter slowness, hanging, or freezing in the app at this time?
Do you have a large volume of custom tags applied to your library, and in particular, are you applying the same tag to a large percentage of your Roon library?
Please also provide a brief overview of your network hardware and how its connected, per the template the moderators provided above.
We’ll keep an eye out for your response. Thank you!