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

DaveSumm · May 24, 2026, 11:36pm

This was the problem. All working now, thanks guys!

meomizzle · May 27, 2026, 12:43pm

I just love this community - The amount of talented people is amazing. @The_Zhu This works great, tremendous job, really appreciate the work and the time you have put in to get this up and running again. Obvs big thanks to @stevehero for creating this in the first place, i have used this for years and its like losing my right arm when Beatport mess things up and it breaks!

Thanks again to all involved, fingers crossed BP/CF leave things alone for a bit now lol.

Cheers

meo

Norbox · May 28, 2026, 9:16am

#proxy.py

#The proxy is working flawlessly.

KrissO · May 28, 2026, 8:32pm

Thank you so much The_Zhu!

nilsmarley · May 30, 2026, 11:13am

Truly amazing. Tested and works now

iamyou · June 8, 2026, 2:25pm

This solution is very good, because I just followed the clear instructions, then tried it today and it works well !

Thank you, @The_Zhu

wickedmix · June 15, 2026, 9:51pm

seems like the py.proxy is no longer working getting 403 forbidden

P.unkt · June 16, 2026, 5:39am

Can't confirm this, still working like a charm.

wickedmix · June 16, 2026, 9:30am

must have been temporary py.proxy working again today

RxB · June 25, 2026, 1:15am

Hi The_Zhu? I have a similar problem with the Traxsource plugin by Jordi & Jean-Claude ( [WS] Beatport · Traxsource · SoundCloud — Updated & Fixed Scripts 2026 (by Jordi & Claude) ) a 403 error that is possibly a Cloudflare problem. Do you think you could adapt and compile a Traxsource Proxy same as the beatport proxy ? I tried to edit the sources of your proxy myself, launch a venv and the python script, but that didn't work for me, failed to connect on port 8788 (i changed the listening port, adapted the URLs in the .inc files, , I must have overlooked something, but then again, I'm not a python scripter . I don't even now how to make an .exe from it.

Sergius · June 25, 2026, 4:37pm

Hello @The_Zhu,

I'll be releasing a BSI-Mp3tag project in a few weeks. My programming is finished, and I'll be able to release the project once I've completed my YouTube videos.

@Florian has already given me excellent advice for my project, and one very important piece of advice on this:

You can clarify the situation by writing in a style of text like this:

I am not affiliated with Mp3tag. This registered trademark is the exclusive property of its holder, as is its logo

The_Zhu · June 25, 2026, 4:47pm

Thanks @Sergius, much appreciated, that's exactly the wording I needed. I'll add a clear trademark notice. Good luck with the BSI-Mp3tag release, looking forward to it!

Sergius · June 25, 2026, 5:33pm

Hello @The_Zhu,

I'm glad my text can help you…

Thank you for your interest in my project…

Regarding my upcoming BSI-Mp3tag project, it's primarily intended for programmers at radio stations who use the BSI Simian live broadcast software, which is still receiving updates…

We currently program our tags with BSI Info Editor, which hasn't been updated since 2004, has limited write capacity, contains bugs, and hasn't been fixed since then…

The project I'm about to release fixes all the bugs and allows for more characters for tags. This great Mp3tag program can also manage album art directly within the BSI Simian folder, unlike BSI Info Editor, which doesn't handle album art…

Your mp3tag_proxy.exe project for Beatport.com is fantastic; you're a great help to the Mp3tag community. program, thank you for the time you dedicate to the members of this community…

jfbaastos · June 25, 2026, 6:09pm

dont know why isnt working for me.
i think i did all correct but keep getting this error

The_Zhu · June 26, 2026, 11:28am

Hi @Sergius, thanks, genuinely appreciate it.

BSI-Mp3tag was clearly overdue. Stuck since 2004, known bugs, no album-art support, and the people depending on it work in live broadcast. I really like seeing this: someone picking up an abandoned project and making it work properly. Good luck with the release!

The_Zhu · June 26, 2026, 11:35am

Hi @jfbaastos! That error means Mp3tag couldn't reach the proxy at 127.0.0.1:8787. Quick checklist:

