In the next step I apply the data from the right side to my local files on the left side (similar as Picard does it).
BUT:
Since a week or so, I observe that mainly imported releases from Bandcamp doesn’t match my local releases anymore. Tracks differs in track length and/or track names. It looks like this:
As you can see the first Track called “The End” is the first track on both releases (on the left side my local track, on the right side the data I got from my local MB Server). But the Track length differs by 3 minutes!
My local Track with a duration of 08:14 exists in the data as Track #7 with a title “Take Off”.
I just want to ask you: Do you see this behaviour with your own releases too?
Could it be that Bandcamp releases change the tracklist names or order after the initial publication?
Addition:
This is how it looks in Picard. The first attempt is a Cluster with LOOKUP (resulting in “green” tracks, but great duration differences) and the second attempt is with SCAN (resulting in “yellow/orange” tracks, matching duration, different track titles):
@MrClon Thank you for the link. If I hear the first song on soundcloud.com it sounds the same as my local song #4. So yes, wrong local filenames/tags could be the reason.
Do you know, if Bandcamp/Soundcloud changes tracklist names after the first publication?
IDK, i think author can do it, especially on Bandcamp. But wrong local tags/names much more likely. I seen that few times. For example when files have no track number in name, but tagger (software or human) believe that files ordered by track number ergo first file in folder is first track in tracklist
The MB release entry is correct in so far as it follows the Bandcamp upload.
“VA-Mirror_Fantasy-(RITMOFATALE2)-WEB-2020-BABAS” is correct in so far as it follows Deezer/Beatport
It just so happens that for some reason the Bandcamp upload and entries on other digital service providers are not in sync.
