ISRC script

While viewing:
https://musicbrainz.org/edit/59318659
I saw reference to script https://pypi.org/project/isrcsubmit/ / https://github.com/JonnyJD/musicbrainz-isrcsubmit

Has anyone yet to spend the time to parse such information from digital file metadata?

1 Like

Not that I know of. But an easy solution would be to have this as a Picard plugin.

3 Likes

That was one of the uses I had in mind as well, plugin for Picard. I am sure you know I like ISRC and believe it is more important than a lot of the other stuff when it comes to digital. My interest is that should there be a way to do a mass batch, I have many thousands of files I could run through it. I would need Picard however, I do not have MBIDs in my metadata for iTunes files, which are the ones that would be easy and consistent to pull them from.

Maybe I misunderstood or I’m just confused: I thought this was about submitting the ISRCs that are in the file’s metadata to MusicBrainz. But if the ISRCs are not already in the files this won’t work :smiley:

No, I think you understood correctly the first time. In my metadata, I rarely have MBIDs, the MusicBrainz ID for the album and recording and such. This basically prevents me from using things like the acoustID fingerprinter (separate app) because I have no static matching to the MB database.

Now my iTunes files all have the original iTunes data, which usually includes the ISRC. So for me to get it to MB database, I would need to do a manual match for each album, but it is still far more bulk import than having to do each one individually via the web UI.

So what I mean is that I could, in theory, load in a ton of albums and basically watch them all match to make sure there are no errors, then import away. Emphasis being on the watching for errors on the match or the whole thing becomes counterproductive.

Ok, I think I’m with you again. Just to be clear: My idea was to have this as a plugin, which would allow you to right click on a loaded release and select “Submit ISRCs to MusicBrainz”. You would of course need to match your files to the releases with Picard first, at which point you should also save the MBIDs to the file.

So it would make it easier to submit, because you could do it in the same tool (Picard) right after matching a couple of files. But you still need to do the matching part first for the files you haven’t matched yet, so it’s not a big time saver as opposed to using an external tool.

Still I think we should have this plugin. But not sure when I will have time for it, so if anybody else wants to give this a try please do :wink:

6 Likes

Yes, same page. Only difference I have is where you state:

I do not save anything to files with/from Picard. I use Picard only as an import tool to upload data to the MB database. At this time that means adding a new release or submitting acoustIDs, at least to the degree the system currently allows and supports.

1 Like

It would be very bad to submit for multiple releases at the same time.
It reminds me of nightemarish multi‐release‐barcode submissions.
It’s better per release and with edit note citing the source.

4 Likes