I don’t intend to use Roon with a physical library. It seems that one CPU limitation is dealing with large physical libraries.
For me I intend to use Tidal streaming exclusively. So for me I need CPU only for DSP. I am using only one stream currently. I intended to use REW and the UMIK to create a convolution filter. Possibly I would use other DSP also. I only care that I could do this for 2 potential simultaneous streams.
In that regard I am between the 8th generation i3 two core and the 8th generation i5 four core.
If these processes are single core processes then I doubt it would make a difference. I suppose cache sizes might. Still for streaming i suspect not. If indeed it does then I may consider an optane drive. Still I doubt it would make a difference.
Nope - this is a false assumption. What matters is the size of your library, and hence the size and complexity of the Roon database.
And the size of your library is determined by how many albums you have in it - whether these be physical local copies on a local hard drive, or albums that you have added to your library from a streaming service.
I see. I currently use it on a 8650u quad core laptop. It works fine. I suppose I’ll just go i7.
If like to confirm though if the database process is a single core process. Then I suppose the DSP processes are run on other cores which is why I suppose more cores are better? Or perhaps an older 2 core i7 might work? These new bean canyon NUCs apparently can get loud and while I like the Cirrus 7 after pricing it out loaded it got less palatable to me.
I enjoy doing custom builds so this is up my alley. Combined with Akusa cases I think this will be my route. I just wonder if ROCK can be put on it. I don’t see a reason why not but maybe someone could let me know if there is a reason why not.
ROCK (conceptually) has everything unnecessary removed. If your custom build hardware requires a driver for a peripheral (especially network chip) that is not included in ROCK or not already in use by one of the supported NUC, then you may experience problems. Search the forum for “MOCK” for this type of usage.
If you decide to custom build one and you experience ROCK incompatibility, then install Windows.
If you intend to run ROCK you should buy a NUC. Even if your MOCK works luckily, if a problem comes up in the future it makes it harder for support guys to support you.
Thank you. Do you have any idea about the performance differences when running windows vs. ROCK on the same NUC? I’m wondering if the hit in performance with Windows is worth the speed increases offered by such a custom build.
Hi, i m planning to build a server like nucleus+.
I m planning to buy nuci7 on a fanless case + js2 uptone lps.
Here are the specs i m planning to go for, please i need some advices cause i m not that technical.
That Kaby Lake processor is almost 3 years old. That’s not necessarily a problem, depending on the money you’re spending.
You can probably get a more current processor (7th or 8th gen) for about the same cost as one that is 3 years old.
Don’t know the size of your library, but the base Nucleus is good for 100,000 tracks and up to 6 endpoints. That Nucleus only has an i3 chip. Of course, if you are exceed those specs or are going to do any DSP then you might need to build more.
I have four endpoints and do DSP on some of them and I use ROCK on a 7th gen i5 NUC, without any problems. My library is under 100,000 tracks.