Not at all. You can run roon on an available device, although over time you may see some advantages to a dedicated core or even ROCK. For quite some time as I got to know Roon, i ran it, along with other general purpose programs, on an OLD ( i mean OLD) MacBook Pro Laptop from 2009. yea, it had an SSD and lots of RAM (for an old machine).
Now I run ROCK as an appliance on a 6-core i5 Intel NUC. Huge overkill, but totally stable and forget-about-it.
I now use that old MacBook Pro as a Roon ready remote endpoint and ethernet--> USB bridge - and that's in my **main** system in a dedicated sound room. So don't let anyone tell you its a power hog. Aside from indexing and searching metadata - and unless you are doing wacky DSP - its not. And in general you can do more harm with DSP than good unless you have a very specific problem to solve and tons of knowledge on how to go about solving it. Room or speaker compensation jumps to mind, but again, you;d have to have a for-real problem, and a fully FFT characterized idea of what's wrong. Yea, right :-)
Now I run ROCK as an appliance on a 6-core i5 Intel NUC. Huge overkill, but totally stable and forget-about-it.
I now use that old MacBook Pro as a Roon ready remote endpoint and ethernet--> USB bridge - and that's in my **main** system in a dedicated sound room. So don't let anyone tell you its a power hog. Aside from indexing and searching metadata - and unless you are doing wacky DSP - its not. And in general you can do more harm with DSP than good unless you have a very specific problem to solve and tons of knowledge on how to go about solving it. Room or speaker compensation jumps to mind, but again, you;d have to have a for-real problem, and a fully FFT characterized idea of what's wrong. Yea, right :-)