I signed up specifically to Thank stevehero for this excellent script/project..
And his Amazing support over the past 21 pages of this thread.
As you can imagine 3TB+ of music tags to clean up and rearrange which has been keeping me very busy.
On another note:
Mp3tag.exe /fp:"<full-qualified path to directory>"
Starts Mp3tag in the specified directory using the directory as working directory.
Could this be a method to employ a master script to work around/manipulate the tags. So, in a way: To parse the already parsed data.. Kind of like the "Tools" / "Utils" menus in MP3Tag SW itself.
OR
An external .bat to automate the MP3Tag SW and stevehero BP script to search multiple files from multiple releases. (As per the guy with 200 releases a few posts back, musicbrainz was mentioned.)
I understand the power of MP3Tag syntax is limited yet powerful enough to do amazing tasks I just see the CLI as a possible gateway to expand on any limitations which one may experience and as a path for future expansion of this project/script. Maybe this is not the right place for this kind of suggestion. idk..
Please keep up the great work, This script is a massive time saver.. Thanks once again!!.
FYI: Beatport is timing me out now and again I think its some geo-proxying technique employed.. only on a few releases I get this issue with. Specifically the Material records label. its there on BP but when I use the script it doesn't like it.
You're probably both using v2.73b or v2.73c. With this release Mp3tag uses a completely different HTTP/HTTPS implementation which also has a more strict URI parser.
I've noticed that the URL which is used in the scripts doesn't fully conform to the specification (as stated in RFC 3986), which -- in this case -- means that square brackets are not URL encoded.
Can you please try the following two steps:
In the [IndexUrl] value, replace the square brackets in the URL by their URL-encoded equivalent, i.e., %5B%5D
Just uploading the scripts now. Sorry it took a while, I moved country and had my computer shipped which took a week.
Working scripts in starting post.
Thanks Florian for the fix and kind words, same to you. I don't think I could of found the problem myself.
I did notice that even with your fix, I needed to do this:
[IndexUrl]=http://classic.beatport.com/search?&perPage=50&facets%5B%5D=fieldType:release&query=%s # Place &sortBy=publishDate+DESC at the end of %s if you want releases sorted by date.
to (put the commented line to a new line):
[IndexUrl]=http://classic.beatport.com/search?&perPage=50&facets%5B%5D=fieldType:release&query=%s
NEW LINE
# Place &sortBy=publishDate+DESC at the end of %s if you want releases sorted by date.
Seems mp3tag has parsed that line even though it was commented out.
PS, any way to keep a counter on the scripts downloaded for total amount downloaded over the scripts lifetime. I never like it when it goes back to zero?
Hi everybody,
fist of all I apologize for my english because it isn't as good as it should be.
Thank you stevehero for your amazing job, your script helped me to save a lot of time!
I have a little problem with the latest version, I'm not able to get the musical key anymore. Can anybody help me to get it back please?
The principal proceedings are described in this thread: /t/16471/1
If you ever want to sort by the date, you should leave it as it is. Because otherwise you get all tracks from the first of each month first, then the ones from the second and so on. Sorting by year, then by month and then by day does not work in the format DD-MM-YYYY.
Hello, I'm new to this forum. First off thank you for allowing me to post my comments. Big thanks to stevehero for his amazing job. Regarding this I want to mention that I also encountered this problem with the musical key in the latest version of the scripts. Problem is I can not go back to the previous version. I accidently deleted it and can't recover it. Any chance of getting the previous version or maybe solving the issue with the musical keys, I'll appreciate it! Sorry if that's already fixed or if there is a way to fix it!
I am getting following error with the beatport script. I am pretty sure the error is on my side, but I cannot figure it out. I get this with every release.
Can someone please help me?