Thank you for that @Mel_Martin - we’ll share the information with development team, and should have more insight to report back soon. ![]()
Hey @Mel_Martin,
Additional analysis from logs unfortunately still didn’t point to any obvious errors - but our development team has two additional questions for you:
- Do you only see this issue when attempting to access a secpfiic genre of album? In your case, it seems like you run into sluggish behavior when trying to navigate to a classical album. Do you see this no matter the genre?
- We see you’ve recently tested using your Macbook as a Roon Server - if you restore your same server database from your Nucleus to your Macbook, do you observe the same slowness when using your MacBook?
We’ll be on standby for your reply and results - thank you! ![]()
Any kind of music, local or even from Tidal.
I’ve never consciously used my MacBook as a server. Or had any desire to.
Hi @Mel_Martin,
Thanks for getting back to us with those answers. For testing purposes can you try running your Roon sever on your MacBook and see if you still experience the slowness? It will help us determine whether the issue is the Nucleus itself or something more widespread.
I have no idea how to do that. Wouldn’t it be better on my Mac Studio? Does this mean moving around 1300 albums someplace else?
Hi @Mel_Martin,
Either machine would work, ultimately as @daniel mentioned we’re hoping to better understand the source of the issue.
Here’s more info on what the temporary migration process would look like:
Basically, you’ll want to save a fresh backup - open Roon Server on your Mac and restore the backup you’ve created. You’ll want to add the same storage locations of your local library as well, the article breaks down each step in more detail, but certainly let us know if you have any additional questions along the way.
Thank you!
This looks time consuming and risky. Let me ask if anyone else using Roon has seen these same issues?
2 posts were split to a new topic: Roon Sever slowness
Hi @Xekomi,
We don’t have a fixed list of domains we use, as they can change over time. However, you can check your server logs to see where requests are being made.
Let us know if you need any further guidance!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
Roon still slow… every morning when I build a playlist after I add a few things Roon freezes for up to a minute. Then I can resume. I’ve reported this for months. I’ve sent logs, videos, etc. Others have reported this behavior. Seems to me one of the simplest things for a music system to do is open an album and play it, but Roon can’t reliably do this. It happens every morning. I have a GB Ethernet network, and nothing I have on it chokes like this. My Roon server is a Nucleus+. I still have a Bluesound Vault as a backup and it never fails to work. I wish Roon would consider this a priority to solve. It happens using both of my Macs, and any iOS device, so it’s somehwere on the Roon end.
Hi @Mel_Martin,
Thank you for your ongoing patience. We’ve enabled verbose diagnostics on your account that should pin down the issue - please restart your RoonServer twice to enable these diagnostics to take effect. We should have a more precise sense of the problem shortly thereafter. Thank you!
OK… just reboot… then reboot again? Will do it tonight… thanks
OK… went ahead and rebooted twice just now… hope it helps…
Hey @Mel_Martin,
Thanks for performing the dual reboot! Let us know the next time you experience the same sluggish behavior, as well as the name of the track playing or attempting to load - that would be helpful. Thank you! ![]()
Sure. It happens every morning when I create playlists.
7:53 AM Mountain time it hung trying to load Anna Lapwood album ‘Luna’. This was an odd one as app became unresponsive… clicked around to get things going again, and as usual after a glitch, everything worked fine. It will load now until tomorrow AM. Further reports coming.
Hi @Mel_Martin,
Please restart RoonServer once more on the Nucleus+ from the WebUI - it looks like the diagnostic bit we enabled for verbose logging still needs to be activated, which requires two back-to-back restarts.
We’ll know more shortly! We should have everything we need at this point. Thank you for your patience.
I did restart it twice yesterday back to back and from the Web UI. so you want me to start twice again, or just once?