Server
The server is a Synology DS923 with 32gb of RAM, Roon package is installed on the internal SSD array and music stored on the HDD array.
Library
5162 ALBUMS
52537 TRACKS
Network
Freebox router, the Synology is directly connected to the router.
3 Orbi 750 repeater that operate the wifi network in AP mode.
More info
8 zones but playing only on 1 device
Synology, Core, remotes rebooted
Last Roon versions everywhere
no skipped files
Issue
This problem happens when I play music from my Mac with the system output, when I stream music to a device on my network (Fiio SR11 for instance). The music stops or pause randomly, a pop-up appears āwaiting for your Roon serverā.
In the Synology task monitor, The Roon process maxes out one core of the CPU, sometimes 2 (specifically the dotnet subprocess).
After a moment (from 1 second to 2 minutes), doing nothing the music restarts or I can press play music again.
From my perspective, I really can relate the dropouts to the CPU occupation. Screenshot taken just now, Roon is only streaming a MP3 320 to the Fiio SR11, no Muse adjustments.
How many albums do you have that are unidentified? I have a set up that is similar to yours, but with 5174 albums. Only 152 are not identified and I never see this problem.
You mean analysis speed? Whatever setting I use (throttled, 1 core, 2 coresā¦), the CPU occupation percentage is the same, throttled, I just hit 50% right now. But nothing broke.
So your system is freshly setup and is still analyzing the library or you set it to analyze on demand? In any way, a running analyzing process will occupy your CPU what you identified as the root cause of your issue. Let the analysis process finish with your library before listening will remove the CPU load generated by it. Set both related settings to off for testing might give you insight too about a potential impact on your issue.
PS: With only two cores on the CPU, Roon playback, Roon analyzing and the rest of your NAS system running too, potentially with an active antivirus that wants to scan files on access, you might reach the limits of your CPU quickly.
See my added PS on previous post. It is unclear to me from your answer what your two settings regarding analysis are set to and if analysis is still happening in your system. Again, set them both to off for testing (just to make sure).
Your NAS OS and its services get updates too that may impact performance. Roon may demand more performance after certain updates. The issue seems related to file access which may trigger quite some activity not only from Roon but also from the NAS and its services. We donāt know the details of your NAS setup, what services might be running and so on. If the system runs out of resources this will impact running processes and as far as the CPU goes, it has only two cores ā so it might run out of resources more often (quicker) than a 4 core CPU. If you happen to have a decent PC/Mac (more potent CPU than the NAS) you can use as Roon Server temporarily to test, you can use that to compare to (see if you run into the same issue).
Yeah, I just shut down a docker container which seemed to be faulty and now it seems to be working without any hicups, but still reaching high CPU occupation regularly, Iām gonna think about moving to a more powerfull server dedicated server for Roon maybe.
Your NAS is more than powerful enough as a dedicated unit, at least with not so many unidentified files. I recommend trying to identify some of your 555 unidentified albums if you can. If you canāt, then, yes, you might possibly benefit from a more powerful server.
