I understand @Ronnie. Already tried the closing/reopening but that didn’t change a thing. The copying to SSD for upsampling purposes is a good idea, but also taking the fun and spontaneity out of music listening (core is upstairs, listening room downstairs).
I do appreciate your help though, and I realize it’s all a temporary inconvenience. Didn’t change the RAM yet, just spent some euros on decent ethernet, just after having added SSD to my Mac. Roon keeps leaking money… wife not too happy about that
I’ve found the best option is to set Roon to analyze and just let it go and not use it until finished. With a library as big as yours that is going to cause issues. Ronnie’s suggestion to only start analysis when you are sleeping or away is a good one. I got about 2400 / hour using 8 cores of a Skylake i7 with all music and OS on SSDs in the same machine.
Thanks @Rugby, will follow your advice. Will be going to bed soon and will fire my Mac up then Honestly though, I keep coming back to the fact that I read about 50k album libraries here as being large. My library pales in comparison.
A bit disappointed in that respect, because the whole reason I started digitalizing my collection is because I thought it would be so much more practical. All the work… And yet, it appears there are still some miles to go… I easily outperform all of Roon’s search / focus functions. Ask me any album and I will blindly take it out of my Wall Of (CD) Sound in seconds!
LOL, I digitized my collection because the spouse decided that it had to leave the living space. So digitzed and boxed up. Except for 1 rack of “special” CDs I Keep around to play just using a transport.
Haha, now THAT I can relate to – unfortunately! As soon as I started digitizing, my wife started to think what she (sorry, “we”) could do with “the space saved/regained”. Because of course, I would be selling all of the cd’s digitized?! AS IF…!
And the spinning wheel keeps on turning, hopefully the ending of the audio analysis can lead to this scanning to finish soon (???), though the Files Scanned number is changing awful slowly, perhaps that’s to be expected (???).
Hi @George_Shin —— Thank you for your continued feedback and more importantly your patience as we continue to troubleshoot this issue you’ve been experiencing.
Moving forward, may I kindly ask you to please perform the following procedure on the device that is acting as your core. If you are running RoonServer + Remote together this is for Roonserver.
Please right click the Roon icon and select “properties” from the drop down.
You will see a field titled “target”. Please place ‘-storagetrace’ at the end of the “target’ input field.
Make sure the “start in” input field ends with “application folder” and nothing else.
@Eric
Hi there. I seem to be having a similar problem - Roon 1.3 hanging on a reasonably regular basis / no (or very slow to appear) album art etc - but no (musical) streaming drop-outs either from my NAS or Tidal.
I also have a “number” behind the “application folder” directory in properties - is there something weird going on there, or is that normal ?
Windows10Pro 64bit, i7-3770K, 16GB RAM, Meridian ID41 endpoint, all hard-wired to the same switch with cat6.
, and have restarted the Roon Server (10.0.0.132, MAUI2 host).
From the Roon Remote client (10.0.0.136), i can see the following happening where the files scanning is rapidly advancing,
And there is a brief flash of message saying something about scanning done but since it disappeared so quickly i cannot confirm 100% what the message said.
And the scanning returns to “Scanning now…” and here is where the scan will now crawl to ~6 files scanned per ~hour,
What is Roon Server (core) doing during this (slow) scanning?
And just so that i have this correctly, may i also have marker, delineation that shows when the Roon Server log starts from restarting the server (core), in the server log?
Typically RoonServer just creates a new log file every time it’s restarted, so that’s the best marker of a restart.
Can you upload the new log file again as before? Just send me the whole directory, no need to worry about getting just the ones after the restart.
The reason I’m asking for this is that I think I have a fix that will go out in our next build, but I’d like to be able to confirm that it will actually work. The new log after the -storagetrace option gives me enough information to check that I’m fixing the problem.