My one and only bias is getting the right tool for the job. I am also a linux person professionally and use Windows as well. If you really did at some point you could put Windows on the NUC and run Roon on Windows. The one case this would not be good is if you wanted to use HQPlayer with Roon. So my 2c would be: if you’re considering buying a machine to run Roon Core exclusively, do yourself a favor and get a NUC and put ROCK in it. NET emulation libraries (at least this is my understanding)ģ- Those libraries are at this point relatively optimal on linux, not so much on mac and definitely at this point not on M1-based macs
NETĢ- For running on linux/mac it relies on. But keep in mind that:ġ- Roon is developed on Windows using. Yes the M1 is more powerful than the 2012 mini. Now, you’re considering an M1 mini dedicated to running Roon Core. Everything is essentially as fast as you would want it to be. So far this has transformed my Roon experience. I restored the Roon db from my mini into the NUC. This is a slimmed down version of linux that only runs Roon Core. Out of frustration, a few weeks ago I migrated to a NUC running ROCK (Roon Optimized Core Kit) (1).
I have ~250k tracks in my library and over the many years I have used Roon I have customized everything from duplicate album grouping to careful artist tagging to many other things. I run Activity Monitor and would check CPU usage when I had slowdowns - always below 20% on any one core, and overall below 5%. I am pretty competent with computers but frankly could not figure this out.
This mini was dedicated to Roon alone, with a clean Catalina install.įor the last couple of years I have had woes with Roon - slow searches, slow playback start (even with local files) - all sorts of weird EXTREMELY annoying issues. I have always run Roon Server (aka Roon Core) on a mac mini - first a 2009 one then a 2012 i7 quad-core mini with 16gb RAM and an SSD as system drive. I have been a Roon lifetime subscriber since July 2015.
0 kommentar(er)
