I’ve decided to use dramatic titles to get more attention.
Since I’ve started using Roon, I’ve had no problems spending enjoyable time configuring Roon to my network topography and in adapting my network to Roon. Indeed I built a new computer to serve as the core. At 2 houses.
But I’ve felt funny about grooming my media collection to work with Roon – a little queasy doing things like choosing the preferred release version, identifying albums, applying tags, and otherwise grooming the media collection to work best within Roon, which is far more time consuming than software and hardware config. I couldn’t identify why I felt like that. Until today.
I’m uneasy because if Roon goes away or I go away from Roon, there is absolutely no preservable value from my work within Roon on my media collection. Choosing preferred versions, creating tags, identifying albums, it means nought to any other media player or system. Outside of Roon, these don’t exist.
Foobar and JRiver, among a host of others, don’t work this way. Grooming the media collection is done by organizational techniques outside of the player itself - mainly metatags, images in the media folder, file and path name. Organizing via these techniques makes the media collection portable from software-to-software in a way that Roon disrupts. It’s all in a proprietary database that only Roon understands.
So, Roon is brilliant for creating this Venus Flytrap. But we’re onto you.
To the point: I believe that any collection grooming work needs to be exportable with the media. There are limited options for this, and the obvious one to me is creating custom metatag fields that can hold multiple values - “Tags” is the obvious one, but there is actually quite a substantial amount of media information that the user has to correct/input to get Roon working perfectly, and the vast majority could easily be stored in custom metadata embedded in the media files. To validate this investment of time, we have to be able to take it with us if we need to.
I’d love Roon’s own metadata in there too - lyrics, band bios, album reviews, but certainly that is just icing on the cake. But we definitely need the cake - we need to be able to export the user configured media data that we input into Roon. I’m not talking about genres and things that already export - but rather the deep stuff that takes time and effort on an album by album basis, and sometimes track by track.
Roon could fail as a business (I hope not - I really love it). Tidal could fail as a business or de-integrate. Roon could be bought and the model integrated to a service we don’t want to use. There are many reasons we cannot assume that Roon will manage our collections indefinitely. I thought I would use Foobar forever.
So please, help us dedicate our time to Roon by not making it a sunk investment.