The same issue everyone seems to have since the update. Extremely slow to open, to navigate, to search, to start playing, stopping during songs. Never had any issues before. Using multiple devices as remote: iphone 14pro, two ipad mini’s, two windows 11 devices. All experience the same. I am now unfortunately just stopping using Roon and going directly through the Naim app to my mininmserver and Qobuz again, but am eagerly waiting for a fix.
Frequently rebooting is no help.
a sidenote: I read mentioning that this issue is not affecting many users as not many reports are logged in this forum. I strongly disagree with assuming this. I for one usually don’t complain online if I see a similar problem already addressed. I do now, as I also read the support people asking for logs.
In your case, the machine itself might be the problem as a bit of increasing demand in computing power from roon´s side might cause the CPU to reach its limits. That can happen surprisingly quickly with a new software version or a growing collection.
As far as I know, your Synology is running an Intel Atom CPU introduced roughly 10 years ago. That’s far from sufficient for current roon versions. I experienced similar issues earlier this year and have sent my outdated Celeron-powered NAS to retirement although its CPU was about 2.5-3 times faster than your Atom when it comes to roon-relevant benchmarks.
Give roon a try on a windows computer or a powerful current NAS model. I am sure the user experience will be different despite some cloud search issues.
As much as I appreciate the time and effort you took for your kind reply, I kind of anticipated this line of thought. I disagree, it worked enormously well before the update, the cpu is hardly used and the 8gb ram is more than sufficient. I am not convinced my issue is anything else then everyone else’s.
I would not have suggested this explanation if I would not have been experiencing exactly the issues you are describing half a year ago. Back then it was related to a build version no-one took notice of. Everything had been fine and smooth before and then everything got slow and sluggish, interrupted and delayed. I also had 8GB of RAM which was more than enough, and did not notice CPU coming to its limits. But it did.
Solely replacing the NAS for a model with a more powerful CPU solved all problems and with build 1354 today things seem to be even faster than before.
If I play the same very heavy song (local by the way), and turn off Muse effects, my normal CPU usage drops to insignificant levels. Which is why I am not convinced my setup is the culprit, but the update is.
There clearly is a performance issue currently with the latest update that affects some people - many threads about it, and many of those with non-constrained hardware. However, it doesn’t affect everyone
Same here, with a NUC7I7.
Almost unworkable. Takes more than 30 seconds to analyze a track, although it was already analyzed during import. Swiitching between tracks with different resolution (eg 16 bit to 24) there is a gap of at least a minute before starting playbakck again.
I don’t believe it has anything to do with your hardware. It surely has something to do with this update.
I am not saying the update is innocent both in terms of bringing network/cloud processes of some people to their limits as well as demanding more computing power. Was just sharing my experience that in the past it happened before that a new version might bring an underpowered CPU to stutter and fail.
Monitoring CPU usage while streaming would not necessarily be revealing problems of the CPU reaching its tipping point when performing database operations. Although I wonder if processing speed of x0.4 might not be a hint that reserves are thin. Back then my system was also capable of playing/transcoding a stream even heavier than yours but would nevertheless stutter when skipping, filtering, searching or alike. As far as I understand, roon is utilizing separated cores and threads for separated operations. And single-thread or peak computing capabilities are particularly the problem of older Atom/Celeron CPUs.
As I said, appreciated and an upgrade is in the long term plans, because I echo the thought my system is getting old. Not necessarily now though and my current cpu roon usage is 4%, not 40. That was just for the stress test with a heavy local file with convulsion on, which I never use. At the moment, the issues seem related to what others are experiencing.
Hi @RexManning,
Thanks for your patience as we worked through the queue. Sometimes this problem can be solved by rebooting twice in a row. Please try that and let me know the results. If that doesn’t solve your slow-down issues we will activate diagnostics on your account to investigate further.
Thank you Daniel. The reboot trick I tried a couple of times at your teams suggestion earlier on, to no positive effect. The fix you made a couple of days ago does seem to work, everything is much more like before the update. Thanks again, Steven