Is the proxy actually running? Look for the Mp3tag Proxy icon in the system tray near the clock (might be hiding under ^). If it's not there, start mp3tag_proxy.exe first, then retry. It needs to be running whenever you use the tag sources, and it shuts itself down after 30 min of inactivity.
After editing scripts, restart Mp3tag via File → Exit, then reopen. Just closing the window doesn't cut it.
Check the line you edited. Error 12005 usually means a malformed URL. Open the .inc file and confirm it reads exactly http://127.0.0.1:8787/... , one slash after the port, no doubles, no stray spaces.
Save .inc/.src files as UTF-8 without BOM, using Notepad++ or VS Code. Plain Notepad can add a BOM silently and break things. Leave .settings files alone.
Still stuck? A VPN or firewall might be intercepting 127.0.0.1, or another app grabbed port 8787.

Paste the exact line you changed and say whether it's Beatport or Traxsource, I'll spot it right away.

jfbaastos · June 26, 2026, 1:41pm

yes the proxy is working wll, i think:

14:43:48 Server listening on 127.0.0.1:8787 (impersonate=chrome124)

is this correct on this file: Beatport by &stevehero v6#RELEASE Direct by &Www(URL).src

[SearchBy]=RELEASE Direct by www(URL)||$trim($lower($regexp($regexp(%www%,(?i)^www,https://www),\bhttp\b,https,classic.beatport),www.beatport,https://pro.beatport,https://www.beatport))||http://127.0.0.1:8787%s
[Include]=Beatport by &stevehero v6_Release Direct.inc

now i added the slash on this file: Beatport by &stevehero v6_Release Direct.inc

Name]=beatport.com [v6.004 by stevehero™] (◣_◢)
[MinAppVersionMac]=1.8.4
[MinAppVersionWin]=3.22
[Settings]=Beatport by &stevehero v6#USER SETTIN&GS.settings
[AlbumUrl]=
[BasedOn]=http://127.0.0.1:8787/
[IndexUrl]=http://127.0.0.1:8787/

and i get this error:

The_Zhu · June 26, 2026, 4:15pm

Good news – your proxy is running and the .inc file is fine. The problem is in the .src file.

In Beatport by &stevehero v6#RELEASE Direct by &Www(URL).src, the last field is missing a slash before %s:

...||http://127.0.0.1:8787%s

Should be:

...||http://127.0.0.1:8787/%s

Add the slash, save as UTF-8 without BOM, restart Mp3tag.

jfbaastos · June 26, 2026, 4:57pm

sorry for still bothering you

now theres a new error.
whay i am doing wrong?

Beatport by &stevehero v6_Release Direct.inc
[Name]=beatport.com [v6.004 by stevehero™] (◣_◢)
[MinAppVersionMac]=1.8.4
[MinAppVersionWin]=3.22
[Settings]=Beatport by &stevehero v6#USER SETTIN&GS.settings
[AlbumUrl]=
[BasedOn]=http://127.0.0.1:8787/
[IndexUrl]=http://127.0.0.1:8787/

Beatport by &stevehero v6#RELEASE Direct by &Www(URL).src
SearchBy]=RELEASE Direct by www(URL)||$trim($lower($regexp($regexp(%www%,(?i)^www,https://www),\bhttp\b,https,classic.beatport),www.beatport,https://pro.beatport,https://www.beatport))||http://127.0.0.1:8787/%s
[Include]=Beatport by &stevehero v6_Release Direct.inc

17:55:27 Server listening on 127.0.0.1:8787 (impersonate=chrome124)
17:55:55 REQ GET /http://127.0.0.1:8787/https://www.beatport.com/release/lara/6932610
17:55:55 REQ GET /https://www.beatport.com/release/lara/6932610
17:55:55 RESP 200 https://www.beatport.com/release/lara/6932610 bytes=124255
17:55:55 RESP 200 http://127.0.0.1:8787/https://www.beatport.com/release/lara/6932610 bytes=124231

The_Zhu · June 26, 2026, 5:33pm

No worries, almost there!

Your file's WWW tag still has an old proxy link in it, so the proxy address ends up doubled and that breaks it. Just set the WWW tag back to a normal Beatport link:

https://www.beatport.com/release/lara/6932610

Then run it again.

(Tip: "RELEASE Direct by ID" — where you just paste the number 6932610 — doesn't use the WWW tag at all, so it avoids this completely.)