A multi‐source seeder for digital releases

Tags: #<Tag:0x00007f756ad9fe90> #<Tag:0x00007f756ad9fdc8> #<Tag:0x00007f756ad9fd00> #<Tag:0x00007f756ad9fc38>

It just occurred to me that it would be nice to add support for Bandcamp and/or Beatport sometime in the future:


Beatport provide a barcode?

Not that I noticed. They do provide catalog numbers, though (something no other digital store does, to my knowledge).

Ok because as far I know @marlonob uses the barcode to match release across streaming service.

1 Like

It’s possible they store that information somewhere that’s not publicly visible (as is the case with Apple Music/iTunes).

I hope :crossed_fingers:t2:
Maybe like Bandcamp:

1 Like

Beatport stores barcodes, but unfortunately they don’t appear to expose them through the API or the public website. Sometimes the catalogue number field contains a barcode, but I don’t think the API allows you to search by catalogue number. :frowning:

Example: This release has an EAN for a catalogue number, and that number matches on Deezer, iTunes, and Spotify. Same release.

While we’re on this subject: Sometimes an album, EP, or single on Beatport has a different barcode than it does in other marketplaces. Examples:

Blasterjaxx feat. Junior Funke - Monster:

Blasterjaxx - Perspective:

One reason this can happen is that Beatport deals with labels directly, but on other marketplaces the material might be sub-licenced to another company.


a lot of times they provide a catalog number, which is actually the barcode.

How many tracks does this release have? 25 right?

Let’s look at the iTunes version:

Nothing has changed it seems…

Oh look, if I buy the whole thing it’s 26 tracks:

It’s not detected unfortunately (or rather the iTunes API doesn’t seem to provide this info) and instead a‐tisket links to other listings missing the 26th track.

The 26th track at iTunes is a booklet.


That is just weird. It doesn’t even show 26 tracks on THEIR site. I can see if maybe the atisket just didn’t pick it up, which I’ve seen sometimes when there are videos on the tracklisting, but this is the first time I’ve seen this and I don’t see how anyone could ever have known without it being purchased.

Not that I noticed. They do provide catalog numbers, though (something no other digital store does, to my knowledge).

FYI the following is a list of digital stores that provide catalog numbers:

  • Beatport
  • Juno Download
  • Boomkat
  • Bleep
  • Traxsource

Bleep sells both physical and digital versions of releases and only provides one catalog number for all formats so I don’t tend to treat it as an authoritative source.

Both Beatport and Juno Download seem to perform some sort of internal “standardisation” to catalog numbers. Juno Download strips non-alphanumeric characters and adds a space between the letters and numbers. Beatport just strips non-alphanumeric characters. Also as noted above, sometimes Beatport just lists the UPC as the catalog number.

Using Anunaku - Stargate EP as an example:


A bug I’ve noticed: This Spotify release doesn’t list the track ISRCs. I think it’s because the ISRCs for this album actually have dashes in them on Spotify, which most other tracks do not.



It’s a digital booklet. See that release on Amazon: https://www.amazon.com/dp/B08256SM9S

Another example: https://musicbrainz.org/release/92a398ad-06b5-4ad4-8700-fa9fb42d4661
(can’t set medium type as MB doesn’t allow to do so)


You’re right. Totally failed to notice that. :blush:
In the past iTunes web preview did show if there is a booklet. They no longer do which is really annoying.

Well, booklets shouldn’t be added as tracks anyway. Data tracks are meant for CDs.
Digital booklets should rather be uploaded to the CAA. If you don’t have it an annotation would be good.


I don’t know if it’s been mentioned yet in this thread, but if I’m trying to seed a particularly long release (e.g. around 60 tracks or longer) the seeder will time out and not load the release. Is there a way around this, e.g. by increasing the allotted wait time if a release is X tracks long?


The tool is no longer working as intended. When adding the releases from it, MusicBrainz requires me to login even though I’m already logged in and when I do, the release info is completely blank with the following errors:

  • Unknown field: password
  • Unknown field: remember_me
  • Unknown field: username

Do you normally edit through musicbrainz.org or beta.musicbrainz.org?
If the latter, that may be the issue. MB doesn’t log you into both the live and beta sites at the same time, so if you primarily use the live site you’d be required to log in again to access non-public pages on the beta site and vice versa.


It’s been doing that to me all day today as well. Quick solution is to log in and check remember me, than when the blank import comes up, close the tab and import again and it works.


@librious, @tigerman325 and everyone else plagued by the “not logged in on release import” error, web browsers are changing when cookies are being sent.

If you import a release with one of the many userscripts or a-tisket MusicBrainz depends on a specific cookie in order to identify the user otherwise you can’t add new data (except CD stubs).

As a Chrome user you can revert to the old behavior by setting browser policies.
Add [*.]musicbrainz.org to ​Legacy​Same​Site​Cookie​Behavior​Enabled​For​Domain​List

Users of a Windows Home edition can use Policy Plus as an alternative to the group policy editor.

Restarting Chrome should make the policy take effect. This will also be indicated in the Chrome menu.

The reason why logging in again works is because the cookie date is being refreshed and thus triggers the “Lax + POST” mitigation.

Firefox has not yet enabled the new behavior by default (except for Nightly) but it will happen sooner or later.


Hi! I just started using this piece of code, and it’s great! Thanks a lot!
One idea I’m having: As the audio files are accessible on both deezer and spotify (I don’t know about Itunes), could it be possible to use it to compute and submit the acoustid of the recordings? It’s a very useful tool to find duplicates and could even be used when creating a new release (to spot which recordings are already in MB).