How to effectively merge duplicate recordings with the same AcoustID?

Musicbrainz contains a lot of albums and compilations (usually from Bandcamp in my case) that contain the same song, but each with its own recording*. Looking at a release page (with a load of userscripts) I can open each song’s AcoustID page and merge from there if it has more than one recording. But I still have to check each page to even see if there is something to merge.

Is there an easier way to do this? Like a userscript that shows how many recordings an AcoustID is associated with so I don’t have to check each one manually? Or maybe even a more automated way?


* I guess adding a release with a script is easy, except for checking for existing recordings which is annoying due to having to click each song, and sometimes the correct recording exists but doesn’t appear in the suggestions. And there’s no incentive to do it if all you want is your tagging application to find the right artist and title. A more automated way might also be helpful here.

1 Like

If you have several editions (releases) in the same release group, you can merge the recordings without ultra extensive research, with MASS MERGE RECORDINGS.
But after that, check your open merge edits for mismatches, because it regularly happens that some recordings are wrongly attached to mismatching tracks, in existing albums.

But otherwise, merging, just based on AcoustID and duration, may not be enough research.

There is a very cool script that shows you in what other releases, recordings also appear: Inline all recording’s tracks on releases.

There are also INLINE STUFF (shows AcoustID themselves) and Compare AcoustIDs easier! (shows AcoustID icons only), that can display AcoustID, directly in release page.

And finally: Merge recordings from acoustID page.

3 Likes

I think I have all those scripts. They’re all very helpful in cases where they apply, which unfortunately isn’t here for most of them.

For example https://acoustid.org/track/07f8d45b-81dc-4db2-a4b4-b071870b13aa is one fingerprint for three recordings with the same artist, title, and duration, one recording for an album by the band, two for the two compilations that contain the song.

Your INLINE STUFF script helps check the AcoustIDs, Merge recordings from acoustID page helps merging. What I’m missing is a quick way to see which AcoustID has more than one recording associated with it without having to open and look at each and every page of dozens of songs per compilation.

1 Like

That one hasn’t worked in a long time. Or at least not for me on Vivaldi on a WIn10 PC.

Do you have the latest 2020.9.14 version?
I presume so, but as it works for me on Windows 10 Vivaldi Violentmonkey (and on Android 9 Kiwi Violentmonkey), I ask you.

Works most of the time for me (Firefox+Violentmonkey), though sometimes it opens the wrong page (search iirc), then trying again usually works.

Yes. Though it may just be some security thing stopping the page being opened. I’ve not dug that hard.

Okay… that’s weird. I turned all other scripts off, and it worked! Turned all the other scripts back on and it is still working!!

@jesus2099 and @PacCeggowk9oc clearly your presences has scared it into behaving again.

Extra odd as I had tested it before posting in the thread…

Broke again: Track "1865c595-8384-4c60-9f99-7fae6c4229e8" | AcoustID

But then I have got into the habit of opening every recording so I can check what I am actually merging so ignore my report… happy to work without this.

2 Likes

If I open that page and select all of them then click merge it takes a while gathering info, and then Firefox warns/asks me if I want to open the new window, probably because it took a while after the last action to open. Maybe your browser also has a popup blocker that prevents the window from opening.

2 Likes

Shift + F5 might be binging it back. I know I have some scripts that really don’t like running without refresh and can’t figure out why…

This is exactly what happened to me. I was experiencing the same thing. Then I noticed in the right of the address bar, that pop-ups/redirects were being blocked due the fact that I had recently had to reset my browser.

I had a look at the Compare AcoustIDs easier script, because in principle what I want is easy: For each AcoustID call https://api.acoustid.org/v2/lookup?meta=recordingids&trackid=xxx and in some way mark those AcoustIDs where it returns more than one recording. But I don’t get the async javascript program flow, especially since this probably needs nesting. And none of the websites I found helped me solve exactly my problem, guess I have to reverse engineer it and rewrite it from scratch myself to understand it.