Regular dropouts during streaming and internet radio in Roon (ref#VLXGGE)

Support
63

Hey @Eric_Besemer,

Thanks so much for your long standing patience here! We further reviwed your Rhein z1 server, and saw it has ~7.7 GB of RAM, which is plenty, so this is good news: your hardware is not the problem, and you don’t need a new machine.

Here’s what the logs show. The dropouts are not caused by Tidal, Qobuz, or your internet. They happen on the Roon Server itself (your Silent Angel Rhein). The server repeatedly freezes for long stretches, sometimes 15 to 30 seconds, while it cleans up its memory.

During each freeze it can’t send music to your Meridian 218 (so the sound cuts out) and it can’t talk to your iPad (so you see “connection lost” or “choose an audio zone,” especially the moment you scroll or change a track). This matches exactly what you’ve described, and it’s why reinstalling only helped for an hour or two, the problem slowly builds back up.

The good news is that our team has been actively improving how Roon uses memory, and the newest Early Access builds directly target the behavior we’re seeing in your logs. So here’s what we’d like you to try:

  1. Join the Roon Early Access program and migrate your server to the Early Access build. It's a separate install from the normal version, the full step-by-step is here: https://help.roonlabs.com/portal/en/kb/articles/roon-early-access-program . Please back up your database first (the guide covers this). If you hit any trouble migrating on your Rhein, tell us and we'll walk you through it.
  2. Once you're on the Early Access build, set Settings → Setup → Background Audio Analysis Speed → "Off" to keep the load light while we test.
  3. Use Roon normally for a day or two, streaming, radio, and scrolling as you usually would.
Then let us know:
  • Does the music still cut out, and does the app still lose connection when you scroll or change tracks?
  • If it does cut out, please post the exact date and time (CET) so we can pull fresh logs and see what the server was doing at that moment.
We expect a clear improvement on the newer build. If anything still drops, the logs from that point will tell us exactly what's left to fix.

If you are not interested in migrating your Roon Server to Early Access, these optimizations should be moved into the next full Production Roon update, if you’d rather wait until this is launched.

We know this has dragged on, and we really appreciate your patience and all the detail you’ve provided. :+1:

64

Hi,
I followed your advice and installed the program.
I’ve been listening for an hour now, and my (preliminary) conclusion is: no glitches!
I’ll keep you posted.
Regards, Eric

65

1043 cet drop-out

11.23 again

66

13.27 same issues again

67

17.36 again

68

Same problems as before

18.16 drop out

69

Hi @Eric_Besemer,

Thanks for the reply! Based on your admin, it looks like you’ve only installed Early Access on one of your remote devices, while your Roon Server still holds the Production version of Roon.

Since you’re running Roon Server on a third party machine, it might be best just to wait until we push these updates over to Production, in which your normal auto-update prompt will bring the optimizations to your server.

In the meantime, I’d revert your Roon remote device to the Production version of Roon, and perform a daily reboot of your Roon Server until you recieve the update prompt.

Thanks for your continued patience here!

70

Do I still have to keep reporting malfunctions