mb. MASS MERGE RECORDINGS
Merges selected or all recordings from release A to release B
- Review code on GitHub
- Review code and easy install from Greasy Fork
- Review code and easy install from OpenUserJS
- Known bugs
I think this is one of my oldest scripts.
You will often find within a release group, two editions of the same album which tracks link to duplicate recordings.
Merging recordings from those releases is very tedious to do manually.
This script lets you align local and remote tracklists and then it will do the merges for you.
You can either merge all or queue only specific tracks.
You can also match tracks by name and/or by artist credit (default is normal sequential tracklist order).
So it’s a help for the editor.
It can be a very destructive script, you have to understand what you are doing.
In particular you have to know what recordings to merge and not to merge.
Only merge when you are certain that two editions of an album contain the same tracks, for instance.
It’s also a very good help for the voters as it fills the edit note with all kinds of reviewing info like several similarity indicators, track context (release, track number, track name, etc.).
It can highlight problems with the merge edit (helps voting no) or give more confidence to vote yes.
Here is a demo (animated gif) that shows a MASS MERGE session starting from an RG merge review.
In this demo, you can’t see it but I have pressed Ctrl+Shift+m to invoke the MASS MERGE RECORDINGS window — you can alternatively simply click its button, a little bit down the release page right‐hand sidebar, to make it appear:
Some releases have a leading bonus track or other stuff like that, you can shift the remote release up and down with the drop down combo or with ↑ (up) and ↓ (down) arrow keys.
There are various indicators of similarity (track name, track length).
I hesitated long time before posting here because THIS SCRIPT IS VERY DANGEROUS as it does merge recordings — please use it very thoughtfully.