We are hard at work on improvements that will make Roon friendlier to people with pre-groomed collections, and more democratic about metadata in general. One of the last pieces that still remains to be addressed is Roon’s handling of genres.
Genres are a considerable pain point for many. I’m going to be talking about “our plan”, but I’m using that term loosely. The plan isn’t firm yet. It’s more of a working draft. From here on out, I will to refer to genre assignments from ID3,Vorbis,etc tags as Local Genres. and genre assignments that Roon provides as Roon Genres.
I’m going to start by going over some of Roon’s shortcomings with regard to genres today:
- Roon’s genre hierarchy comes from Rovi/AllMusic and it’s reasonable to disagree with how they have organized the genres, or how they have assigned genres to albums and artists.
- Unidentified content does not have genres at all in Roon.
- Many people have manually groomed their files with genre tags and want to use them.
- Genre assignments roil peoples’ emotions in ways that other editorial metadata (like reviews) do not, and we are currently offering no flexibility in this area. I’ll admit to being surprised at how upset people can become when they see genre assignments that they perceive as inappropriate. Nonetheless, we get it. You care. We need to do something about it.
Incorporating local genres into the Roon hierarchy seems like a good move, since the alternative is a segregationist approach that creates two side-by-side systems that are separate but not-quite-equal, duplicate copies of “Jazz”, and so forth. This means:
- Roon Genres and Local Genres are organized in the same hierarchy. “Jazz” means “Jazz” no matter where it came from.
- Users are able to re-arrange the genre hierarchy as they see fit, so the Roon hierarchy is basically a suggestion/starting point, not a royal decree.
- Local genres that don’t match up with Roon genres go into a special node in the genre hierarchy called “Uncategorized” until the user puts them somewhere more apt.
It’s pretty clear that genre assignments need to be editable. This means that you’d be able to add or remove genres from albums and artists. I don’t think there will be much controversy on this point. Roon should keep separate lists of local genre assignments, Roon genre assignments, and changes to genre assignments that arose via manual editing. This is both fully non-destructive/intent preserving, and allows us to treat them differently.
We don’t think the default experience should include local genres. For people without groomed genres, they will make the experience worse because in non-groomed collections, local genre tags are a complete mess. The current plan includes a setting that defaults to off, called “Show Local Genres”. When the setting is enabled, it causes local genres to show up alongside Roon genres on the album details screen.
Ok, those were the parts that I’m feeling pretty confident about. Lets get to the stuff where I’m less certain:
- If you have “Metal” as a Local Genre, and we have “Heavy Metal” as a Roon Genre, those are treated as separate entities, even though they are semantically equivalent. Maybe we need some kind of user-defined mapping so that local genres can be re-written on the way in?
- Since genres are identified by their names, there’s no such thing as “renaming” or “merging” genres. Semantically, in order to “rename” a genre, you would go to each album and change the reference from “Metal” to “Heavy Metal”. If this were a high-traffic use case, it could become a batch edit operation. This is how file tags work, so it seems like a reasonable place to be when supporting use cases that come from that world, but it still feels a little bit weird to us.
- No-one (to my knowledge) has asked for a way to hide/disable Roon genres as a blanket choice, but we have considered having two switches: show/hide local genres, show/hide roon genres. If you flip both to off, then you start with a blank slate and only see genres that were added using Roon’s editing functionality. Otherwise, you see what you have chosen to see. I don’t like the slippery slope of disabling major product features as a solution to problems, but putting this one out there for feedback.
We’re interested to hear any thoughts you guys have on this topic. We want to make sure that the effort we are putting into this actually solves the real problems.
@danny, @mike, @jeremiah, @AndersVinberg, @audiomuze, @trtlrock, @o0OBillO0o, @Machine, @extracampine, you guys might be especially interested in this discussion.