I have a Mac Studio M1 with 32 GB RAM. I tried to use it as a Roon core and it was a disaster. Hundreds of crashes while importing the data base. I am using the latest version of the Mac OS. I have large collection (over 500,000 tracks), and gave up after trying to import over a period of 5 days. Whenever the Mac would restart it would try to reimport the entire collection again and this was very frustrating. Tried to import one folder at a time, but it kept crashing when I added more folders. Never had such a frustrating experience. This is a machine that should be able to run Roon well.
Hi @steveoat87 ,
Thanks for your report here. I have seen libraries larger than yours run on 32GB of RAM, so I suspect something else was going on when you were trying to import your library on the Mac. Did you have background and on-demand audio analysis turned on under Roon Settings → Library? Perhaps Roon was still ingesting your library and hadn’t finished yet. Have you uninstalled Roon on the Mac already, or do you still happen to have the previous install/log set?
Had analysis on throttle. Roon is still installed on the Mac but I have disconnected as it is not usable
Hi Norris,
Since I did not uninstall Roon core from the Mac Studio, still have the logs. Is there anything you need to help me solve this problem?
Hi @steveoat87 ,
Yes, can you please access your old Roon + RoonServer logs on the affected Mac by using these instructions, upload both of them to the below link and let us know once uploaded so we can review? Thanks!
https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external
Hi Norris,
I sent both the Roon and RoonServer log files to you under my user name steveoat 87.
I made 2 submissions. In the first I just included the Roon log files. Then I re-read your note and sent another submission including both the Roon and RoonServer log files. Both under my user name steveoat87. Please let me know if you need anything else.
Hi Noris,
Were you able to take a look at the log files I sent to you? Do you have any insight as to what may be causing my problems?
Hi Noris,
I wanted to call to your attention that Roon seems to use a lot of RAM on the Mac Studio. Depending on how many folders I try to scan, the usage is anywhere from 10 - 17 GB RAM (looking at system monitor including Roon Core and Roon Server). This seems high to me, although the Mac Studio has 32 GB of RAM. Is this unusual? Still having a lot of issues with crashes.
Hi Noris,
Wonder if you were able to take a look at the logs and uncover the issue. Please let me know.
FYI: I ran an apple hardware diagnostics test and everything is fine.
Hi Noris,
I would appreciate a response. It has been almost a week and I still have an unusable Roon core on my mac studio. Please get back to me ASAP
Very disappointed that I haven’t heard from you. How can you call this tech support when you don’t respond to a basic request.
Hi @steveoat87 ,
Thank you for your patience until we’ve had a chance to look over your logs. I do see some clues as to what could be going on, it looks like Roon tries to import a large amount of Boxset tags, 27,000 tags to be more precise, and it looks like this could be causing the issues with your Roon database. Do you happen to use an app called SongKong?
As a matter of fact, I do use Songkong. However, when I did an initial scan with Rock or with Windows, the process was quite slow but I saw far less crashes. If you feel it will help, I will remove the "AddRoonAlbumtag. Let me know what you think
I also have a custom tag called “Box Set”. Do you think this may also be causing a problem?
However, I also notice when importing alot of new files, not box sets, I still get a lot of crashing. So, I think there is still more to the problem.
Hi @steveoat87,
There have been known issues in the past with large amounts of external tags and the performance of Roon.
You could first create a fresh backup to save your current database. After that, perform a database refresh and attempt to import your library excluding any external/third-party tags associated with your files.
Here’s a step by step on how to refresh your database:
- Make a Backup of your current RoonServer Database
- Exit out of RoonServer
- Navigate to your RoonServer’s Database Location
- Find the folder that says “RoonServer”
- Rename the “RoonServer” folder to “RoonServer_old”
- Reinstall the RoonServer App from our Downloads Page to generate a new RoonServer folder
- On the Roon Remotes, press “Use another Roon Server” and connect to the new database
I eliminated many of the external tags and finally, after many crashes and hours my library is finally loaded (676000 tracks). Everything seems to be working OK except for the fact that when I add a new album, Roon rescans every folder, not just the one I added the new files to. My library is spread over 8 folders, and a new rescan takes forever, often with frequent crashes. This does not seem normal to me. I don’t recall this happening when I used either windows or ROCK. What do you think is going on? Is there any way to restrict the scanning to just the folder that has the new file?
Hi @steveoat87,
Are you referring to 8 different watched folders?
Roon will only re-scan the watched folder in which the edit has been made. You can disable additional audio analysis from your Roon Settings>Library which may help! 
I wouldn’t be completely shocked if a library of this size doesn’t push your server to its limits. An impressive collection! 
My Music is on NAS and I have broken my collection into 8 folders. Roon monitors these folders so I think this is what you mean by watched folders. However, I notice that when I add a new album, Roon appears to scan every one of these 8 folders which I find odd. I recall that when using ROCK or windows, only the folder that a file was added to would be scanned but it appears on the mace that every folder is being rescanned, which seems odd as well as inefficient, which probably contributes to all the crashes.