# \[WS\] iTunes

**URL:** https://community.mp3tag.de/t/ws-itunes/13478
**Category:** Web Sources Scripts
**Created:** [May 24, 2012, 10:05am UTC](https://community.mp3tag.de/t/ws-itunes/13478 "2012-05-24T10:05:22Z")
**Posts on this page:** 20
**Page:** 12

<div class="post-metadata">

### Author: ![thesuperintendent](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/t/4da419/32.png) [@thesuperintendent](https://community.mp3tag.de/u/thesuperintendent)
#### Post date: [July 18, 2016, 2:23pm UTC](https://community.mp3tag.de/t/ws-itunes/13478/225 "2016-07-18T14:23:44Z")

</div>

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. 🙂

Thanks!

---

<div class="post-metadata">

### Author: ![Thibziboy](https://community.mp3tag.de/user_avatar/community.mp3tag.de/thibziboy/32/6760_2.png) [@Thibziboy](https://community.mp3tag.de/u/Thibziboy)
#### Post date: [August 7, 2016, 6:45am UTC](https://community.mp3tag.de/t/ws-itunes/13478/226 "2016-08-07T06:45:06Z")

</div>

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 🙂 !

 ![](https://community.mp3tag.de/uploads/default/original/2X/5/53dc04fa51f438a4460ae27087a431ba68f36f3a.jpg)

---

<div class="post-metadata">

### Author: ![jonaaa](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jonaaa/32/457_2.png) [@jonaaa](https://community.mp3tag.de/u/jonaaa)
#### Post date: [August 11, 2016, 10:48pm UTC](https://community.mp3tag.de/t/ws-itunes/13478/227 "2016-08-11T22:48:04Z")

</div>

> [@Thibziboy](#):
>
> 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 🙂 !

Maybe change the encoding to url-utf-8?

---

<div class="post-metadata">

### Author: ![jonaaa](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jonaaa/32/457_2.png) [@jonaaa](https://community.mp3tag.de/u/jonaaa)
#### Post date: [September 17, 2016, 9:15am UTC](https://community.mp3tag.de/t/ws-itunes/13478/228 "2016-09-17T09:15:38Z")

</div>

Just added more countries (88 on total), recently i've checked the iTunes API, there's nothing new or any changes...

[iTunes\_Update\_36.zip](https://community.mp3tag.de/uploads/default/original/2X/a/a83a2ebedc10c18b6cfab140dd9932c6e260bc99.zip) (146 KB)

---

<div class="post-metadata">

### Author: ![jonaaa](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jonaaa/32/457_2.png) [@jonaaa](https://community.mp3tag.de/u/jonaaa)
#### Post date: [September 29, 2016, 1:12am UTC](https://community.mp3tag.de/t/ws-itunes/13478/229 "2016-09-29T01:12:37Z")

</div>

Found some issues:

1- Problem with {}, some albums like "Waka Waka" from Shakira have {} on album name, SO, the script fails to "catch" the rest of the tags...

2- Problem with "Kids" album from "OneRepublic", i don't know why but the script fails to catch the rest of the tags too...

So, any helpers are welcome! 🙂

btw, here's the iTunes API Results:

OneRepublic - Kids: [https://paste2.org/tKkf05CW](https://paste2.org/tKkf05CW)

Shakira - Waka Waka: [https://paste2.org/cPyWmhAP](https://paste2.org/cPyWmhAP)

---

<div class="post-metadata">

### Author: ![jonaaa](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jonaaa/32/457_2.png) [@jonaaa](https://community.mp3tag.de/u/jonaaa)
#### Post date: [October 6, 2016, 2:00am UTC](https://community.mp3tag.de/t/ws-itunes/13478/230 "2016-10-06T02:00:49Z")

</div>

Hello! Well, here i am again updating the script...

the problem with "{}" on Album Names is properly fixed (for now), i still need some feedback if the script is working properly or not...

Yaaay! 😛

[iTunes\_Update\_39.zip](https://community.mp3tag.de/uploads/default/original/2X/6/64d6a7a8a0a93ea6b658c2f64a26fc8361d563db.zip) (146 KB)

---

<div class="post-metadata">

### Author: ![stevehero](https://community.mp3tag.de/user_avatar/community.mp3tag.de/stevehero/32/337_2.png) [@stevehero](https://community.mp3tag.de/u/stevehero)
#### Post date: [October 7, 2016, 10:03am UTC](https://community.mp3tag.de/t/ws-itunes/13478/231 "2016-10-07T10:03:30Z")

</div>

> [@JonaaaBR](#):
>
> Hello! Well, here i am again updating the script...
> 
> the problem with "{}" on Album Names is properly fixed (for now), i still need some feedback if the script is working properly or not...
> 
> Known Issues:
> 
> The Album "Kids" from OneRepublic simply don't work on the script, the API structure is strange on this album... still looking for a workaround 😛

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):

```
regexpreplace "(\"\:\s*\".*?)\{(.*?)}(.*?\")" "$1($2)$3"

```

It may seem complicated but it's not once you get the basics of regexp.

Your script doesn't output the tracks to the TRACK field. My mod script attached does this. See very bottom of code and see if that might help.

I know Pone has been absent of late but it's guys like you JonaaaBR, Pone etc that make this forum great by keeping these scripts alive.

**PS. You're more then welcome to use the code / rip it apart and learn from it.**

[iTunes\_GB\_\_stevehero\_Edit\_.src](https://community.mp3tag.de/uploads/default/original/2X/f/fec1d947fdd5ed740107b8cba55e5c973507f49e.src) (9.28 KB)

---

<div class="post-metadata">

### Author: ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [October 7, 2016, 10:50am UTC](https://community.mp3tag.de/t/ws-itunes/13478/232 "2016-10-07T10:50:20Z")

</div>

> [@stevehero](#):
>
> **PS. You're more then welcome to use the code / rip it apart and learn from it.**

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. 😉

---

<div class="post-metadata">

### Author: ![jonaaa](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jonaaa/32/457_2.png) [@jonaaa](https://community.mp3tag.de/u/jonaaa)
#### Post date: [October 7, 2016, 11:10am UTC](https://community.mp3tag.de/t/ws-itunes/13478/233 "2016-10-07T11:10:47Z")

</div>

> [@stevehero](#):
>
> 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):
> 
> ```
> regexpreplace "(\"\:\s*\".*?)\{(.*?)}(.*?\")" "$1($2)$3"
> 
> ```
> 
> It may seem complicated but it's not once you get the basics of regexp.
> 
> Your script doesn't output the tracks to the TRACK field. My mod script attached does this. See very bottom of code and see if that might help.
> 
> I know Pone has been absent of late but it's guys like you JonaaaBR, Pone etc that make this forum great by keeping these scripts alive.
> 
> **PS. You're more then welcome to use the code / rip it apart and learn from it.**

Many thanks for you feedback friend, will help me a lot, gonna check here 😉

---

<div class="post-metadata">

### Author: ![jonaaa](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jonaaa/32/457_2.png) [@jonaaa](https://community.mp3tag.de/u/jonaaa)
#### Post date: [October 8, 2016, 2:45pm UTC](https://community.mp3tag.de/t/ws-itunes/13478/234 "2016-10-08T14:45:06Z")

</div>

Okay, this time i think that the script is almost 100% bug-free...

i removed A LOT OF USELESS TAGS like COLLECTIONPRICE, TRACKPRICE and blah blah blah (totally useless...)

Just to remember...

😛

I'm still working on the script, so, i'm not done with it **YET.**

[iTunes\_New\_Release.zip](https://community.mp3tag.de/uploads/default/original/2X/7/75ac418d3335f80caa2fe099a9cac9f8542b5f27.zip) (142 KB)

---

<div class="post-metadata">

### Author: ![betty](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/b/0ea827/32.png) [@betty](https://community.mp3tag.de/u/betty)
#### Post date: [October 8, 2016, 4:30pm UTC](https://community.mp3tag.de/t/ws-itunes/13478/235 "2016-10-08T16:30:39Z")

</div>

Hello,

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=

Best regards.

---

<div class="post-metadata">

### Author: ![jonaaa](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jonaaa/32/457_2.png) [@jonaaa](https://community.mp3tag.de/u/jonaaa)
#### Post date: [October 8, 2016, 4:57pm UTC](https://community.mp3tag.de/t/ws-itunes/13478/236 "2016-10-08T16:57:12Z")

</div>

Oh, my bad. fixed it.

[iTunes\_Stable\_Release.zip](https://community.mp3tag.de/uploads/default/original/2X/4/4e330ce3f009010d4efc67d9427f6fb21dd36563.zip) (133 KB)

---

<div class="post-metadata">

### Author: ![michelp](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/54ee81/32.png) [@michelp](https://community.mp3tag.de/u/michelp)
#### Post date: [November 3, 2016, 3:13am UTC](https://community.mp3tag.de/t/ws-itunes/13478/237 "2016-11-03T03:13:39Z")

</div>

Good day,

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.

Thanks a lot!

Michael

 ![](https://community.mp3tag.de/uploads/default/original/2X/0/02298914dd54e8d30c4225b4ead0a106974a0b76.png)  
 ![](https://community.mp3tag.de/uploads/default/original/2X/7/7cde9952e34e8fee53cb22a5f08478360b224fa9.png)  

 ![](https://community.mp3tag.de/uploads/default/original/2X/0/02298914dd54e8d30c4225b4ead0a106974a0b76.png)  

 ![](https://community.mp3tag.de/uploads/default/original/2X/7/7cde9952e34e8fee53cb22a5f08478360b224fa9.png)

---

<div class="post-metadata">

### Author: ![jonaaa](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jonaaa/32/457_2.png) [@jonaaa](https://community.mp3tag.de/u/jonaaa)
#### Post date: [November 4, 2016, 3:53am UTC](https://community.mp3tag.de/t/ws-itunes/13478/238 "2016-11-04T03:53:24Z")

</div>

> [@Michael P](#):
>
> Good day,
> 
> 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.
> 
> Thanks a lot!
> 
> Michael
> 
> ![](https://community.mp3tag.de/uploads/default/original/2X/0/02298914dd54e8d30c4225b4ead0a106974a0b76.png)  
> ![](https://community.mp3tag.de/uploads/default/original/2X/7/7cde9952e34e8fee53cb22a5f08478360b224fa9.png)

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.

---

<div class="post-metadata">

### Author: ![marcoxD95](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/ecc23a/32.png) [@marcoxD95](https://community.mp3tag.de/u/marcoxD95)
#### Post date: [November 19, 2016, 12:03pm UTC](https://community.mp3tag.de/t/ws-itunes/13478/239 "2016-11-19T12:03:02Z")

</div>

Hello.

Thanks a lot for this. Works amazingly good!

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](https://itunes.apple.com/us/album/pokemon-heartgold-pokemon/id796790051)

Is there a way to list more than 200 tracks, lets say 300 or more?  
Thanks.

---

<div class="post-metadata">

### Author: ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [November 19, 2016, 12:24pm UTC](https://community.mp3tag.de/t/ws-itunes/13478/240 "2016-11-19T12:24:29Z")

</div>

> [@marcoxD95](#):
>
> Is there a way to list more than 200 tracks, lets say 300 or more?

No. 200 is the maximum that the iTunes-api allows.

---

<div class="post-metadata">

### Author: ![marcoxD95](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/ecc23a/32.png) [@marcoxD95](https://community.mp3tag.de/u/marcoxD95)
#### Post date: [November 19, 2016, 12:33pm UTC](https://community.mp3tag.de/t/ws-itunes/13478/241 "2016-11-19T12:33:14Z")

</div>

Damn. Guess I have to tag it by hand then...

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?

---

<div class="post-metadata">

### Author: ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [November 19, 2016, 3:42pm UTC](https://community.mp3tag.de/t/ws-itunes/13478/242 "2016-11-19T15:42:55Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![jonaaa](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jonaaa/32/457_2.png) [@jonaaa](https://community.mp3tag.de/u/jonaaa)
#### Post date: [November 20, 2016, 12:06pm UTC](https://community.mp3tag.de/t/ws-itunes/13478/243 "2016-11-20T12:06:43Z")

</div>

> [@poster](#):
>
> No. 200 is the maximum that the iTunes-api allows.

To be honest, iTunes API sucks. 😛

---

<div class="post-metadata">

### Author: ![stevvs](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/s/3e96dc/32.png) [@stevvs](https://community.mp3tag.de/u/stevvs)
#### Post date: [November 24, 2016, 12:37pm UTC](https://community.mp3tag.de/t/ws-itunes/13478/244 "2016-11-24T12:37:04Z")

</div>

Hello, I would like to know how will be able I to have the real composer of the music I tag with the software.

Because when I publish with script “iTunes” I have the name of the artist has the place of the composer.

Thank you in advance

[Previous page](https://community.mp3tag.de/t/ws-itunes/13478.md?page=11)

[Next page](https://community.mp3tag.de/t/ws-itunes/13478.md?page=13)
