Fellow user here. The first thing to try is to turn off Audio Analysis, leave it off, and see if the crashes continue. Are you using Roon on a general purpose machine, or, one dedicated to running it? If it is a general purpose machine, I would check to see if the time frames of Roon stopping match any other system processing events, like backups.
BTW, If you are on a trial with a large library, I always suggest to turn off Audio Analysis, anyway. That is only used to create a waveform and for volume leveling, it is not for identification. I personally, only use ON Demand analysis which will just do the track you are about to play as I never use volume leveling.
It’s the software, I guess both crash though? I didn’t check to see if a process was running but it seems to go through a full and long start-up process after it. That said, it’s not crashed since disabling the audio analysis.
My new problems appear to be high memory usage (should it be at 2.5GB, and I’m sure that’s going up) and me experiencing some pops/dropouts on playback of 24-bit (I don’t get any dropouts in foobar2000 or other software). So those bits might make me reluctant to go from trialist to subscriber… I definitely think dropouts and a huge memory dump would be a no deal. Or are there solutions there?
(back to Crocs on my asymmetrical isolation feet!)
No good ideas, I’m afraid. It sounds like you have the all-in-one core+UI app running. You might try the separate RoonServer download as the core, so that the app with the UI is only the “remote control”, even if they’re running on the same machine. My thinking is that an OS will often treat an unattended UI application as closable, depending on power saver and screen saver options. So maybe the UI is being closed by Windows, and that kills the whole app.
If you have been stable after disabling Audio Analysis, then that was probably the issue. Roon can be considered a database server so heavier RAM usage is not unexpected, especially with such a large library.
When you have dropouts during playback, and I am assuming this is with Audio Analysis, turned off, Look at the Signal Path and see what the CPU load is, anything near 1.3x and the CPU is working too hard. You did not detail your CPU or RAM. Are you using any DSP?
Roon is not like other players actually. It has a large database portion to it that is unique. Roon will want to keep as much of the database in RAM, so as Mike mentioned, that can vary with your library size.
There have been widespread reports of random crashing since build 903. I am having very similar issues as reported by the OP on Windows 11 for several weeks now but it seems to effect Windows 10 as well. I am experiencing everything reported in these links.
Notice the processing speed pointed to in red above. That is telling you how much of 1 core is being used. If the speed is 100% + it is not shown. In your screen shot it is not showing, so above 100.
And over 100% is bad, I assume? The CPU usage in task monitor occasionally spikes to about 12% at most but is mostly as shown. I can’t understand what’s using huge CPU use. It’s an Intel Core i5 8600K CPU, not sure if that makes much difference but it’s handled everything in the past.
I noticed you use Wasapi. Have you tried to use ASIO and see if that makes a difference?
I’ve changed to ASIO already, and it still happens.
No, the opposite. the higher the x value the less CPU being used. A rating of 2x means that 50% of the cpu is being used. So, in my example, the 65.5x is something wickedly small like 5 or 6 % CPU usage. Your usage would be even less.
Ah, ok. So it’s not a usage issue, maybe it’s a soundcard setup for Roon? Are issues with buffer size or something like that plausible? I’ve done no special configuration for it.
Totally anecdotal, but I’ve been listening to some 16-bit music for about half an hour and no skips. 24-bit, of course, should logically put more strain on things, not the CPU clearly as we’ve evidenced, but maybe that’s a clue to the problem.