Code should be wrapped when posting.
Some code
Code should be wrapped when posting.
Some code
error with regexp. how to right syntax?

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?
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.
Awesome, cannot wait to try this out!
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.
Explain how this works?
regexpreplace ".application/json">({.)</script><iframe.*" "$1"
I don't particularly care if you don't. GL.
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 ![]()
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.
tryin to dl
beatport by stevehero vTBC.0 Scripts.zip (70.1 KB)
and getting this error:
" Oops! That page doesn’t exist or is private."
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.
got it!
the new version of mp3tag i already have ![]()
I was under the impression that the newly uploaded 3.21a) included all the changes needed?
No, there's one more.
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.
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.
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? ![]()
Can you please tell me if there is a workaround now?
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.
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.