Hello! Great script, I've used it a couple times already and have some suggestions that maybe could improve the (my ) experience.
Right now mp3tagtrack is missing leading zero for all the numbers < 10. Would be great if that could be fixed:
For example 1/9 until 9/9 could be 01/09 until 09/09
I've fixed YEAR to show only the year and created RELEASETIME for the actual date of release
outputto "YEAR"
sayregexp "(?<=\"releaseDate\":\")\d\d\d\d(?=.)"
Say "|"
OutputTo "RELEASETIME"
GotoChar 1
FindLine "\"releaseDate\":\""
sayregexp "(?<=\"releaseDate\":\")\d\d\d\d-\d\d-\d\d(?=.)"
Say "|"
I also take it there's no real way to put the correct publisher in the publisher field?
Now it just copies the whole line.
Hello!
So, I was tagging my Pokemon soundtracks and I wanted max sized covers so I tried to find one of the albums on iTunes Japan and it turns out that apparently you can't search words in Kanji/Romaji or Hiragan...
All the movies' soundtracks are only available on iTunes Japan so there are no possibilities of tagging them with iTunes US or France..
I ended up using Amazon Japan and well, it worked so the non recognition of Japanese language is exclusively an iTunes problem.
Any guess on what I could or if there's a solution ?
Thank you !
The problem with the script is it uses the less consistent (slower) method of findline, findinline, SayUntil etc
When this script first came out I edited it and added a few more outputtos using sayregexp just how Pone had done it.
I've tested this and it works for both of these albums you're having difficulty with.
Regular expressions is probably the best thing I've learned in my adult computing life . So for me the sayregexp is x10 the more powerful method of writing Web Source scripts.
I've noticed in the script all your regexpreplace could be replaced with the simple replace fn.
regexpreplace "100x100bb" "100000x100000-999"
is same as
replace "100x100bb" "100000x100000-999"
regexpreplace is only used where the text string will vary and is ill-formatted therefore giving problems.
In my beatport script I've placed all the regexpreplace just below [ParserScriptIndex]=... and [ParserScriptAblum]=... becuase it outputs cleaner better formatted code to parse then and is much easier to spot problems.
The regexp for the waka waka fix is (place this at the top of your script like I have - see line 35 & 79):
I am not at all experienced in scripting and I am using Pone's script (with some modifications) a lot and noticed a problem with this and other scripts for some time now.
Filling the search-field with the websoutce-search from the tags with special characters (like German Umlaute: äöü) results in error-messages. So I had to manual change these characters during websource-search.
I tested JonaaaBR's latest itunes-script and it did not have this problem.
So I had a look at the code and spotted this difference:
Mine till now and also your script: [Encoding]=utf-8
JonaaaBR's script: [Encoding]=url-utf-8
"[Encoding]=url-utf-8" solved my problems with special characters but I am far from understanding why.
Thank you very much for this script.
Maybe there is a small bug in the french version of the script.
I think the country should be FR and not FA in :
[IndexUrl]=https://itunes.apple.com/search?country=FA&entity=album&term=%s
and
[AlbumUrl]=https://itunes.apple.com/lookup?country=FA&entity=song&limit=200&id=
The script does not work correctly in the part of fill fields "Composer" and "ComposerSort".
The data from "Artist" is written in these fields. But this is not correct. The fields should be Komposer own data, which often differ from the data in the Artist.
If there is a possibility to receive the data correctly from itunes - please, fix the script.
If this data is not possible to recieve from itunes - it is better to leave this field untouched. Otherwise can be a situation where the correct data previously placed there to be mistakenly overwritten from the field Artist.
Yeah, i'm using the Artist field on Composer... if you want to leave it untouched, just remove the COMPOSER and COMPOSERSORT lines... and, iTunes API doesn't provide any Composer information, that's why i'm using the Artist field on Composer.
However, there is one problem, MP3Tag stops listing tracks after 200? In this autotag editor.
Yeah, some might think, what the hell has more than 200 tracks?
Answer: Pokemon Super Music Soundtrack https://itunes.apple.com/us/album/pokemon-h...mon/id796790051
Is there a way to list more than 200 tracks, lets say 300 or more?
Thanks.
EDIT:
Well actually I cant since I dont see the full tags in the browser. And trying to open it in iTunes is impossible. Its not even in the store?
Did I say how much I hate this crap Apple software? Holy hell?! It did not only install iTunes. It also installed tons of idiotic side programes and services. My poor Windows...
Any way to export the tags from the browser view?
You can do it with copy&paste from the website to a text-editor.
You even can work on the test-file and import the tags from there.
I wanted to show the result but you obviously have disabled personal messages.
) experience.
!
. So for me the sayregexp is x10 the more powerful method of writing Web Source scripts.
