What kind of performance/speed issue are you experiencing?
· Other
Please try to reboot your Roon Server
· No, the issue is still the same even immediately after a reboot
Please try to reboot your networking gear (Router/Switches/etc.)
· No, the issue is still the same even after a reboot
Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?
· No, the issue is still the same
Does the issue happen on multiple Roon Remotes (controllers) or just one?
· Issue happens on multiple remotes
Router Domain Name System (DNS) change
· I was able to change my router's DNS servers but it did not help
What is the operating system of your Roon Server host machine?
· Linux Server (Ubuntu, Fedora, ArchLinux...)
Timestamp of issue occurrences
· no specific time, happens during any playback
Describe the issue
After the last roon server update, updates to the roon remote visual information can lag behind the audio by 10-20 seconds (i.e. a new track starts and the previous song image and metadata continues to display for 10-20 seconds, then eventually updates).
Describe your network setup
eero 7 mesh wifi, cisco workgroup switch, at&t 1 GB fiber, roon server on wired ethernet 10 Gb
We checked your account status and noticed that your Google Pixel 7 is running an older version of Roon (2.57), while your Roon Server has already been updated to version 2.58. This version mismatch is likely causing the connection issue.
Recommended Steps:
Update the Pixel 7:
Please update the Roon Remote app on your Pixel 7. You can do this via the Google Play Store or by downloading the latest APK directly from our downloads page:
If the Pixel 7 is not the device having trouble, or if the update does not resolve it, please try uninstalling and reinstalling the Roon Remote app on the affected device. This often clears up cached connection data.
Please let us know if this gets you back up and running.
All of the impacted devices are already on 2.58. Reinstalling and/or clearing the caches did not fix the problem, in fact, in some cases, it now takes 25-40 seconds for the metadata to catch up to the audio.
Can you please share a few examples of this issue, perferably using a screenshot? E.g. Roon shows that visual information dispays X when in reality it should show Y. Once we have this info, we can look over diagnostics to see if there are clues. Also, in case this is related to network congestion, can you please perform a full reboot of all your networking gear?
Not sure what a screenshot will tell you because it would just show a different songs progress bar with the previous songs metadata (and no way to tell what the new song is).
Ah, yes, and the bog standard ‘reboot everything’ response I expressly asked not to hear. Oh, and, yes, it made no difference other than causing a massive outage from all my perfectly functioning other networked devices.
Is there really no proper instrumentation in the app to tell what is going on? The reboot → reinstall app → reinstall everything ‘diagnostic’ is very very concerning for a commercial product…
Sure. If you look at the logs between 19:30 and 20:00 ET on 8 Feb 2026 you will see multiple instances of the overlapping and/or delayed playing and display of metadata.
Additional observation here. If the Roon Remote is in the playlist view, the icon for the next tune shows up immediately in the lower left of the screen after the current tune ends. The start of the tune is still delayed by 20-30 seconds. When the RR is in tune view, the entire screen takes 20-30 seconds to render and usually coincides with the tune actually starting,
I have gone ahead and enabled diagnostics mode for your account and what this action will do is next time your Roon Server is active, a set of logs will automatically be generated and uploaded to our servers for analysis.
I wanted to reach out because I’ve been keeping an eye on our servers, waiting for the aforementioned diagnostics report.
For some reason it is not reaching our servers, even after I tried re-enabling diagnostics on your account. I also ran a quick test and I was able to submit a similar report from my setup here, so something else is going on.
So we can move forward, I was hoping for now you could use the directions found here and send them to our Logs Uploader Service and let us know after, thanks!