Tell that to the artists - they are the ones getting “screwed” in this. It is estimated that between 25 and 50% of royalties due are misallocated because of incorrect/insufficient metadata (streaming or even sales). Its better to burry your head in the sand (or in your headphones).
Completely with you here. If I want to dig deep into Miles or Billie Holiday, Ike Quebec - it’s just not there. But it is out there and this is a premium product. Expecting way better from Roon on this area. Years and still not there.
So I buy a lot of music, mainly pop and rock, and frequently I will buy from the artist’s website direct. I used PledgeMusic for a time, and fortunately all the artists I supported there got their money, but now just go direct. It’s a bit more costly but I hope that, in some small way, it helps offset the loss of revenue from what the streaming services pay.
I also tend to be out of the house a lot and, although I have my music server set up to stream my owned content to my phone or computer offsite, I still stream from Tidal or Spotify, hoping, again, that in some small way they get a bit of coin out of it. Maybe my thoughts are misguided in this area, but, I try.
It never occurred to me about the metadata, mainly because the artists and songs I listen to, even back to classic rock stuff of the 60’s and 70’s, always seems to be properly coded in my apps, so I never perceived a problem.
I am also undecided if I want continue using Roon, and yes, my only issue is not being able to use my own metadata in the event there is something wrong with what’s provided. Simply add my vote as a feature request.
Indeed, and as a premium product we expect much better. If it was a best-effort part-time project reliant on donations then maybe we would accept years of tinkering without fundamental improvements.
33 posts were split to a new topic: Posts about leaving Roon
I’d wager that males, affluent, 80%+ of which over the age of 50 and mostly caucasian should be all the explanation you need as to where the entitled behavior comes from.
There are Roon KB articles on album tagging and editing how Roon presents things. If I don’t like what Roon comes up with, I select “choose file”, which assumes the file was correctly tagged in the first place. Never had a problem with dbpoweramp. I suppose the next step would be to share your edits for the greater good.
I understand your irritations, but after 3 years of payment you have Roon allmost for free. Lifetime.
From the inside (paying member) it’s easier to influence Roonlabs to make changes then from outside…
I happen to think my point of view on the issues surrounding Roon are not totallly irrelevant, and that the discussion has generated some suggestions and ideas.
I basically said what i had to say in my first post, and expanded further later in reaction to some comments to detail further some aspects: why i think metadata is important both for the end user and for the industry as a whole.
As for the “drama”, I was only referring to the TONE of the last messages, which I find inappropriate - there is no point in posting comments on forums which only mock and denigrate others.
Anyway, as you rightly point out, I have made my point and am done - I wish Roon would have offered some feedback on their strategy and how they see their product evolving, but they have not, which could mean:
- either they feel the issues are not important
- or they do not have a clear strategy to address them, at this point
No problem, no sweat.
Mods come into these type of threads for two purposes:
To check whether an unhappy user is missing something. It’s a big product and very few people know all of it (I’m not one of them). So far as I can tell @anon49565150 isn’t missing anything and has accurately and politely described why Roon isn’t fitting his requirements;
To make sure other users don’t pile onto a perceived critic. The admins have asked us to watch for that and ensure people who are critical of the product can have their say. Obviously there are sometimes trolls who intend to inflame as well as criticise and occasionally a thread may have to be closed to avoid the reaction getting out of hand. Thankfully that still seems very rare.
I was pleased that this thread seemed to follow a more mature path, at least initially. We really should all be able to listen to people who have a different experience of Roon without getting upset.
The OP never committed to lifetime. He bought the annual license. It’s not cumulative. You have to pay the whole fee upfront.
My renewal is tomorrow or the next day. Would not want to be without it.
The best solution to the ”why I’m not renewing” dilemma, is to buy a lifetime in the first place. Honestly, it saves a great deal of worry
In my opinion @anon49565150 was very corteous providing reasons for his exit, in an elaborate way that can be of great value to the Roon team and product. Roon will never (hopefully) be everything for everybody, but I for one, surely want it evolve. No, I wont like every product change, but then you can always make your voice heard here.
I think a way to come back on track with this initial post is to get an answer from Roon as OP made some valid points and demonstrated why. Would be nice to have the opinion of Roon on these points to at least understand if these have been acknowledged and if they will be addressed in the future.
The rest, is just noise.
They are rather different. Yate provides a comprehensive toolkit for metadata modifying but you can only match to MusicBrainz one album at a time, and it takes the metadata from MusicBrainz as is. SongKong is designed so you can apply to your whole music collection, and applies more intelligence to MusicBrainz metadata such as resolving some of the issues with Classical metadata in MusicBrainz, such as correctly identifying the track artists in a consistent way.
If you have any questions about SongKong feel free to contact me on the Roon or the SongKong forums
I really think Roon would solve alot of its metadata issue by switching its primary metadata supplier from Rovi to MusicBrainz, and just using Rovi as a supplementary source where necessary.
- MusicBrainz has artist entities, this would solve the problem of confusing artists with the same name
- Generally the data is rich and correct, the database model is more sophisticated then other models.
- Data is freely downloadable, don’t have to use webservice (probably Rovi database do have to use webservice)
- Apart from the MusicBrainz Edits themselves the MusicBrainz metadata is a series of non -copyrightable facts and hence there are no licensing issues with the data (it is available under a public domain license)
- Data is editable by anyone so Roon customers can help resolve metadata issues themselves by editing/adding MusicBrainz data
There are two major problems with MusicBrainz
- The database is not as large as Rovi
- There are some decisions regarding Classical (such as having composer set as track artist) that are bad decisions
But both could be solved.
- Roon could switch their resource currently used with dealing with Rovi to enter data directly into MusicBrainz, and leverage their customer base to help. (also quite easy to import data from Discogs/Bandcamp etc into MusicBrainz)
- Roon can augment the MusicBrainz data with their own database. For example although MusicBrainz does not identify classical/non-classical releases an algorithm can be written that in most cases can identify if Classical and take action accordingly.
How did they ever come to make such a stupid decision, there a rationale expressed somewhere?