roon firewall update

For some reason which I now forget, I signed up for the beta channel for Roon’s Linux server software. It updates maybe once a month, and very recently (with 1.8.x) everything stopped working right. A quick jump to the community boards and I found out that Roon Labs had changed the ports required for the software. Even more astonishingly, it’s undocumented. Here’s what I’m using.

22/tcp                     ALLOW       Anywhere                  
9003/udp                   ALLOW       192.168.0.0/24       # roon
9330:9339/tcp              ALLOW       192.168.0.0/24       # roon
8008:8009/tcp              ALLOW       192.168.0.0/24       # roon
30000:30010/tcp            ALLOW       192.168.0.0/24       # roon
8010                       ALLOW       Anywhere             # chromecast
1194/udp                   ALLOW       192.168.0.0/24       # roon
22/tcp (v6)                ALLOW       Anywhere (v6)        
8010 (v6)                  ALLOW       Anywhere (v6)        # chromecast

roon 1.8

Five emails from Roon Labs announcing their latest version, 1.8. Take a look below, that’s the home screen. Seriously. A big “one step back.” No additional features, a horrible UI and UX that’s shaky. Is Roon becoming nothing but a frontend for streaming services? Well, like any other old component in the rack, it’s time to look for the next one and upgrade.

uncomplicated firewall (ufw)

I run a Roon Server or “Core” on my Ubuntu box to supply music to various endpoints on my local subnet. Because the computer also has a window to the outside world, I run a firewall, ufw. Like its namesake, it’s easy to configure, you can get the basics here. Anyway, I need to open a few ports so Roon Server can be discovered on my subnet, by creating an application profile and then adding a rule to the firewall.

First, we’ll create a file “roon” in the following location:
$ cd /etc/ufw/applications.d/
$ sudo touch roon
$ sudo nano roon

Here’s what’s in the file:
[Roon]
title=Roon Server
description=Roon Labs Core Music Server
ports=9003/udp|9100:9200/tcp

Note the context of the ports entry: The pipe separates udp from tcp, and ranges are set with a colon (and individual ports with a comma). Once you create the file, you can quickly check syntax by running ufw status, and it will let you know if you made any errors, which is handy. Once that’s created, it’s easy enough to add the rule to ufw, and check status again to see it working:

$ sudo ufw allow from 192.168.1.0/24 to any app roon
$ sudo ufw status
Status: active
To Action From
— —— —-
Roon ALLOW 192.168.1.0/24

I should note that the reason I’m doing this is because Roon doesn’t document what ports need to be open, and I’m having an issue with one piece of hardware being recognized on reboot. There’s probably another series of ports that I need to open up, so having a profile is an easy way to trouble shoot; once I make changes, I can edit the profile then update ufw with the following command:

$ sudo ufw app update Roon

Since Roon uses randomized ports, my interim fix is to allow access to the server from the endpoint in question:

$ sudo ufw allow from [endpoint ip]

Nothing scary here folks, just some computer and network basics.

roon 1.7 update

Woke up in the middle of the night and for some reason I discovered that my Roon app needed updating. Did that, updated the core, then went down to my PC to update the Windows application. Today on Facebook, I see post from Roon that touts the new “Valence” feature, one of those “expert” algorithms that people that don’t love music use to figure out what to play or buy next. The algorithm has been recording over 100,000 Roon users play habits (did I opt in or out?). Okay… that little search icon in the upper right is all I need.

On the upside, all the Google Home minis in the house now show up as available audio devices. That’s a fix, I also think that the playback on Android phones has been improved.

But the big disappointment is that the update did not include the ability to add reviews, bios, notes, links etc. Now having that would make it “expert.”

roon 1.6

Yesterday a big update to Roon came out. It touted integration with Qobuz, an unpronounceable and paid streaming service similar to Tidal, and some enhancements to Roon Radio, for a “personalized radio experience… [that] helps you discover new music by curating great recommendations.”

