Match To One Album appears okay and then doesnt

[JohnnnnyOppps]

@paultaylor Many thanks Paul. I’m going through, it’s a slog, but I got a lot of albums without thinking this through before! Your tools make it better.

One question- I have an album by the Orishas: https://musicbrainz.org/release/8f6f48f0-ae99-4fd8-8ab8-db92b79c9d27
When I try to Match to One Album, I get a very strange behavior:
On songs, you can see that it is matching track #s in a sensible way

But on artwork it looks like the matches are all over the place - where the file which is clearly track 7 is matched to track #1.

I don’t want to let this complete, so I can’t really upload reports (or at least I dont’ think it’ll help if I do.

Does this make any sense to you?

[paultaylor]

@JohnnnnyOppps

Does this make any sense to you?

Hi, no it doesn’t make sense

What you can do is run Match to One Album with Preview Only enabled so it doesn’t actually make any changes and then run Create Support Files. What might be even more useful is if you could upload the files using something like Dropbox just for testing purposes so I can see if I can replicate the issue.

[JohnnnnyOppps]

Ok, here are support files for this one.

The album is actually this: https://musicbrainz.org/release/22c6fb7f-02d8-487d-8c9b-df1f91ac3f62

It’s in Roon correctly currently identified pre changes as this:

When I go to Match Songs, I get this (you can see the filenames are out of order):

And you can see that in songs the track order has been picked up incorrectly again:

And again in artwork:

I don’t want to say it’s impossible that I’d previously done some bad tagging, perhaps the filenames are incorrect and AcousticID is actually finding that the tracks have the wrong names, Maybe. But I listened to a couple songs on this and another album and they correspond. I just wanted to double check if I was crazy - doesn’t seem like it.

Support files uploaded! (inbound for the other issue)

Thank you.

[paultaylor]

Its a bit confusing but if I look at FixSongsReport0214 it had already been matched to a Discogs release, but only matched MusicBrainz Song Only because it couldnt find a matching MusicBrainz release

Then when you run MatchToOneAlbum0219 you forced the match to https://musicbrainz.org/release/22c6fb7f-02d8-487d-8c9b-df1f91ac3f62 this has same name but different track order to the Discogs release

So I am unclear, are you sure https://musicbrainz.org/release/22c6fb7f-02d8-487d-8c9b-df1f91ac3f62 is the right release for these tracks?

[JohnnnnyOppps]

Hi Paul. Thanks for figuring out that Le Flow issue.

I went back to the Orishas / A Lo Cubano one from before.

There’s something strange in the order that SongKong puts out the order of tracks in the Metadata spreadsheet, and in the Artwork tab. Otherwise, as far as i can see it’s actually doing the right thing - it doesn’t seem to be renaming tracks to the wrong name. I’m pretty sure the release I have is the actual same as the album I have, based on the filenames and track order. But if you look in the Artwork tab it looks (see image I posted above, SongKong is still doing the same thing) and in the metadata spreadsheet as though it’s actually scramblng order and renaming tracks. Uploaded support files - let me know if you can make heads or tails. Thanks!

[paultaylor]

Can you email/upload the album for testing I think that is the only way Im going to be able to give you a definitive answer.