Sorry… My English was unclear. I’m saying they aren’t the same class of computer. I didn’t mean to imply that they aren’t the same thing. They aren’t even in the same ballpark. It’s like comparing a Honda vs a Lamborghini.
The Synology is well below our minimum spec requirements, and the Mac with m1 is well above what is needed to run Roon (or most other software).
Synology is usually very conservative with their hardware, making it just enough to do the task to serve files (which takes no real “power”).
Yes, the fly in the ointment is macOS. But the hardware is fine. You know, installing and dual booting Windows 10 on a Mac mini is not difficult. Give problematic macOS its own partition. Run Roon on the Windows partition.
If Mono is the root issue, why are all other Roon platforms using .NET, while macOS is the lone outlier still using Mono? That has to place at least some culpability on Apple and its walled garden approach to the rest of the industry.
Really? I used to have a sonicTransporter i9 and I replaced it with an M1 Mac mini. The M1 Mac mini has proven to be every bit as reliable. I am running the Roon Server app with no GUI and I have had zero memory issues. I am running HQPlayer Desktop on the same machine and have had zero issues with HQPlayer or Roon…
There are no issues with HQP, and Roon “runs” but I have a large library (250k+ tracks) and Roon eventually grinds to a halt. You really cannot compare apples and orages!!!
First, this was not made clear. Second, I have an Apple ecosystem and do NOT care to put Windows in it. Why don’t you think about what you’re writing before telling me not to mention issues, when you don’t even know my other requirements??? I expected better from you.
I will look. But I doubt that Microsoft has implemented .NET as an across the board release, prob only for the latest macOS (which is not what I can use in my mini). BTW, I am not complaining about them not releasing for older macOSs! I’ve moved on to NUCs.