Workflow for large classical compilations

Tags: #<Tag:0x00007f6d4d176080> #<Tag:0x00007f6d4d175f40>

Hi all,

I have a few 100 track classical compilations that I need to add to MB.

Do ONCE:

  • Get tracklist from wikipedia and reformat to suit paste into manual track listing
  • Create release in MB

Do per-CD:

  • Add medium
  • Paste correct tracks for the correct CD and import

Do per-TRACK:

  • Read track lengths from booklet and type into each track listing in Tracklist
  • Click on each Artist and bring up existing MBID (easy, normally the first hit in the pop-up)
  • In Recordings, click edit.
  • In another tab, search for one of the artists credited in the booklet, go to their recordings, and copy the link from the existing MB recording (NB, so far all of the tracks in the compilations are already in MB).
  • Back in the new edit, paste the URL.

And that’s pretty much it - this process takes about 30mins. For a 100-track 10-CD compilation there goes 3 hours.

Can anyone suggest a better/programmatic way of accomplishing this?

1 Like

Why hand typing the track times? Picard would upload those 10 CDs of track times for you much quicker. Or there is the script for decoding an EAC rip log.

Track times in booklets can often include typos anyway.

1 Like

First of all, have you seen the “classical editor toolbox”? If not, check that out:

If you’re adding Disc IDs, don’t bother with this, they will be added for you.

I know it’s generally better to reuse existing recordings (when you know they’re right), but if you want to cut down on time used, drop this step as well and consider using @jesus2099’s “mb. MASS MERGE RECORDINGS” userscript to merge recordings en masse after the release has been added:

In the same vein, what I have sometimes done for multi-CD releases is to add each medium as its own release using a CD TOC/Disc ID lookup (from Picard, isrcsubmit.py, or other means) and then merge all the releases together at the end. If you know the full track listing though, it will probably be quicker/easier to use the track parser to populate the release and then add Disc IDs afterwards.

3 Likes

Old reply I know…

I’ve taken a quick look at the user script. It seems geared towards multiple releases in the same group (similar track number and sequence).

In the case of the 100 track release, it’s associated recordings are all over the place, across many other releases. Am I right in saying the Mass Merge script isn’t much help here?

Thanks

1 Like

Yes indeed, this (MASS MERGE RECORDINGS) script is intended to be used between multiple editions of same album, with only slight variation of tracks, or between a compilation of several albums in same package and the actual albums (maybe it’s your case, here): you can align/shift tracklists with up and down keys, or you can type 13 to align remote tracklist track 1 to local medium 13 track 1, when the track selector is focused (it’s focused by default).

It can be used in other cases, with match titles button, but the result is very unsafe (less likely legitimate), and I discourage from doing so.

2 Likes