Welcome back to the forum. Can you provide more details on when the cutting out is happening, specifically whether it is between tracks or in the middle of a track? Please share the exact local time, date, and track when it next occurs. Does it happen with multiple zones or just one in particular? Is the Roon Server connected via Ethernet?
Tidal cuts out at random times. It stops in the middle of a track. Of course, I updated to the latest versions, did hard reboots, and everything is fine now. Roon had a tough time finding the audio zones but they are working normally now.
Roon has been losing connection to Meridian 218 zones. I will record the next time it happens.
The intel nuc running Roon Rock is hardwired to the network as are all the zones which include four Meridian 218s, a Meridian ID41 in a 861v8, and an Eversolo A6.
The server is connected via ethernet to a switch which is connected to the router. The 218s are connected to the same switch. We were playing the Project Hail Mary soundtrack from Tidal. It cut out after 30-60 seconds of play and the zone disappeared. The zone comes right back. The zone is a pair of 218s. This occurred at 7:55 AM and I tried again at 6:05 PM and it happened again.
Thanks for sharing the above timestamps! I was able to review a fresh diagnostic report surrounding the failures you’ve mentioned.
The logs reveal a series of Network Reachability and Output Buffer issues that caused the playback to stall and eventually skip tracks. Around 18:06:21, the log begins reporting that the audio stream from Tidal is not arriving fast enough to keep the playback buffer full.
The system then hit a critical failure while trying to play the track “I’m an Astronaut”:
[Living Room] [zoneplayer] Output State: Stalled
[zoneplayer/raat] Error during playback: System.Exception: unexpected transport state: Stalled
Just before the stoppage, there are several “Slow Connection” warnings and DNS-related traces:
The log shows FTMSI-B (Roon's file transfer system) reporting accessTimeOut:True for several Tidal blocks.
The server was attempting to fetch data, but the response times from the Tidal servers were exceeding the allowed threshold.
Based on the above, let’s see if any of the following troubleshooting steps help:
Reboot Network Gear: The "Stalled" state and "accessTimeOut" are classic symptoms of a router or network switch that has a full NAT table or a hung process. Power cycle your router and any switches between the Roon Server and your Living Room device.
Check DNS Settings: Since the log shows timeouts fetching Tidal blocks, try changing the DNS on your Roon Server (or your router) to a faster provider like Cloudflare (1.1.1.1) or Google (8.8.8.8). This often speeds up the initial "handshake" Roon makes with Tidal's servers.
Wired vs. Wireless: If your "Living Room" endpoint is on Wi-Fi, the logs suggest it is losing its connection to the stream. If possible, test with an Ethernet cable to see if the "Stalled" errors disappear.
Tidal Streaming Quality: If your internet bandwidth is fluctuating, try lowering the Tidal streaming quality in Roon (Settings > Services > Tidal) from "Max" to "High" temporarily to see if the buffering stops.