They probably upscale using AI to 8k and derive the rest from that.
If you change the URL from 500 to something crazy like 10000 then it'll get the very largest image possible. In my quick test 8192x8192px is the largest doing this.
I might edit the 500 to 1200 perhaps. 5k px covers is a lot. 1.2MB that one is.
What is other peoples opinion on this?
I don't embedded artwork any more so it wouldn't add much doing it that way.
For anyone wanting higher resolution artwork replace the outputto COVERURL section with this below.
Please note bp seems to only have upscaled any images that are 2021, so this code will check this and get the artwork at whatever size you want. Change 2000x2000 on the line regexpreplace "\d+00x\d+00" "2000x2000" to whatever size you need.
I checked this and I only get custom HiRes covers with 500x500 (low) quality for most of releases. Also, I noticed that 1400x1400 is max default size for BP covers, but I can't get it for all 2021 year releases. It's not clear why...
And one more thing is not clear for me...
If we click "open image in new tab" from the release/album/compilation page https://www.beatport.com/release/night-versions-ep/3266483, we will see 500x500 cover.
But, if we click the same on any cover from publisher/label page https://www.beatport.com/label/innervisions/3315, we will see BP default and nice 1400x1400 cover.
What does happen with all of that?
Edit:
Yes, I understand now... For some releases it works, for some not and covers are blurred. After all, it's not bad. Probably BP doesn't have all covers in 1400 yet, for year 2021.
Thanks for spotting this. I didn't like the fact that it was upscaling images so i didn't release a version with that. Now I know this, I've amended the scripts to get that image using:
Just stumbled across this script and I love it.
Am i being really stupid in that the Year or ReleaseTime doesn't write to the tag?
Any help would be greatly appreciated.
in the *.inc file(s) accordingly. Unlike Juno and other places, Beatport mostly releases only the extended mix and not the original + extended mixes (remember audiojelly )
Hey, really sorry to annoy you with my problem. I didn’t use MP3Tag in the last year. I started up my work a few days ago and saw that u you have a new version of your script and I did a roll over to my, a bit to fast. Ending with lost of my old modified script.
I really fucked because I don’t remember what I had changed and how to do it again. Whit your new script I don’t find the info's to change it back too I needed.
I’m using only the:
Beatport by &stevehero v5.0#TRACK Direct by BEATPORT_TRACK_I&D.src
Beatport by &stevehero v5.0#TRACK Search by Artist + Title.src
First Problem:
On the search result page, I don’t see the Track Title Tab. The result is I don’t can use the easy way to search by title and track.
Second Problem:
The Key is not written in to the tag (comment or initalkey) before it writes both infos in the tag.
Last Problem:
The track title (Original Mix) is missing completely, with my old script it changed it to (OM). But now its only the title name without (Original Mix).
Again, a big SORRY! Hope U can help me or show me where I find the Info to do it by myself. I don’t find the answer in 10 Years! Hey, really THANK YOU for creating, sharing and giving support!!!
‘’ RELEASE’’ is showing me the artist’s name, not the title of record.
‘’ REMIXER/S’’ shows only a dash… but I tied it only on a few samples.
On the missing tags… I get it to work to write the keynote into the ‘’initalkey’’ field but not to copy that in the ‘’comment’’ field.
On the missing (Original Mix) I try out enable/disable the # on multiple positions. But that seems to be not the reason, so far I understand the text in the script. There is no point it says enable here for missing (Original Mix). It is maybe possible that Beatport has change something on their website? I see that (Original Mix) is separated from title field. That can maybe also the reason for the dashed ‘’REMIXER/S’’
I continue with my trying’s. Just want give u a update of my. Have a good time
found that it was my fault with the trying to change the order of the search result page. This leads to new faulty results. Steve on your script it works fine title + (Original Mix) and writing in to the tag by adding # in front of replace ""Original Mix"" """"
I tried to find my fault but everything looks correct for me. Maybe u like to take a look over it? If not I’m cool with it and take it like it is.
I have these faults in my moded script…
‘’RELEASED’’ date is not showing, it is blanked.
‘’ RELEASE’’ is showing me the artist’s name, not the title of record. (same on your TACK search and differently to your REALEASE search)
‘’ REMIXER/S’’ shows only a dash. (on yours it works fine)
And don’t get it to work copy initalkey to the comment field.
I had tried to modify some small aspects of the script,
but I was having trouble to recreate my cosmetic needs.
I just have some small requests to modify the following:
Padding 'Track No.'
I like to see 2-digit track numbers, ie. Track 01 but not Track 1
Script only writes track numbers, without any "padding", ie. '0' at front.
4-digit year
I like to save into the tag: '2021' instead of '2021-05-04'
No catalogue / label in 'Album' field
The script already saves the record label to the "Catalog No." field,
but it also shows the record label, in the 'Album' field.
I do not want it in the 'Album' field and I am fine with how it writes to the "Catalog No." field already.
Removing extra columns from:
_Search results
I want to remove columns such as "Exclusive", "Price", "ID", etc. to make for a cleaner result page.
.
_Adjust Tag Information
I want to remove columns such as "Beatport Track ID", "Beatport Track URL"
and/or re-arrange columns, so it's easier to read 'Length' or 'Track', when viewing side-by-side
Padding is not possible. This needs a feature added by mp3tag for counting when doing a json_foreach loop.
Year only, look in the scripts for:
# regexpreplace "(released\":\s*\")(\d\d\d\d)-(\d\d)-(\d\d)" "$1$2-$4-$3" # YEAR in YYYY-DD-MM format
# regexpreplace "(released\":\s*\")(\d\d\d\d)-(\d\d)-(\d\d)" "$1$4-$3-$2" # YEAR in DD-MM-YYYY format
# regexpreplace "(released\":\s*\")(\d\d\d\d)-(\d\d)-(\d\d)" "$1$2" # YEAR in YYYY format
Change to:
# regexpreplace "(released\":\s*\")(\d\d\d\d)-(\d\d)-(\d\d)" "$1$2-$4-$3" # YEAR in YYYY-DD-MM format
# regexpreplace "(released\":\s*\")(\d\d\d\d)-(\d\d)-(\d\d)" "$1$4-$3-$2" # YEAR in DD-MM-YYYY format
regexpreplace "(released\":\s*\")(\d\d\d\d)-(\d\d)-(\d\d)" "$1$2" # YEAR in YYYY format
For no Catalog in album change:
# ALBUM [CATOLOG #]
outputto "ALBUM"
say " ["
sayoutput "CATALOG #"
say "]"
To:
# ALBUM [CATOLOG #]
# outputto "ALBUM"
# say " ["
# sayoutput "CATALOG #"
# say "]"
For removing columns, Remove these two:
|% ↓ EXCLUSIVE%|% ↓ ID (◣_◢)™%|% ↓ PRICE%
json_select "exclusive" # EXCLUSIVE
sayrest
say "|"
json_select "id" # ID
sayrest
say "|"
json_select_object "price" # PRICE
json_select "display"
sayrest
json_unselect_object
say "|"
For removing tags, use set at the bottom of the scripts so:
# set "BEATPORT_TRACK_ID"
# set "BEATPORT_TRACK_URL"
stevehero,
thank you so much for the detailed reply
the first 2 of your 'workarounds' are a success,
ie.
Year in "YYYY" format
No Catalog in Album name
However, when removing the columns from the results section,
ie. removing the 2 'sections' (which you pointed out), the entire web source scripts stop working.
Also, for 'removing tags', if I use "Set", wouldn't that omit those 2 x tags from the ID3,
ie. MP3Tag will just not write the BEATPORT_TRACK_ID and URL tags ?
All I wanted, was to remove the visibility of these columns, in the search results,
because it saves me from horizontally scrolling between first and last columns
(which contain track numbers/names and track lengths).
I don't need to see TRACK_ID and URL information , however, I do not mind if MP3Tag writes this information into the ID3 tags.
)
