I checked everything and corrected the errors found. Now everything works. Thanks a lot.
2 Likes
Hi,
I'm very happy with the new version, one thing is not working when I'm not wrong and that's v6.0 can't find promos in Beatport anymore. As a DJ I receive promos that are unreleased but they are already visible as pre-order in Beatport.
For example
https://www.beatport.com/artist/nicolas-soria/845710/tracks?page=1&preorders=true
https://www.beatport.com/release/forja/4197174
https://www.beatport.com/release/voragine/4188811
Are not found when pressing CRTL + i (track search by title) These tracks will be found once they are released at Beatport and available as a regular order.
I wonder what has changed that pre-order tracks can't be found anymore. Many thanks in advance for fixing this.
If Beatport cant find what you're looking for, neither can the scripts. Sorry, email them and raise a ticket with support. My scripts can't fix this.
https://www.beatport.com/search/tracks?q=Airport+Delirium+Remix&order_by=-release_date
Edit:
Even with the &preorders=true switch in the URL, nothing comes up. So 100% a beatport issue with their search.
https://www.beatport.com/search?q=Voragine%20Bruno%20Andrada&preorders=true
Yes, you are right, very stupid of me I didn't look at it the way you just did. I emailed Beatport about the problem. Once they fixed it, we might all profit from this and even be more happy with your beautiful scripts 
1 Like
I don't think there's any point in adding searching by ISRC. I could see the benefit of doing it if there was a direct URL I could parse but you have to search which I can't see the benefit in.
I could get it direct with this URL but it's missing a lot of info in the JSON.
This okay?
User option will be this:
# INITIALKEY CAMELOT KEY OR MUSICAL KEY OPTION (Leave Set for Camelot or not for Musical key)
# Set "OPTION:INITIALKEY_CAMELOT_KEY_OR_MUSICAL_KEY" "Add # at the start of this line to write the Musical Key"
1 Like
UPDATE HISTORY
v6.001 2023.07.23
- ADDED: Option to get the Musical key of the tracks along with the Camelot key. New user option
OPTION:INITIALKEY_CAMELOT_KEY_OR_MUSICAL_KEY' inside .inc scripts. - CHG: Deleted "Beatport by &stevehero v6#RELEASE Search by (Album)Artist + Release (150 Results).src" as
&per_page=150switch is no longer working plus searches are much faster so no need really for them. - CHG: Deleted "Beatport by &stevehero v6#RELEASE Search by Release (150 Results).src" as
&per_page=150switch is no longer working plus searches are much faster so no need really for them. - CHG: Renamed the date-sorted RELEASE search scripts or greater clarity. Please note this seems to be broken ATM. Could be an Mp3tag, Beatport issue or mine
! - CHG: Spring cleaned the search by ID scripts to not show the full URL in the Search by input box.
- FIX: With the TRACK scripts, the release name of the album wasn't the true name of the release.
It appears there's no method for sorting by date for releases.
Going to delete the ones in the starting post and reupload them with the same version number as they're just taking up space. You can always click the RELEASED header in the search results dialog to sort them so no biggie.
4 Likes
Hi! i know that this is not the right topic, but when the new 3.21b was release the Traxsource web tag script doesnt works anymore..so i try with my backup version 3.21 and they work..but beatport new script as you know doesnt work..so, can you try to fix this problem please? thanks in advance and sorry for my english.
Not sure about traxsource ones as I don't maintain them. But these Beatport ones work perfectly fine. Download the zip in starting post. They've been updated this week.
Sorry, I'm new in the forum and i confused you with @Florian ..anyway..your beatport script works perfectly with the new 3.21b mp3tag..in the last replay i mean that traxsource script doesnt work anymore whit the 3.21b version but works with 3.21. on the other side beatport new script doesnt work anymore with the 3.21 but works with the new 3.21b..so if i need both Traxsource and Beatport with the 3.21b only Beatport scripts works and i ask for a fix in the future mp3tag 3.21xx version so everything can work. I hope I explained well this time
1 Like
Best thing to do is create a new thread in the bugs section of the forum and explain the issue. There's been functions where extra parameters have been added so it could be that. Reference this reply when reporting. 
Yeah! So much thank you!
1 Like
The search still seems to be a bit off. I can't determine if it is a script issue or a Beatport issue. My primary search method is with the "RELEASE Search by (Album)Artist + &Release" script. Frequently, the initial search with BOTH parameters gives NO results. (e.g. Release:Once, Artist: Alex Stealthy). A search for those two terms does not show the release in the list of candidates. A subsequent search with JUST Artist:Alex Stealthy, shows the "Once" release as the TOP candidate. A manual search on the Beatport website with BOTH parameters:
https://www.beatport.com/search/releases?q=artist%3Aalex+stealthy+release%3Aonc
also shows the correct release as the top candidate. This occurs quite often. Interestingly, if I reverse Artist and Release in the search query box, I see the correct release as the TOP candidate again. Are the artist/release fields inadvertently reversed in the script?
A separate, but possibly related problem: sometimes the search yields a 404 error, but when selecting the Retry option, it presents a release results page with no data in it. e.g. ARTIST:einmusik Album:Arrival gives a "404: Not Found" error. Selecting Retry gives an empty release dialogue. The release DOES exist though:
I'm using the same script only and cannot report of any problems, it's just working fast and flawlessly.
Are you saying that the exact example I gave, which repeatably fails on my install, actually works on yours?
When you tested with "Alex Stealthy" as artist and "Once" as release, what results did you get?
When you retested with JUST "Alex Stealthy" as artist and with the release blank, what results did you get?
Enter the your examples into Beatport search on the site. I think you'll find you get the same results as the scripts. I've noticed that 404 thing myself.
That's the thing that had me puzzled Steve, when I do that on the site, the correct track shows up as the top candidate, but the script doesn't have it anywhere in the candidate list. e.g. alex stealthy once :: Beatport
I'll check this out once I'm at the PC. It may not be until tomorrow.
I get a list with 150 entries and the correct release on top in both cases.
2 Likes
Now that's interesting. I wonder what could be different about the behavior of our two installs? Thanks for confirming that!
I'm using Script V6.001 with MP3TAG v3.21f (64-bit)
Have you modified the scripts in any way? Thanks for checking @P.unkt