To add: I don’t think we are at the point of spending a lot of effort on chases, yet. By opening a support case, the staff can gather your Roon logs and analyze them. That’s not a lot of effort, certainly preferable to getting annoyed by issues, and maybe they find something, either in Roon code or elsewhere. Then see about whatever the next steps might be.
Sorry, @Tom_Harskamp, it’s not as simple as that, you need to open your own support request. By doing so, your request generates both the post in Support and a ticket in Roon Lab’s internal ticketing system for the support team.
So to equip the Roon Technical Support team to assist you directly, please follow this link to provide the details of your case to Technical Support: Technical Support Request
Respond to the prompts there to ensure that you’ve performed basic troubleshooting and to ensure Technical Support has the full details necessary to expedite Technical Support’s investigation into the case.
Your responses will create a ticket on Roon’s support tracking system and auto-generate a Community thread in the appropriate section.
Because this Community thread will be in a public forum, please do not include any personal information, such as your email address, postal address or telephone number in your submission.
Thank you.
1 Like
I’ve made my own ticket, and honestly, I’m not holding my breath. From what I’m seeing here, Roon is on a fast track to losing a lot of customers. Keep going like this and the whole platform is going to crash and burn.
I’m extra salty because I’ve thrown stupid amounts of money at this setup—NUC, linear PSU, upgraded switches with their own linear PSUs, fancy Ethernet cables, the whole audiophile circus. And after all that, Roon basically shrugs and goes, “Yeah… no. I’m not loading. I’m not playing your music. Deal with it.”
1 Like
Well, personally, I use bog-standard unmanaged switches with their wallwart PSUs and plain Cat6a cables. I tried a simple managed switch once and quickly replaced it…
Network Bizarreness with a TP-Link SG108e Switch - Support - Roon Labs Community
2 Likes
This is assuming something changed in the setup and there was no change.
Also i checked speed of network. all switches are doing what they supposed to do.
Hey Tom, I wont assume, but there is an update in the last 48 hours (and a much bigger one on the 20th) I am sharing the pain - but since Updated - seems better (could just be the reboot) but worth the update!
This worked for me. Had the same issues with my NUC gen 8 i7. I already cleaned all the dust out and rebooted several times. After a reboot it seemed fine for a day, but afterwards the slowing down occurred again. I was thinking about a SSD issue or a cooling issue.
But this update yesterday seemed to have resolved everything, Rock functioning as expected.
Now i reboot nuc daily or even before any listining session. Then it is okaish fast enough. Didnt test much after the last update. Hence I always reboot now. Ill try not reboot comming days.
Same kind of problem with Roon on my Inuos (Zen mini mk3). 
It’s been happening for the couple of weeks already. To avoid this I reboot my Nucleus every second day.
Since last update it seems I have no problems anymore.
But with what I’ve red.
Can we rule out a database related issue with alle that rebooting by everyone and running fine (for a short while) after rebooting?
I’m having the same problem.
I’ve been using Rock on my Nuc7i3 for a while now. I’ve noticed that even local tracks are switching with a noticeable delay of 3-5 seconds. Roon Radio starts playing after 15-20 seconds, and tracks from Qobuz take even longer to switch.
The library is new, with about 20,000 tracks plus Qobuz.
At the same time, ARC works perfectly, and Qobuz works well on its own.
The only thing that helps is restarting the roon server software on the Rock webpage once a day. It’s a shame there’s no scheduled server shutdown feature; that would be somewhat helpful.