Bug / poor logic in album ingestion logic

The album:

Musicbrainz entries (apple & bandcamp):

https://musicbrainz.org/release/5fc472ac-8e9b-493a-ab3e-2c9b56593966

https://musicbrainz.org/release/46336d55-6685-4081-ade6-3c524e8d3f01

Doesn’t exist in Tivo.

Roon’s answer, despite musicbrainz metadata being embedded in tracks:

To be fair, this was only added to MusicBrainz on 6th September 2020 (today.) Give Roon a chance to pick up the metadata!

https://musicbrainz.org/release/5fc472ac-8e9b-493a-ab3e-2c9b56593966/edits

1 Like

One of the entries is old enough for Roon to pick up; the newer release group from September - it seems - is planned to get merged into the older release group entry from late August. mb is a dynamic source…

What seems strange are the values for Album title and Album artist in the screenshot; doesn’t look like this came from mb. :thinking:

Incorrect, the bandcamp version was added today, there is an earlier Apple music entry “Last updated on 2020-08-28 01:00 UTC”

The data we currently have looks okay here, but it could be taking some time to make its way to your library since there was newer data added. I’d make sure that this album is set to use Roon’s metadata and not file tags and then give this a week or so for your library to have time to update.

That’s the default and I’ve not changed it for any albums in this library. As of now it’s still incorrectly identified. Any reason not to be able to force a re-identification from a mobile client?

Also, given Roon considers the album identified what would trigger Roon to automatically attempt to re-identify it?

Finally, a forced re-identification reverts to the incorrect album reported in the first instance.

Thanks for clarifying, @evand. Can you send this album over to us so I can have the QA team investigate further? Please zip the album and upload it here.

@dylan. Done.

THanks, @evand. I’ve sent this along to the QA team.