Non-existent albums (Release MBID) in Picard 3.0b1

MusicBrainz Picard
1

Picard stubbornly detects 2 non-existent albums

e5a1ba39-7eec-47b1-a270-60062b59114f

c90d8723-37f6-4a17-ae16-6b77d8a61033

a1
a1833×584 21.8 KB

MBID not found
No MusicBrainz entities match the MBID c90d8723-37f6-4a17-ae16-6b77d8a61033. Either it’s incorrect, it was for an entity that has since been removed, or it is an ID for something else than an entity (for example, a relationship type).

and assigns 10 tracks to them.

a2
a21817×1440 419 KB

These 10 songs have their correct data, e.g.,

Rick James - Super Freak, Part 1

from album 80s Music Explosion! which has Release MBID 99f4da5b-e345-4c25-8e79-5249074fbeba

I can provide additional data if necessary.

2

The files have a release MBID that is invalid or no longer exists. If releases get deleted from MB (and not merged) the MBIDs can’t be loaded.

Retag your files against an existing release.

2 Likes
3

So they can’t be deleted from the database?
They’re probably hidden somewhere very deep.

4

They are deleted from the database, that’s why they can’t be loaded anymore.

5

But Picard is getting these MBIDs from somewhere. Where?

6

From the file tags. The files got previously tagged with those releases, when they still existed.

3 Likes