Yes, that portion is running the new, more cpu intensive, audio analysis that is generating both the waveform and the R128 volume leveling and the LU dynamic Range number.
Well, in my analysis, I left it at 4 cores. My i7 is a quad core so the other 4 or virtual cores for hyperthreading. I did not notice much performance gain by going above the physical core count.
Okay, i’m leaving at 8 cores, across two cpu’s, though my eyeball subjective analysis shows the audio analysis seems to be going relative faster than previously at 4 cores.
Now at 6870 / 40514.
The CPU Usage as seen from Windows Task Manager varies, but median seems to be at ~40%, but fluctuating, as high as i’ve seen hitting ~60%.
Perhaps by the end of the weekend, will be done. We shall see.
One time hit, overhead to greater goods to come from 1.3 update.
I’ve read in other threads people successfully solving it with temporary selecting less cores for the audio analysis, so the scan can finish. When the scans are finishes the audio analysis can use more cores again.
What about your network connection/speed to the nas where the music is stored? The audio analysis will read all audio files, so you can expect this is a huge amount of data to be analysed. Maybe your network connection between Roon and the storage of all your music can be limiting here.
Initially i’ve left the audio analysis at throttled setting, but i guess i’m at trade off to finish this darn audio analysis (first).
Looking at current status,
So, i’ll let the audio analysis to finish.
But you are right, the scanning is really crawling amid (quicker) audio analysis given the 8 cores setting.
I did see that 194 is on deck to update to, but for now reading the release notes, i would prefer to say at 1.3, and let the analyzing and scanning to finish.
I have few new music materials to add that i would prefer to do so after 1.3 housekeeping is done and db in consistent, quiesced state.
This way, it will take WEEKS before Roon has analyzed my library. Fast analysis speed, using 4 cores on a dedicated Mac Mini i7 Quad Core with SSD and 10 GB RAM. No DSP Engine or other 1.3 features for me – if I try it my Mac goes berzerk and skips each song. Average 0f 413 % CPU for analysis only (rescanning appears to have finished), so I guess I have to wait a few more weeks before my 1.3. is “released”. Sorry about the frustration quite apparent from my post, but cannot help but being underwhelmed and frustrated…
The Analysis is a Dynamic Range analysis based on R128…and this process will take a long time…especially for a library containing 250,000 tracks…there’s just no way around it…and it will be a useful tool for those who wish to implement Volume Levelling, which is another feature high on many users’ wish list for v1.3
My advice would be as follows to allow you to benefit from this in the future
Assuming you do most of your listening at the weekend or at night after work etc…simply go into the settings screen above whenever you wish to play music…and switch OFF the Audio Analysis…which in turn will reduce your processor usage to normal…and also Music Replay will return to what it was…or even better due to the performance enhancements within v1.3
When you’re finishing listening and heading to sleep, then go back to the screen above…and turn Audio Analysis back on
As you state above, the Macmini processor is a QC Core i7…which allows for something called Hyperthreading…so if you click on the “Speed” drop down box above, you should see that there is the option to choose 8-cores…which will increase the speed of Analysis substantially compared to using the current 4-cores
Summary: Turn off Analysis while you want to listen to music…and turn it back on overnight and when at work etc…and the process will happen reasonably quickly…without it interfering with music replay…and will still allow you to play around with the new DSP and Minimum Phase options in v1.3
@Ronnie, even when I turn everything off as you suggested, and Roons finished rescanning, the spinning wheel keeps spinning. What is Roon doing in the background, impacting the performance of my Mac? For instance, when I try upsampling to DSD256, Roon hangs and skips each track (processing speed: below 1 – 0.7 or even lower). DSD128 is the max I can currently achieve over ethernet. Is Roon scanning my artwork, or…? I made this screendump five minutes ago, but Roon is still at 371237 Files Scanned.
There are a lot of substantial new features within v1.3…and in order to make these available, Roon needs to rescan / reimport all the files in your Library…and this is simply a long-winded [and therefore frustrating] experience, until it gets completed…and this is not helped by your large library
My suggestion would be unless that “Scanning Now” changes in the next 10 minutes would to close and reopen Roon…which will result in Roon rescanning…but usually much quicker
You may also want to copy a few albums to the local drive of your Server / Core…and do the DSD upsampling on those albums only while you’re playing around in the initial stages
Also, did you change that 2Gb RAM module for an 8Gb…bring your machine up to 16Gb from its current 10Gb??
