This okay?
I think it would be best to combine this into the genre tag. So in the example:
Trance (Main Floor) | Tech Trance
This is the code (You can add this above OutputTo "GENRE")
OutputTo "SUBGENRE"
json_select_object "sub_genre"
IfNot ""
json_select "name"
SayRest
json_unselect_object
Endif
Say "|"
sub_genre now parsed and added to the genre tag like so: Main Genre / Sub GenreThats perfect. Thank you
I'm wondering if it's possible to implement or modify one of the scripts in the bundle to allow searching based on the ISRC metadata from file?
I know it's possible to copy and paste an ISRC into the Beatport search bar, but is something like that possible from script?
Thanks for your time.
Is that for single track scripts? I can't imagine this being useful for the album ones.
Yes, it would make the most sense for Single track script.
If doing a release it would make sense to use the current approach (release number), but a different use case would be if Beatport search accepted UPC number (untested) by me. Not as important.
This is a bloody gamechanger, mate. I use 'Cogs as my primary, but so much from BP isn't in there and this works perfectly. WELL DONE.
How do I change the output from VA to Various Artists?
Hi.
Sorry if I'm asking a question that probably has been already answered...
Would like to know, how to tag a folder (for ex. 100 tracks)?
Do i have to go ad tag them one by one or is there another way?
THNX for your great work Steve
Answered a right few times. These are separate track listings and you want to do them all together? Not possible but otherwise follow the previous reply by @xaoc.
thank you for your answer.
it's a various artists folder, compilation... 100 different artists and tracks.
i normally use the script (file name) to search and apply the tag, unfortunately, i failed to find the ( line: while "<>" 99 ) section to eventually change it! Do i simply have to add it to the script?
Hi, I have been using your scripts for many years now. I would like to know if there is a way to speed it up because these new versions are very slow for me, while I have one for Apple Music that works really fast, that someone has fixed its speed because I don't need it to find me 150 tracks for each track I'm looking for. I use the filename version.
Hi Steve. I'm a long time user of your Beatport script and am coming back to it after some time. I am trying without luck (so far) to write the catalog number to the CATALOGNUMBER tag. I use mainly track search by artist and title, and by filename, and then same for 2 release by src's.
Could you point me in the right direction how to do this and which src files to edit?
Edit: I have searched through the forum and found some older posts but nothing that has solved this for me.
Edit 2: I see the Beatport WS settings in the UI, nice addition since I was last active on MP3Tag. I decided to ditch CATALOGNUMBER and just go with what is available out the box from the script. Thanks again, as always, a consistently excellent script.
Sorry, very late on this reply. Not sure if it's possible to limit the json_foreach loop. @Florian, is this possible?
Hi @stevehero (or the Mp3tag community), I'm using your **Beatport by &stevehero v6_Track Search.inc** script (v6.007) and I'm running into persistent technical issues trying to correctly pass the **Label Catalog Number** to the tagging screen.
Could someone explain me how to extract the `catalog_number` (label's number, e.g., 'BLV6671508') from the search results, pass it to the URL, and assign it to the `CATALOGNUMBER` tag, instead of the Beatport Track ID (`BP SINGLE TRACK #...`).
Thankk in advance
Hi, in your single-track scripts, do these things.
After:
OutputTo "BPM"
json_select "bpm"
SayRest
Add:
OutputTo "CATALOGNUMBER"
json_select "catalog_number"
SayRest
Finally, delete:
# CATALOG #
OutputTo "CATALOG #"
Say "BP SINGLE TRACK #"
SayOutput "BEATPORT_TRACK_ID"
Releases with 100+ tracks are not scraped correctly. Script cuts off everything after the 100th track.
Probably nothing you can do about it, but I wanted to inform you.
Not much I can do about this without having direct access to the API I would say.
Is this Beatport WS “broken” now (Monday, 23 MAR 2026) ?
As soon as I run the script, in v3.34 Beta 4 or 6,
and choosing any ‘option’,
I immediately get the error:
“Sorry, no entries are matching your search criteria.”