MASS MERGE RECORDINGS :: Merge duplicate recordings from two similar releases

Yes, that works. The main key is keeping track of your target.

I have merged three or four releases into one this way. Just need to keep a keen focus on the direction. As long as they all go into Release A you are good.

It will only fail if you tried to do B to A and then C to B as that goes pop if B merges to A first as the target (B) disappears.

Technically you can do C to B and then B to A as long as it all happens in the correct order. (but that can be messed up with misplaced votes)

5 Likes

Awesome, I was hoping it worked that way but didn’t want to try it with the 40+ track released I am trying to fix.

2 Likes

The trick is open Release A. Then paste in Release B, do your merge. Paste in Release C, do your merge, Paste in release D, do your merge.

As long as you push them all in the same direction into Release A you are good. The trick is picking a good Release A to start with.

2 Likes

Exactly.

Usually:

  • I launch the release merge with releases A, B, C and D to see which one is the oldest (thanks to MERGE HELPOR userscript), by clicking the Row ID column, to order it
  • I Ctrl+Click those 4 releases in Row ID (MBID age) order
  • I don’t launch this merge, of course
  • My base is the oldest release, let’s say B
  • I test if indeed A, C and D recordings are all more recent (thanks to MASS MERGE oldest target auto-select) than B recordings, by pasting the 3 release URL one by one into B release MASS MERGE form
  • If not, I now know which release I should target (B or another)
  • Now I merge reuse by release, towards this chosen target
  • Before taking next release as source, I reload its page to see if its recordings have not satisfy been merged by previous releases

It sounds tedious but it’s quite fast, in fact.

2 Likes

But other than this do-as-we-can-with-what-we-have, I had that multiple release (group) merge in project, among all the MASS MERGE wish list.

But I don’t know if I will finish it, or when.

At the moment, you can already load all recordings from a release group page, to see possible duplicates.

1 Like

I did not know that, that’s pretty awesome.

2 Likes

Off topic but I had to test this because I wasn’t sure what you meant haha. I did not know Ctrl+Click opened links in new tabs, I have only ever known middle click to do this for as long as I can remember.

1 Like

The script instructed me to merge this 10-cd release one disc at a time, which seems reasonable. The trouble is that for the source disc it’s only counting tracks from the single disc, while on the target it’s counting tracks for the whole release. It doesn’t show that all 194 tracks matched up exactly, disc-by-disc, which would be extra helpful here since the source has no times entered.

1 Like

I think I have a ticket for this problem.
Maybe you can check if it needs some better title, description or ideas:

1 Like

I don’t have much technical input, but I think if you’re matching specific mediums within a larger release, then both med#.track#/medtracks and overall#/total tracks would be valuable, but only if you can compare the same info from source and target. (Would probably have prevented the issue you caught.)

It’s not a huge deal, but I also found that for some of the individual discs your script would automatically match it with the same disc on the target, while for others it seemed to align the first track of the source disc with some random other track, until I adjusted it. (I thought maybe it had found a similar track name, but I didn’t get around to confirming that.)

1 Like

Yes, that’s it.
It looks for similar name for the first track (s?).

My keyboard shortcuts to shift remote tracklist alignment with local tracklist were a little clumsy.
They needed the Starting position select combo to be active (focused).

Now I have replaced that with a global keyboard shortcut:

  • On non-Mac OS: Control + Shift + Arrow Keys
  • On Macintosh: ⇧ ⌘ Arrow Keys
1 Like

Is there any way to make the font sizes of the Mass Merge Recordings sidebar larger relative to the rest of the page? The edit notes field in particular is microscopic. I miss a lot of typos because I can’t really read it.

2 Likes

Something’s gone haywire today. Could be related to tampermonkey updates, or the server update?

When trying to set up a merge to here from (remote) here, the sidebar reports 10 recordings to merge but shows nothing in the track list, not even “same recording” for any of them.

If I switch it and try to go the other way, the merge info shows up on the 10 tracks that could be merged and a few of the others show the “same recording” label, but not nearly all.

(I tested with all other scripts off, to be sure there wasn’t another one causing interference)

2 Likes

It works for me on main and on beta, with Android 9, Kiwi Browser and Violentmonkey.
I will test, later today, on a PC, with Tampermonkey.

1 Like

I’ll also give it a try with violentmonkey when I can. May be a day or so.

It works for me (the display, at least), on main and beta, with:

  • Android 9 Kiwi Violentmonkey 2.26.0
  • Windows 10 Vivaldi Violentmonkey 2.26.0
  • Windows 10 Vivaldi Tampermonkey 5.2.3
  • Windows 10 Vivaldi Tampermonkey 5.3.1 with developer mode on in Extensions tab

It doesn’t work with:

Am also seeing something funky.

Win10 Vivalidi and Violentmonkey

Merge this one track single into this album.
One track: Release “Where Is My Mind (Novö Piano Live)” by Maxence Cyrin - MusicBrainz
Album: https://musicbrainz.org/release/17bfae8c-586d-4d4c-8aa2-ee07b9625ea5

Note how it starts at the top, and is visible. Now use cursors to move it down the list to the bottom. It keeps disappearing, then reappearing. It is clearly there are the cursors control it, but I can’t see it.

When I reached the bottom, it is not visible. But hit the “Merge all found recordings” button and the merge happens.

Are you with version 2024.10.16?
I don’t see this issue on my Windows 10 Vivaldi Violentonkey.
Maybe try bu deactivating other userscripts and userstyles?

The version of Tampermonkey beta is currently 5.3.6215