[WS] Beatport.com by stevehero [Release, Single Track & Artwork tagging]

Not possible, as beatport dictates the album artists not me or the scripts. :upside_down_face:

thanks for the work and the support.
Sorry for a nb question, but i just extracted the files in the source folder, restarted mp3tag (v2.96), and i still cant use the pluggin: it doesnt show in the ui and the shortcuts dont work. Is anything wrong with that new version?

Also, I am struggling to understand what the different scripts do, could you please explain what

  • Artwor K - by Release www(URL).src
    and
  • RELEASE Direct by B EATPORT RELEASE ID.src

mean, for instance, please?

thanks

aure

See here for ways to find the right place for the source scripts:

Ignore the part about the Windows store.

Welcome to the forum. In the starting post there's a link to show how to install them.

For the keyboard shortcuts you need to press the Alt key then the S key, then the letter A like the example below.

You'll see the scripts shortcuts from the underlined text like so:

071Rc1reMW


As far as what each script does it's fairly self explanatory from the starting post. If the script has direct in the title then it's when you have already gotten the WWW tag. Then there's artwork, release (for albums) and single (these are for when you only download a single track from a release).

Since yesterday, I get many 500: Internal server Error, when attempting to tag a bunch of tracks. This happens irrespective of the type of Script (Release, Artist+Title, Title, ...), and randomly (some tracks can be found, others can't)

Did Beatport change something recently or is it just me?mp3tag_beatport

Any ideas?

I'll investigate this should it be down a couple of days. Let me know if that's the case.

The site appears to be working though. :heavy_check_mark:

Great, thx. I'll let you know if it's still nolt working early next week.

It seems that the classic.beatport.com search is broken again. Same 500 error.

yep, still not working for various searches. The error occurs for searches by

Artist
Release
Artist+Release
Artist+Title

In the meantime, you may switch between those, occasionally one of them succeeds.

This usual means there's a problem on the beatports server side. If you google a 500 error it'll tell you all you need to know.

It's real. I've tried to pinpoint exactly what queries cause this 500 since some searches will work while others won't. At first I thought that mp3tag will return 500 if there are more than one word in the query, i.e. queries by Album such as "Anything Goes" will fail every time, while "Anything" will always return results.

But then I tried other words such as "Uniformity" and "Society" and they were failing as well, while the two-word queries "FD CTRL" and "Woo York" were working. It seems arbitrary.

The only good news is that tagging via WWW(URL) works without fail.

Same problem here...500 error

1 Like

@stevehero: What could be causing this behavior?

  1. Searching by Artist+Release produces the error, while Artist only does not
  2. Any search involving e.g. Pegboard Nerds --> error; manual search on beatport works fine

If we can narrow down the issue, we may be able to build a quick fix for this.

1 Like

Cannot confirm this - sometimes searching by artist & release works, sometimes not.

Searching manually on classic.beatport.com itself fails quite regularly: "Oops... looks like there was a problem with your request."

Then it's not a problem with the script as it uses the classic search url to parse the info you see in the first UI. When beatport fixes the problem, this issue will be resolved.

Temporary fix for release search : add the release date.

Just tried with "Ugur Project Phoenix EP" and "Ugur Project Phoenix EP 2019" .
For sure this issue is from their side.

Not always working either, @Wannastayunercover.

Check e.g. "D.Gol'man My Entrance EP" vs "D.Gol'man My Entrance EP 2019". Sometimes, just using Release or just Artist may work. Until BP fixes its search, we will need to try all possible combinations :frowning:

As Steve said the script works as it should. The issue in on the beatport side, i wrote them and i got the following message:

Hi,

We have reported this issue. Unfortunately we cannot guarantee when this will be fixed as we have multiple product launches at this time. Also please note that Classic will be decommissioned in the future. We recommend using beatport.com at this time. I apologize for the inconvenience!

So it seems that they gonna close the classic.beatport.com soon

By the way stevehero i didn't see the traxsource milestone that you have created... I didn't recived any notification by email on that thread, and i assume that there are more users that didn't know about it. I don't know if maybe is there any way to tag them all and re-open that. Also maybe you can do the same with a script that works with beatport.com api directly, create a fund raising. Thanks