New metadata provider?

@support … was there a change in a metadata provider recently?
I noticed (happy) that Angry Anderson isn’t an ohio based garage band but the australian hard rock legend now with bio and so on. (4-6 months until this happend …ok)

But I also noticed that roon now garbled some others, means Ajren Anthony Lucassen aswell as Ayreon and Arjen Lucassen’s Star One now all share ‘Ayreon’ (group) which is also give a birthdate.

Haven’t digged through the whole lot, but it looks pretty disappointing now since I suffer from multple artists now, which I preceisely declared to not use the roon assumptions since being wrong. And now all these seem to have been reset and I have no idea why this happened.

Another easy example where this issue get’s easily detected:
Any help / idea?

Got more but a dozend of these where an artist got simply split up. And no I don’t use the ‘merge artists’ feature since if I would this list would become pretty hard to handle since having some hundred entries.

There’s more exciting one where roon realised that there’s 2 artists being identically named, and the funny thing it that the artwork provided sometimes doesn’t match the bio. Came across one where the picture did show a norwegian band while the bio described the british artist and the artists linked were simply spread as if using a watering can.

Not to mention that I found entries where an artist got listed 2 times and each of them did contain the very same album.

Can’t help myself something got seriously broken while I was in bed … perhaps I should lay back and wait if that get’s redone until I get up again?

That shows us again how dangerous beds can be. :wink:

As far as I understood there’s work ongoing to better handle multiple sources as well as equivalences. Maybe things get straightened out once this project matures / comes to an end.

I know … some go to bed being their last action in life … :wink:

Wonder where you got this information from … and yes I’m convinced it got to do with either differnt metadata handling or additional metadata provider, since some bios did materialise which haven’t been there before as are some yet unidentifier artits known to roon since yesterday eve.

Wonder why they didn’t simply put a spoiler / comment in here saying something such as “in case you experience strange effects … be patient … something exciting will happen soon”.

Better but asking oneself if the database got broken somehow.

1 Like

It was mentioned a couple of times by Roon staff, especially in the Artist Equivalence issues thread.

1 Like

… but (as for “solved”): I believe the feedback is valuable when things go wrong. So Roon can (fine) tune its code. It sure helps pointing out when things seem wrong.

@StefanB How many duplicate artists do you have?

…because Transparency Rn’t Us

I digged till arists starting with B and had 10 till now.
And some by now have 3 in a row (3 times Alice Cooper, 3 times Al Anderson)

Granted Alice Cooper must be 2 since the band vs, the individual.

I do think to know what happened, since the pattern shows that only artists are affected which were unknown to roon till yesterday.

A short workflow from the day in day out roon user suffering from huge gaps in metadata which might be part of the issue, better said I would bet a tenner it got to do with it.

you add an album to roon and not it goes like this
if roon already knows an artist with the same name it adds the album to this artist
roon creates a blank artist with the name given

this works as long as the user doesn’t find out that roon knew about a country singer while the album added was one from a Metal group.

So the user now does the following thing. Select the album, remove the artist, create a new artist identically named and add this one to the album.
Result 2 artists with the same name on being the country dude, the other one the metal band.
Everything fine apart from the fact that the metal one misses the bio and credits, but one could add at least a small chunk of information such as formed, disbanded, or birth, death and an artist artwork. Suits if you ask me since way better but the metal album with a country dude bio.
Now assume one adds another album .and sticks that one to the correct artist.

Then we had black-roon-nightmare yesterday
I assume the following.
roon got aware of that metal band and simply provided this artist + bio and so on.
And it was aware of 1 (not both) albums belonging to that artist.
So what happened it moved 1 album from the user-created-artist to the newly available artist and the result was 3 artists
the country singer
the user-created metal band (which had 2 albums attached and not reduced to 1 left)
the newly known to roon metal band (which ripped one album from user created artist)

The intelligent way would have been … “stack things which aren’t 100% precise” and present the user a query in the form … we found artist information and detected you already have 1-n of them. Should we merge the data with one of them, if so select, if not press skip"

Not to mention that it’s very complicated to find out which artist entry is which one in the end, especially if they share the same artist artwork. I spend more but an hour to find out why the hell 7 Bob Seger album tend to get show by 2 Bob Seger dudes with the same picture. And in all the selected boxed I can’t even tell you if I select on of the entries which one it exctly is. Should I renew my request for a flag in the setting which would show a database object ID if being turned on, so that one does precisely know which object one works at?

Anyway … found a pretty poor way which helps adressing this misery. I can simply selected both entries of duplicated stuff and revert all changes. This most times leads to a single artist, but then I epxerienced that I do loose manually attached hi res artist images while roon provides thumbnail alike ones. And there’s no way to export them first.

if you could point out on how to generate a list of all artist it might be way easier to tell you the exact number. Normally one would use an sql query upon the database or such like …

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.