Not quit sure where to post this: it’s my experience until now - setting up and “tinkering” my Roon system, giving first time users some thoughts and tips to “streamline” the test period.
I am still within the first month of paid subscription deciding if I’m going for a longer “commitment” with Roon. Most of the tinkering is done on RBpi’s with Ropieee, but I decided to post it in the Roon software discussion section; feel free to move this post if it’s more relevant in another section.
System layout when I downloaded Roon to give it a go was straight forward:
Storage on a DIY FreeBSD NAS with ZFS running 6 Tb on 6 HDD’s for redundancy.
Living Room
Bowers&Wilkins 702 S2 on
Yamaha R-N 301 receiver optical connected
Sonos Connect
Kitchen
Sonos Play:3
Dining room
Monitor Audio Radius 90 hd on
Sonos Connect:Amp
Hobby Room
Magnat Monitor 1000 on
Connect:Amp
Outdoors
Sonos Play:5 and a “free” Sonos Play:5 where needed…
Streaming was done with the Sonos1 app and the Yamaha NP wireless controller.
Why did I try Roon?
The first time I encountered Roon was during listening sessions at dealers.
I liked the GUI and the amount of information, so decided to try it at home. The main reasons to do so are listed here.
- The Sonos streaming is limited to 48/16 and can’t handle Flac files. I collected/bought a lot of files with higher resolution stored in a separate directory I couldn’t play with the Sonos app, only with the Yamaha controller with no multiroom functionality.
- I wanted to try a system that could play hires files and compare them with low res files and that would still let me use the Sonos boxes doing so, single or grouped.
- The lack of information about artists, colaborations etc in short the lack of “enriched” data and a useable, good looking GUI was also something I was searching for.
- I wanted to integrate the Yamaha receiver better in the system, because that position (living room) is planned for a serious receiver hardware upgrade…
- And last but not least: I was searching for something more flexible than the Sonos1 app for older models, which is barely maintained by Sonos. I am so to speak updating from the Sonos installment I did a while ago, still using the hardware because it’s working ok.
Roon Core
I would have liked to install the core on my freeBSD NAS. But not being able to do so I decided to “tinker” another route: use an Apple box (we’re running 4 of them: 3 MacBook Air and 1 iMac). I tried the iMac but running the core on a box that is also daily used for other tasks does not work, don’t go there, I’ve tried it…
So I got an external ethernet connector to create a wired connection for a Macbook. I first tried to run the core over Wifi, but even though we have a solid and fast network, that’s also a “no go area” - esp. when using DSP.
The MacBook only runs Roon and is placed in the utilities cupboard together with the ISP box, main router, Sonos Connect and Yamaha Receiver (we really did place the receiver in a cupboard….)
Installing and setting up was straight forward, the NAS was quickly found (with SMB) and the database created. I also connected a SSD (sata to USB) on the main router to create a small storage location (Netgear’s USB-storage) I can use when I want to try other core locations or other streaming solutions like Moode, PiCorePlayer or Volumio.
Hick ups and stutters
As mentioned I soon found out that good advice needs to be followed: wired connections are to be made where ever possible between the system components, esp the Core and NAS. Although my local ethernet is good, 192/24 files playing from the NAS were occasionally (once or twice per day) interrupted with an error message:
“Roon lost control of the audio device” or “An audiofile is loading slowly etc). Because the connections are wired, there has to be an other explanation for this to occur: I’m investigating network traffic and/or a corrupted component somewhere in the hardware. I solved this hick up by placing the 192/24 files on the local ssd of the MacBook running the core. Needless to say that everything is now running OK.
Endpoints and RBpi’s…
All Sonos boxes were easily found by Roon. Also the receiver connected via Airplay. So far so good, but this also meant that the maximum bit rate was determined by Sonos and Airplay, 16max…. Although the Sonos Connect was setup to bypass the DAC and use the one in the Receiver, Roon only uses 16 bit on Sonos.
That’s where the RBpi’s enter the equation. Using HifiBerry hats I could create 2 endpoints: 1 with a Digi+ hat for the Receiver and 1 with a DAC+ for a Connect:Amp (line in).
Installing the Ropieee software I ran into something odd: the second RBpi was internally grouped by Roon making it a clone of the first one and unusable. It got listed in the audio devices in the settings menu but it didn’t show up in the audio devices selection list. Also when using the device setup menu, the given name from the second RBpi always changed automatically to that of the first one.
I found that flashing new images on the SD cards of both RBpi’s and installing them separately from each other before connecting them both on the system solved the issue.
I don’t know what triggered this: maybe Roon sees the endpoint before the setup of Ropieee and stores the hostname before I changed it? It’s something to take care of when installing multiple RBpi’s on a network.
Both endpoints are now working like a charm and deliver more than I ever expected!
Endpoints with benefits (pun intended)
I’m using Roon since December 21st. This weekend the RBpi’s are installed. What are my first thoughts about it all?
-I really like the GUI and the logical layout of menus and choices. It looks killer and works on all devices we own.
-The control over the actual streaming is amazing, I’ve never been able to control that many aspects of it.
-DSP has blown me away; what a possibilities to explore…
-Grouping works great - grouping Sonos was always possible, but hold on to your seat: when I group the two new endpoints (RBpi’s) one is using the line in from a Sonos Connect:Amp - by using the Sonos app I can create a Sonos group from this box and all Sonos boxes stream the music!! Despite not being possible within Roon, it can be done. (Check the audio delay setting on the used Amp, this must be set to minimal…)
-My receiver position can now be reached with 4 signal paths for comparing:
Airplay (16 bit)
Sonos Connect optical connection (16 bit)
RBpi Digi+ digital connection (HiRes)
Receiver app DLNA connection with NAS (HiRes)
-The tinkering required until now is easy and straight forward; lots of info to be found here in the community
-Although I wanted to install the Core on the NAS, I really think that’s a next best solution. I can control the Macbook with screen sharing from anywhere in the network, the GUI is off course way better than freeBSD offers. The computing power on the Macbook is also solely for Roon, the NAS has permanent other tasks to attent and already I’m having that tiny problem of the bandwidth (?) or speed delays with the 192/24 files.
I hope this helps other people to decide about Roon - I still have 2 weeks to decide about an annual subscription…