The only problem is a) I already own a music collection, and b) I could give a f*ck as to what some algorithm thinks I should listen to next. I want Roon to stream and organize the digital music I own. It’s all about metadata, and it’s all about getting that metadata correct.

Straight up: I don’t buy into music services (Spotify, iTunes, Tidal, etc.). They are for people who don’t love music: this notion that they or Roon “can help me listen and find music” is diametrically opposed to my journey with music. It’s unsatisfying and it’s lazy, but most of all, it’s imprecise.

Sidebar: I am from the era of the Record Hunter, when one had to put in the work to get music, and put in even more work to discover new music. I’m not sure if the younger generation has any appreciation of how difficult it was to find things in the pre-internet era. I’m not only talking about crawling through bargain bins, driving miles to find new record stores or visit old favs, or scanning the back of Goldmine for vendor listings; it’s going to record shows on Sunday mornings; sending paper checks in envelopes to vendors that were only an address; waiting weeks for a special order to come in, or something to arrive in the mail; tearing out the Yellow Page listing in a new city and taking the rental car to every store you could hit; have a typed want list that was carried on travels; actually talking to people about music, writing letters to friends and acquaintances about favs, making friends just because of the music you shared in common; just hanging out and listening to music; carrying records to friends house, or school, or wherever because you found something you thought others may like. being heartbroken when a purchase didn’t pan out, because those hard-earned dollars were just that; listening to the radio, because that was what we had!

The sheer joy of finding a golden nugget from my want list, or an unknown gem I’d never heard of before: This was how I fell in love with music.

roonlabs: the good, the bad

When thinking about the best way to write a review of Roonlabs music server software, the best way to do it is with is a list. So here we go:
Pros:

• Roon works. Everything works as intended, the very first time. Sometimes my phone takes a few seconds to connect to my Roon core server, but everything worked “out of the box” including Core software, Windows app and phone app. No Contact Us, no Help Tickets, etc. That’s great!
• Roon sounds great – Yes, my digital library sounds fantastic. Whether this is because of their software or not is debatable, but my system sounds fantastic.
• Heterogeneous hardware playback. Roon works with my computer’s outputs, Hifiberry, Squeeze devices, Chromecast devices, phone, PC, etc, etc. That’s great, not being tied to any particular hardware. It works over a VPN connection with my phone, but it’s spotty to say the least.
• DSP. The ability to apply DSP to each signal is a big deal. Unfortnately for me, I’m not ready to dive in.

Cons:

• Roon’s metadata has holes. I’ll post some screenshots, but Roon certainly isn’t a fan of progressive rock. While it tagged the vast majority of my albums correctly, it has precious few pictures of the artists in my library, and when it’s wrong, it’s wrong. I get that I have some obscure music in my collection, but still. Roon’s handling of metadata is a bit like the Wizard of Oz. Something’s happening behind the curtain, but who knows what!
• Roon’s artist biographies and album reviews. Nothing – and I mean nothing – would make me happier than being able to add my own album reviews to my music in Roon. But there’s no way to that, no way to edit an artists biography, or even add weblink. The kicker? Most every other field for an album is user-editable. That’s really the most disappointing thing about Roon.
• Roon only works on a local network. No out-of-the-box VPN or greater internet integration. Don’t know if this is because of RAAT, but I imagine they’ll get there. So I need to keep Bubblesoft for now. Also, the Android app is okay, but has bugs. I imagine the iOS app is better!
• Roon has excuses. Reading through Roon’s Community board, one thing is clear: Ask for something – Discogs link? Soundcloud integration? Custom artist text? Custom album reviews? – and you get another community member responding as an “authority”. Meh.

All that said, I can sum up two things about Roon. The architecture works perfectly and it sounds wonderful, which is saying a lot; however, Roon does not want metadata that isn’t already embedded in my FLAC files or what they provide, which frankly, sucks.
But I’m sticking with Roon, because I’m financially committed, and I see the promise. The question is when will I disable Logitech Media Server and Bubblesoft UPnP/DLNA?

