Use the direct by URL scripts. Your tags must have the correct info for this to happen.
Thanks for reporting, is this the TRACK or RELEASE scripts.
Use the direct by URL scripts. Your tags must have the correct info for this to happen.
Thanks for reporting, is this the TRACK or RELEASE scripts.
I fixed them in my tracks scripts, I never use the release searches except Beatport by &stevehero v5.0#RELEASE Direct by &BEATPORT RELEASE ID manually, the rest is done automatically.
https://drive.google.com/file/d/1J23oNNn5pkH05hrsKchVvOK0oQlbjopC/view?usp=sharing
Fixed in the latest. The WWW tag was affected too.
Hi guys
I haven't used the script for a while and see some nice updates, but I can't remember how to do these things:
How do I append " (Original Mix)" to the end of a track title?
How can I make the results to display in ascending release date order? (I used to do this on the previous build I was using, but can't remember how)
There's two scripts for that.
Beatport by &stevehero v5.0#RELEASE Search by (Album)Artist + Release (Sorted by Date Desc).src
Beatport by &stevehero v5.0#RELEASE Search by (Album)Artist + Release (Sorted by Date Asc).src
Original Mix can be activated by commenting out replace "\"Original Mix\"" "\"\"" by placing # at the beginning of the line.
Thanks! Is it possible to list results be ascending date order using the Track Search by Filename?
Also, when I press ALT+S and then +L, the +L does not work work and I have to navigate to this .src by mouse. Am I missing something obvious here?
In that .scr file use this over what's there for [SearchBy].
[SearchBy]=TRACK Search by Filename||$trim($regexp($regexp($regexp(%_filename%,'\b-\b|_', ),'(?i)\[.*\]|cd\s*\d*|[^\s]+\.com|\bep\b|feat\.|ft\.|\bom\b|\boriginal\b|\bclub\b|\bmix\b|\bremix\b|\bthe\b|vinyl|web|www[^\s]+|[^\w\s]|\b&*amp|\b(various artists|v\.?a\.?)\b',),'\s+', ))||+%s&per-page=100&sort=release-asc
It's Alt+S+S+L.
Made a little donation bud, was already overdue imo 
Thanks for all the work 
That's very kind of you good sir. ![]()
Just to put some icing on the cake I prefer using those regex to rename "mix" fields to my liking :
regexpreplace "(?i)"mix": "Extended Mix"" ""mix": "extended""
regexpreplace "(?i)"mix": "Vocal Mix"" ""mix": "original""
regexpreplace "(?i)"mix": "Original Mix Original Mix"" ""mix": "original""
regexpreplace "(?i)"mix": "Main Mix"" ""mix": "original""
regexpreplace "(?i)"mix": "Extended Version"" ""mix": "extended""
regexpreplace "(?i)"mix": "Extended Mix Extended Mix"" ""mix": "extended""
regexpreplace "(?i)"mix": "Extended Mix Original"" ""mix": "extended""
regexpreplace "(?i)"mix": "Instrumental Mix original"" ""mix": "instrumental""
regexpreplace "(?i)"mix": "Dub Mix Original"" ""mix": "dub""
regexpreplace "(?i)"mix": "Club Mix original"" ""mix": "club mix""
and so on
didn't notice this website translates Backslashes" to "".. of course backslash" has to be read instead of ""
I don't know how that's working as when you replace " in regular expressions for WSS you need to escape it with a \.
So one of your examples would be:
regexpreplace "(?i)\"mix\": \"Extended Mix\"" "\"mix\": \"extended\""
My code is fine I'm not used to this forum and outputting raw text.
I don't know how that code is working in your scripts I meant. It should break them.
Here's the correct code for what you want:
regexpreplace "(?i)\"mix\": \"Extended Mix\"" "\"mix\": \"extended\""
regexpreplace "(?i)\"mix\": \"Vocal Mix\"" "\"mix\": \"original\""
regexpreplace "(?i)\"mix\": \"Original Mix Original Mix\"" "\"mix\": \"original\""
regexpreplace "(?i)\"mix\": \"Main Mix\"" "\"mix\": \"original\""
regexpreplace "(?i)\"mix\": \"Extended Version\"" "\"mix\": \"extended\""
regexpreplace "(?i)\"mix\": \"Extended Mix Extended Mix\"" "\"mix\": \"extended\""
regexpreplace "(?i)\"mix\": \"Extended Mix Original\"" "\"mix\": \"extended\""
regexpreplace "(?i)\"mix\": \"Instrumental Mix original\"" "\"mix\": \"instrumental\""
regexpreplace "(?i)\"mix\": \"Dub Mix Original\"" "\"mix\": \"dub\""
regexpreplace "(?i)\"mix\": \"Club Mix original\"" "\"mix\": \"club mix\""
To format code blocks in the forum use ``` at the top and bottom of the block of code.
Here's a screenshot of this reply.

it looks like they changed their release name, I 've just done 1000+ searches automatically and just realised they moved the release name in their json structure.
you have to grab it doing :
json_select_object "release"
json_select "name"
Not sure I follow. The scripts grab the name from the release array but it works fine.
Are you experiencing an issue?
stevehero, I've noticed Beatport increased the artwork quality to 1400x1400 as well.
Is there an option to pick the highest quality artwork available per release?
I'm sure that's possible, I'll take a look at this this evening. Thanks for point that out.
It already does get the 1400px artwork, IF it's available.
Here's one that has it and it works: https://www.beatport.com/release/home/3146301
outputto "COVERURL"
json_select_object "images"
json_select_object "large"
json_select "url"
json_unselect_object
json_unselect_object
sayrest
This is the existing code which will get the 1400px artwork. Beatport places the 1400px artwork in the large object. But judging by beatports json they have 1400px artwork in all the different sizes!
"images": {"dynamic": {"height": 60, "id": 26846219, "url": "https://geo-media.beatport.com/image_size/1400x1400/69205a40-a1cb-45cf-bfb4-d66597dc8ac1.jpg", "width": 60}, "large": {"height": 60, "id": 26846219, "url": "https://geo-media.beatport.com/image_size/1400x1400/69205a40-a1cb-45cf-bfb4-d66597dc8ac1.jpg", "width": 60}, "medium": {"height": 60, "id": 26846219, "url": "https://geo-media.beatport.com/image_size/1400x1400/69205a40-a1cb-45cf-bfb4-d66597dc8ac1.jpg", "width": 60}, "small": {"height": 60, "id": 26846219, "url": "https://geo-media.beatport.com/image_size/1400x1400/69205a40-a1cb-45cf-bfb4-d66597dc8ac1.jpg", "width": 60}},
Thanks for elaborating. I noticed this as well:
In the source you can see only 500x500 > https://geo-media.beatport.com/image_size/500x500/949ce322-9a70-4fde-8944-3de55636d7d8.jpg
If you edit the 500x500 to 1400x1400 it outputs a 1400x1400 jpg.
This led me to believe there was an update in the background.
However I just checked and found out that if you edit it to 3000x3000 it also outputs a 3000x3000 image
Same for 5000x5000.
Must be some upscale going on in the background.
I'll keep it as is for now 