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

**URL:** https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568
**Category:** Web Sources Scripts
**Created:** [October 4, 2011, 9:07pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568 "2011-10-04T21:07:57Z")
**Posts on this page:** 20
**Page:** 49

<div class="post-metadata">

### Author: ![stevehero](https://community.mp3tag.de/user_avatar/community.mp3tag.de/stevehero/32/337_2.png) [@stevehero](https://community.mp3tag.de/u/stevehero)
#### Post date: [July 14, 2023, 10:14pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/973 "2023-07-14T22:14:06Z")

</div>

Code should be wrapped when posting.

```auto
Some code

```

---

<div class="post-metadata">

### Author: ![X-Tropic](https://community.mp3tag.de/user_avatar/community.mp3tag.de/x-tropic/32/7536_2.png) [@X-Tropic](https://community.mp3tag.de/u/X-Tropic)
#### Post date: [July 15, 2023, 12:26pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/974 "2023-07-15T12:26:05Z")

</div>

error with regexp. how to right syntax?  
 ![15.07 - 15-24_FU](https://community.mp3tag.de/uploads/default/original/2X/1/1964aa87d9f788a10d114752f381914c8061d074.jpeg)

---

<div class="post-metadata">

### Author: ![esenfur](https://community.mp3tag.de/user_avatar/community.mp3tag.de/esenfur/32/14353_2.png) [@esenfur](https://community.mp3tag.de/u/esenfur)
#### Post date: [July 15, 2023, 1:53pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/975 "2023-07-15T13:53:11Z")

</div>

I've just tried this for the first time on a song with the correct metadata to ensure it works. All it returns for me is "Sorry, No Entries Matching the Criteria" - Is this in line with the recent update you guys are trying to amend the scripts for?

---

<div class="post-metadata">

### Author: ![stevehero](https://community.mp3tag.de/user_avatar/community.mp3tag.de/stevehero/32/337_2.png) [@stevehero](https://community.mp3tag.de/u/stevehero)
#### Post date: [July 15, 2023, 3:12pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/976 "2023-07-15T15:12:01Z")

</div>

The one you see doesn't work and I don't even have to test it to see that.

I'm back working on them. The zip file will be updated when I have all scripts done.

---

<div class="post-metadata">

### Author: ![esenfur](https://community.mp3tag.de/user_avatar/community.mp3tag.de/esenfur/32/14353_2.png) [@esenfur](https://community.mp3tag.de/u/esenfur)
#### Post date: [July 15, 2023, 3:39pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/977 "2023-07-15T15:39:44Z")

</div>

Awesome, cannot wait to try this out!

---

<div class="post-metadata">

### Author: ![Wannastayunercover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/w/977dab/32.png) [@Wannastayunercover](https://community.mp3tag.de/u/Wannastayunercover)
#### Post date: [July 15, 2023, 7:17pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/978 "2023-07-15T19:17:55Z")

</div>

When I woke up this morning got 7000+ files tagged overnight ... for something that doesn't seem to work you're right. I guess I should switch from marijuana to alcohol to get something working in my life just like all my livesets have been awful to listen to for 23 years.

people can amend the code using  
json\_select "release\_date"  
SayNChars 10

wherever seen to shorten it.  
Have fun in this thread.  
I won't bother checking it back since my own setting of mp3tag is v3.12 with an empty source dir : nuff said.

---

<div class="post-metadata">

### Author: ![stevehero](https://community.mp3tag.de/user_avatar/community.mp3tag.de/stevehero/32/337_2.png) [@stevehero](https://community.mp3tag.de/u/stevehero)
#### Post date: [July 15, 2023, 7:48pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/979 "2023-07-15T19:48:00Z")

</div>

Explain how this works?

```auto
regexpreplace ".application/json">({.)</script><iframe.*" "$1"

```

I don't particularly care if you don't. GL.

---

<div class="post-metadata">

### Author: ![thesuperintendent](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/t/4da419/32.png) [@thesuperintendent](https://community.mp3tag.de/u/thesuperintendent)
#### Post date: [July 15, 2023, 7:49pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/980 "2023-07-15T19:49:56Z")

</div>

Can you give me a message on how you have the auto tag working overnight?  
I've seen your video and it looks insane 😃  
Tried to DM you, but you've got DM's turned off 😉

---

<div class="post-metadata">

### Author: ![stevehero](https://community.mp3tag.de/user_avatar/community.mp3tag.de/stevehero/32/337_2.png) [@stevehero](https://community.mp3tag.de/u/stevehero)
#### Post date: [July 16, 2023, 10:29am UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/981 "2023-07-16T10:29:49Z")

</div>

Beatport has for some reason reversed the track order in the JSON for releases. So in order to get the tracks in the right order a new function was required.

Florian has PM'd me a build with this function so, hopefully, full steam ahead now.

> [@New json\_foreach\_reverse function for WSF](https://community.mp3tag.de/t/new-json-foreach-reverse-function-for-wsf/61572):
>
> Beatport has changed to all JSON and rewritten the site. I'm kinda stuck until I get this new function to rewrite the beatport tag sources. The trouble is I need a json\_foreach\_reverse function in order to get the right track order @Florian. This JSON order of the tracks is the inverse of the actual track order. See Release: [https://www.beatport.com/release/tomorrowland-remixes/1612329](https://www.beatport.com/release/tomorrowland-remixes/1612329) vs. JSON:

---

<div class="post-metadata">

### Author: ![jfbaastos](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/j/c37758/32.png) [@jfbaastos](https://community.mp3tag.de/u/jfbaastos)
#### Post date: [July 16, 2023, 7:12pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/983 "2023-07-16T19:12:58Z")

</div>

tryin to dl  
[beatport by stevehero vTBC.0 Scripts.zip](https://community.mp3tag.de/404) (70.1 KB)  
and getting this error:  
" Oops! That page doesn’t exist or is private."

---

<div class="post-metadata">

### Author: ![stevehero](https://community.mp3tag.de/user_avatar/community.mp3tag.de/stevehero/32/337_2.png) [@stevehero](https://community.mp3tag.de/u/stevehero)
#### Post date: [July 16, 2023, 7:18pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/984 "2023-07-16T19:18:49Z")

</div>

I've removed the link. That's just a placeholder.

The scripts are all now broken due to beatport updating their site and I'm currently rewriting them all.

I'm also waiting on 2 new functions to get added to Mp3tag by Florian.

He has one done and working on the 2nd.

* * *

**Note to all:** You will need to update to the newest version of Mp3tag when it's released publicly for the new scripts to work.

---

<div class="post-metadata">

### Author: ![jfbaastos](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/j/c37758/32.png) [@jfbaastos](https://community.mp3tag.de/u/jfbaastos)
#### Post date: [July 16, 2023, 7:20pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/985 "2023-07-16T19:20:59Z")

</div>

got it!  
the new version of mp3tag i already have 😉

---

<div class="post-metadata">

### Author: ![nexu](https://community.mp3tag.de/user_avatar/community.mp3tag.de/nexu/32/10040_2.png) [@nexu](https://community.mp3tag.de/u/nexu)
#### Post date: [July 16, 2023, 7:21pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/986 "2023-07-16T19:21:35Z")

</div>

I was under the impression that the newly uploaded [3.21a](https://community.mp3tag.de/t/mp3tag-development-build-status/455)) included all the changes needed?

---

<div class="post-metadata">

### Author: ![stevehero](https://community.mp3tag.de/user_avatar/community.mp3tag.de/stevehero/32/337_2.png) [@stevehero](https://community.mp3tag.de/u/stevehero)
#### Post date: [July 16, 2023, 7:28pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/987 "2023-07-16T19:28:50Z")

</div>

No, there's one more.

> [@Json\_foreach and json\_foreach\_reverse access counter](https://community.mp3tag.de/t/json-foreach-and-json-foreach-reverse-access-counter/61578):
>
> The new Beatport JSON doesn't have an identifier for the track numbers and I was wondering how to access the counter when in the json\_foreach\_\* loop. The reason for this is to output to the TRACK tag, TRACK/TOTALTRACKS. So the code may look like this (notice the new SayCounter function) json\_foreach\_reverse "results" OutputTo "TRACKTEMP" # TRACK/TOTALTRACK|TRACKTEMP SayCounter Say "/" SayOutput "TOTALTRACKS" Say "|" outputto "TITLETEMP" json\_select "name" sayrest json\_select "mix" ifnot "…

---

<div class="post-metadata">

### Author: ![bitskream](https://community.mp3tag.de/user_avatar/community.mp3tag.de/bitskream/32/7247_2.png) [@bitskream](https://community.mp3tag.de/u/bitskream)
#### Post date: [July 16, 2023, 11:44pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/988 "2023-07-16T23:44:23Z")

</div>

It strikes me as very odd that Beatport do not have a Track Number field anywhere in the JSON. I wonder if that is intentionally to make scraping more challenging. Anyway, it looks like the new source script is getting close now! I sent a few bucks via Revolut as a tiny thank you for your efforts and expertise.

---

<div class="post-metadata">

### Author: ![stevehero](https://community.mp3tag.de/user_avatar/community.mp3tag.de/stevehero/32/337_2.png) [@stevehero](https://community.mp3tag.de/u/stevehero)
#### Post date: [July 16, 2023, 11:52pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/989 "2023-07-16T23:52:18Z")

</div>

Thanks for that. I'm sure they've internal code for the page to order the JSON themselves. But it is odd that the order of the tracks was reversed and no track ids. I'm sure they have their reasons.

---

<div class="post-metadata">

### Author: ![owlcatz](https://community.mp3tag.de/user_avatar/community.mp3tag.de/owlcatz/32/9883_2.png) [@owlcatz](https://community.mp3tag.de/u/owlcatz)
#### Post date: [July 16, 2023, 11:58pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/990 "2023-07-16T23:58:25Z")

</div>

Yeah I have to wonder if they see all of our requests and are trying to hamper them on purpose to take load off their servers. Then again that's just me who used to run a lot of websites lol. 🤷‍♂️😂

Now I wonder is there a header or something that is sent on these requests that they can identify? 🤷‍♂️

---

<div class="post-metadata">

### Author: ![X-Tropic](https://community.mp3tag.de/user_avatar/community.mp3tag.de/x-tropic/32/7536_2.png) [@X-Tropic](https://community.mp3tag.de/u/X-Tropic)
#### Post date: [July 17, 2023, 11:13am UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/991 "2023-07-17T11:13:05Z")

</div>

Can you please tell me if there is a workaround now?

---

<div class="post-metadata">

### Author: ![owlcatz](https://community.mp3tag.de/user_avatar/community.mp3tag.de/owlcatz/32/9883_2.png) [@owlcatz](https://community.mp3tag.de/u/owlcatz)
#### Post date: [July 17, 2023, 11:33am UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/992 "2023-07-17T11:33:54Z")

</div>

I don't think so Steve said he's waiting for Florian to release the next version of mp3 tag for one last fix he needs.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [July 17, 2023, 12:07pm UTC](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568/993 "2023-07-17T12:07:01Z")

</div>

I've already sent this updated version to @stevehero and I think it's best for all to be patient and wait until both a new beta of Mp3tag and the updated Tag Sources are released.

Watching this topic for news is the way.

[Previous page](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568.md?page=48)

[Next page](https://community.mp3tag.de/t/ws-beatport-com-by-stevehero-release-single-track-artwork-tagging/12568.md?page=50)
