Any better?
Note that you often don’t need to wait until UTC-12:00 because the country with the most distant timezone on Spotify is Niue, which is UTC+11:00. The warning is not displayed if the release has worldwide availability.
6 Likes
Looks great, thank you!
1 Like
Hi, I have a few quick questions for the iTunes experts which are following this thread:
- Are all releases which can be queried via the iTunes API downloadable? I know that the seeded Apple Music links are currently marked as “streaming” since the URL format has been changed from itunes.apple.com to music.apple.com, but as far as I can see that isn’t technically correct as the API responses contain an
ìsStreamablefield for each track. So I guess the correct behaviour would be to always mark the URLs from a-tisket as “purchase for download” and only mark them as “streaming” if all tracks are streamable. - That leads me to my second question: Apple Music exclusive releases, which can only be streamed but not purchased, are not returned by the “old” iTunes API, correct?
- Are all releases which can be queried via the iTunes API downloadable?
No: itunes.apple.com/lookup?id=1491472651&country=JP
- That leads me to my second question: Apple Music exclusive releases, which can only be streamed but not purchased, are not returned by the “old” iTunes API, correct?
As above, no.
The only obvious difference vs. itunes.apple.com/lookup?id=1491156777&country=JP is that the streaming-only release lacks a collectionPrice, however that could also indicate that the release date is in the future.
1 Like
Interesting, thanks for the examples. Good that I’ve asked, I vaguely remembered that Apple Music exclusive releases could not be queried from the iTunes API. Apparently I remembered that wrong, but not completely:
One thing which I noticed, is that the API only returns the “collection” / “Album” result but not the “track” results for http://itunes.apple.com/lookup?id=1491472651&country=JP&entity=song (streaming only example) which it does for downloadable releases, e.g. for your second example: itunes.apple.com/lookup?id=1491156777&country=JP&entity=song
So I guess the presence of “track” results in the response should be a good indicator for downloadable releases in addition to the price.
For this release a-tisket apparently concatenates two release versions (and keeps the wrong barcode):
https://atisket.pulsewidth.org.uk/?upc=884388874435
884388874435 should be https://music.apple.com/us/album/utopium/1672065081
Deluxe edition (884388874442):
https://music.apple.com/gb/album/utopium-deluxe-edition/1674724800
There is another one which seems not available for purchase (884388874459):
https://music.apple.com/us/album/utopium/1672063971
BTW
Sometimes a-tisket fails to find existing releases (or artists for that matter) in MB. Am I right to assume this is due to the infamous frequent search errors?
Example
https://atisket.pulsewidth.org.uk/?url=https%3A%2F%2Fopen.spotify.com%2Falbum%2F1SYwFUYTGKVixxPaEcSyQr
Other times it suggests to add artist URLs that already exist.
1 Like
Will look at the release issues when I have some time.
Could be a search error but is more likely to be due to MB API rate-limiting.
Again this could be due to search errors or rate-limiting, however if the artist URLs were only recently added then it’s likely because the search index hasn’t caught up yet.
3 Likes
Is there any chance of supporting searching on Amazon Music as well from within this tool?
I’m afraid there isn’t much chance of this at all, sorry.
1 Like
Yeah, I think this was discussed in the old thread. Amazon Music doesn’t appear to have a public-facing API.
Yes, they do have a web API where you can search and retrieve information on artists, albums and tracks etc. The API response for albums even includes an availableMarkets field.
However from what I can see the API is not publicly accessible:
The Security Profile ID(s) used by Music client applications must be enabled by the Amazon Music Service in order for authorization to be successful. Reach out to your Amazon Music point-of-contact for more information.
4 Likes
I noticed sometimes the script selects “Single” as release group type when there are 4 songs, it would make often more sense if EP was selected, or in doubt left empty.
But it also selects single when it is clearly marked as EP.
Example: تفاح - EP by Yusor Hamed | Spotify
Spotify’s API is calling it a single for some reason. I checked both the one on a-tisket (Spotify API) and the one at Web API Reference | Spotify for Developers. a-tisket shows both Apple Music & Deezer as an EP. So, that’s just a fault on Spotify’s end.
5 Likes
any plans to import playlists or whole artist ? one by one albums is way too slow
Although not Spotify, Apple classifies Japanese maxi singles as EPs. No other platform does this, and I always fix this on sight in MusicBrainz too. Which is to say, Apple appending " - EP" or " - Single" to the end of an album that has no suffix on other platforms means little to nothing.
4 Likes
You’re expected to actually check the data, and ensure that follows the style guidelines. As such, it being a bit slow is not a bad thing 
It would be a lot harder to do that for a whole discography at once.
12 Likes
i made like 3k edits in 2 years and at this speed i will be dead before i even add the songs i got on my nas
Two questions…
Can anyone confirm that COI by Coi Leray COI - Album by Coi Leray | Spotify is not returning iTunes and Deezer data? I’ve even manually inserted the IDs and it still will not return data.
Is it possible to use atisket to amend a pre-existing Musicbrainz album? The aforementioned COI is missing some data and I don’t want to erase the release completely I just want to use atisket to add what’s missing.
Thank you so much for any help given!
Just checked. All have different barcodes. Spotify has 00602455901170, Apple Music, 00602455901118 & Deezer has 602455901132. Use the script by Toad King (GitHub - ToadKing/apple-music-barcode-isrc) on the Apple Music page and it’ll give you the barcode for the Apple Music release. It’s not uncommon for Apple Music releases to show up with different barcodes. When using a-tisket, I always follow this order to avoid mistakes:
- I use Experience the App Store and iTunes Anywhere | fnd to find the Apple Music release first. When using Toad King script a small black box appears at the top left of the page. Click that and get the barcode. Always run search on a-tisket using BOTH the Apple Music URL & Barcode fields filled out. If there is a Spotify and/or Deezer release with the same barcode it will find it. Also, make sure to check the box that says “Search iTunes globally for release countries”. So many editors forget to do this and this is why you don’t see Apple Music (iTunes) in the annotations or their exclusive countries.
- After adding the Apple Music releases, if no Spotify and/or Deezer release found then I do Spotify next and make sure to check the skip avoid iTunes box at bottom, so that it doesn’t accidentally add the wrong Apple Music release.
If you follow this order, you shouldn’t have mismatches. It’s not uncommon for Spotify, Deezer & Apple Music releases to sometimes have different barcodes.
Also, other than style corrections, looks like the only thing needing changing is release event. There is a script that will add all the countries, however, adding long country lists is now discouraged. There are also scripts to change to Worldwide and change all dates, etc. But no, a-tisket by itself cannot make MB edits.
3 Likes
I’d like to point out that this script is broken. It is now changing to either United States or United Arabia, even if it shows Worldwide as soon as you click the bookmark, so I have to make sure to change from Worldwide to blank and then back to Worldwide.