I've been trying to extract the country code from the Apple Music script without luck. It looks like the only place it is available is in the storefronts data, which I am having issues accessing. Would you be able to suggest where in the script and how I might be able to pull and write the two letter country code?
Apple is not alone with throwing things together. Often sources use "Written by" for both. It would be not such a problem if there was an official tagfield named "Author" or Writer", where you could name both but naming both of them "composer" is irritating.
I am not so familiar with the apple-world. Is there a website where you see all those informations you get in your apple-script?
You script lists a tagfiled AMLYRICS and gets informations of 0 or 1. As I understand that could stand for "Apple Music Lyrics", right?
Are you able to get these lyrics in cases the field shows 1?
Apple Music has its history from MP3 world and the SoundJam app, as well as requiring the AMG database, which all only uses "composer" only. This was all in iTunes days, but they don't seem to have expanded it further. I guess it is because there is little value for them in return, and having one field only makes the apps more coherent. Now it seem like the record labels update the data themselves, directly in Apple Music. While Apple have relatively strict guidelines for metadata, many labels do not (especially minor ones) follow them.
AMLYRICS is just if Apple have lyrics or not, I was looking for a way to get it, but I don't know of any way. I should probably remove the tag from future scripts, as I don't think it is necessary for anyone.
Mp3Tag has just been updated to support a bunch of m4a fields such as the Album ID via ITUNESALBUMID. Can you please update your source to support it? Ik it’s probably so easy and I could just tweak it myself but I have no knowledge about that
The ITUNESCOUNTRYID is supposed to be the storefront ID, not the two-digit country code. Also, there is a funny x at line 249 of Apple Music Web.inc.
Please also remove the debug output from the official scripts — it has performance implications and also might Mp3tag seem suspicious, trying to create random files in the root folder of the system drive.
Yes I already figured out that it should be the storefront id, I think I will drop saving that field altogether as it is not really that useful. You already choose which storefront by which country store to collect the information from anyway. Another option will be to convert the country code to the respective storefront id.
The "x" is deliberate, although I should have removed it (actually the entire surrounding code) as well as the debug output, which I always keep forgetting to remove, before publishing. Sorry about that. I store the debug on the root because I run MP3tag on my M1 Mac via crossover and it is too tedious to keep it buried deeply.
I was originally hesitant to update the script until the 3.06b version of MP3Tag was not a beta version, but because it was requested I rushed out a new version yesterday. If the script is run on a pre beta version they will not be stored as expected. Which brings me another curious question to what happens if you open those tags again after saved in 3.06a and earlier and save again in v 3.06b?