First of all I want to say hello to everyone here in the community. I’m running roon for round about 1.5 month now and I couldn’t be happier. It’s such an intuitiv piece of software and helps me to find new tracks and musicians while forget to go to sleep
This Post is more of an overview of my past thougths and tests on how to implement Roon to my existing IT and audio environment.
What I want to achiev with Roon:
-
Manage all my Qobuz music in roon to find similar and new tracks. → thumbs up for Roon Radio!
-
rip my round about 250 CD Collection and add it to the local library.
-
have a system that simply could play on all my devices. (WiiM, Denon Receiver, Chromecasts, Android Phones, Android Auto)
-
fire and forget solution with low maintenance
All of my requirements are fulfilled by roon. So let’s go ahead to the technical part.
1st Core/Server installation:
I simply have run and test all of my requirements while running the core/server on my local PC.
The core/server was able to find all my streaming and remote devices in all network segments (IoT, Wireless, DMZ, LAN). But I had already preconfigured Avahi, mDNS and all other necessary prerequisites.
So let’s find a solution for a 24/7 installation.
2nd installation (Core/Server on Synology NAS):
I’ve installed a VM on my Synology DS1621xs+ with a striped down debian 12 and roon installation. This installation had some troubles with hanging (process running until man. restart) .net streaming processes from Roon ARC forwarded from my reverse proxy.
As much as I prefer a self build Core/Server (possibility to monitor the Server, running open source, …), I also appreciate an easy to handle solution. Maybe I could have debug every problem, with my background (I’m a IT Systemengineer for Datacenter and Cloud solutions…). But why to tinker, when there is an “appliance” version of the core?
3rd installation (ROCK on Synology NAS):
I’ve installed ROCK inside a VM on my NAS. This works perfect until today. The performance is great, everything works as intended and it’s supported if I run it on an Intel NUC.
Running ARC with ROCK:
I’ve never forwarded a port to my Core/Server as I have the knowledge to do it “the right way” with a reverse-proxy or client to site VPN (openvpn, wireguard or what ever)
ARC itself works at the moment without a problem connecting to the core with wireguard managing the client to site connection only for the ARC App on my Google Pixel 7 Pro.
Final solution (ROCK on NUC12):
Let’s face it, lots of us end up with a NUC running ROCK on it. It looks like me too
I’ve ordered yesterday a NUC12i5 (latest officaly supported ROCK Hardware) to install Rock baremetal on it. Why? No tinker and direct support from Roon if I face any problem in the future. I just want to enjoy my music.
I’ll be happy to report the performance differences to the solution on the NAS as soon as I migrated the core. So stay tuned
Oh and please don’t ask me if solution A has better SQ than solution B. I can’t hear any difference. But I also do not care about snake oil cables or such things
Security concerns (ROCK):
-
having a non ssl enabled web management GUI without any kind of authentication is by far not state of the art.
-
port forwarding to a closed source appliance is not optimal for systems like this not being isolated. Not everyone has an IoT network segment or the knowledge to build client to site vpn or reverse proxy solutions. I don’t have a global answer for this “problem” for the normal customer/user. All I want is to share my opinion.
-
smb (smb1?) server without authentication. really? I’ve had to spin up my WSL on my Win11 Desktop to copy the codecs do the ROCK. Please do not activate SMB1 or enable unauthenticated SMB connections on your PCs. Or if you need so, roll back everything after copying the files to the ROCK! It makes your PC vulnerable if you do such changes without reverting them.
Sorry for the wall of text and for any kind of gramar or misspellings. English is not my native language