Picard script to consolidate multiple sequential catalog numbers (KDSD-10012, KDSD-10013) into one (KDSD-10012~3)?

MusicBrainz Picard
1

VGMDB uses this format of catalog numbers, which I prefer. Is this possible with Picard scripting?

1 Like
2

I made the same change one time but I was told that was not the preferred way to handle sequential catalog numbers: Edit #107177337 - MusicBrainz

1 Like
3

I’m not talking about Musicbrainz, I’m aware that separate catalog numbers is the preferred way. I’m wondering if there’s a script I can run in Picard to achieve the effect. I think the VGMDB script I have to add new releases has a function to do the exact opposite (split VGMDB’s catalog numbers to fit MB’s preferred style) but I dunno how to translate that into Picard’s scripting.

2 Likes
4

Hm, guess not. Oh well.

5

I thought it might be too complicated for a script, but it looks like it can be done without being a plugin. I’ve started making one, with some caveats*.

For example, releases like https://beta.musicbrainz.org/release/20481a93-72d2-48c0-9da3-29958381dac5 exist, which would be very difficult for a tagger script to achieve what you want (what do you want here? VGMdb’s equivalent data is intentionally incomplete compared to this.)

Caveat*: You have to remember that many editors refuse to store standardized catalog numbers and try to use what’s printed on the cover art despite what the record company might use in their own public database (e.g., whitespace vs. hyphen). I intend to only support standardized catalog numbers and no error handling.

6

That PROE-1903 catalog number seems like it should be for a different release? In this case, I would want COZX-1645~6. I’ve never seen a release that had two completely different labels assign a catalog number like that to the same release before. At the very least, I can say with some certainty that my own library wouldn’t run into that issue.

7

No, that data is correct per the cover art.

8

Huh, well that’s a first for me. Also yes, standardized or whichever you go with is fine. I just don’t want, for example, 1000 to 1050 being listed as 50 different catalog numbers in the meta field.

9

Done.

2 Likes
10

Thanks! If there’s a script megathread or wiki or something, I hope this gets added to it. I imagine I’m not the only one who prefers this consolidated catalog number format.

11

Hmm, I don’t think there’s a wiki page (anyone know of one?)

I have added it to the list on this wiki page, for now:
https://wiki.musicbrainz.org/External_Resources

I have already wondered about making a separate Picard scripts/tools (that aren’t suited to be added to the more ‘official’ Picard website) Wiki page, this will probably nudge me to finally make one - when I have time :stuck_out_tongue:
If anyone wants to beat me to it, go for it!

edit: made the wiki page (thread)