[As a side note, RoonCore doesn’t seem to broadcast the host machine IP. In typical fashion, Roonlabs marked my support request as “Tinkering” and said it wasn’t supported. Seriously!]

roon labs

Roon is paid software. Now that that’s out of the way, let’s talk about Roon. Roon is software for managing and accessing your disk-based music library. There is a server aka “core” element, as well as “endpoint” apps for (nearly) every OS, including Windows, Mac, iOS, Android, etc. Some like to think of it as a component of your audio system, albeit one of the software variety.

Why use Roon? I have to admit a directory tree isn’t the most elegant way to view ones digital music library. And that’s what Roon does: it scans your digital music, applies rich content – pictures, text, weblinks, etc – and puts it all together for a paid subscription-like experience. It even fills in the blanks on missing artwork, etc. I don’t use Spotify or iTunes, but Roon provides a very similar interface.

I installed RoonServer on my linux box with ease. When I ran the “easy install” script (remember to chmod +x first), it alerted me that I needed cifs-utils installed first. That corrected, the script downloaded and installed the server software, and set itself up as a service. But that’s it as far as linux goes. It’s a headless game, no native app, no web interface, from here on out I’m off to my phone or computer to control my music.

On the Roon app for Android, I logged into my Roon account and gave them my credit card number. Viola! it all worked. I then setup a music “zone” (an odd choice of word), which is an audio player. I was a bit shocked by how many appeared: my Pixel 2 phone, the (four) audio outputs from my linux box, Roon Bridge which I installed on a new RaspberryPi (more later), all my Chromecast devices, and lo and behold, my Squeezebox3 and Squeezelite players. In order to use the latter, one must enable Squeezebox support AND stop the LMS (Squeezebox) server. Once you select something to play, you can then choose where – including simultaneously – to play it.

I’ll write up another post as after a week or so of my free 14 day trial, but initial thoughts are mostly positive. It is a great interface, and it brings the whole digital music experience up a level. However, I really am disappointed there is no native linux app, and I still haven’t figured out how to add my own rich content, other than pictures to artists and albums to the library. (Hey, of course I’d like to add my Strawberry Bricks reviews to my collection!) The Android interface could sure use refinement (separate player from config mode, easier access to artists) but I suppose this is a forever work in progress.

Roon all sounds fine, and it all looks great; the question however is simple: is it worth $119 per year, let alone $499 per lifetime?

On the web:
Roon Labs

aries mini vs node 2 | roon

Two very popular streaming devices, one from Auralic, the latter from NAD/PSB affiliate Bluesound, are very tempting to purchase at $499. While neither have displays, they have all the guts of a good streamer, perhaps an update to my decades old Squeezebox, or better version of my Hifiberry Pi. I’m a bigger fan of streaming every day, because, it sounds just as good if not better than CDs, and is so, so convenient. Plus, playing music directly from my computer is getting… passé?

But there are some downsides to these streamers: Foremost, no display; to get visual, I’d have to spend more money. Also, each of these players has a serious fault: The Aries Mini has no native Android app, while the Node 2 doesn’t support UPnP/MiniDLNA. Sure, I could fork of some $$$ for a Roon Core, which both support, but I’m not sold on that either. I’d like to use an existing music server (UPnP, Logitech), and I have only Android devices in my home.

I’ll admit, Roon is tempting. At $499 for a lifetime license, it could be the future of my streaming server. Or at least, another one. It supports Linux, it’s got a good UI, combining the rich content of the web to file names and folders. But wouldn’t it be even cooler if I could pull up my music collection via Roon on my TV and use that as an interface, instead of a little phone screen? Tell me it’s so Roon, and I might sign up!

On the web:
Node 2
aries mini
Roon Labs