plz learn to use the software/forum
I think @hjm678 just wanted to illustrate how many untagged files are still remaining that they might need to submit with atisket. Is that about right?
But are those all really albums that are not yet in MB? Maybe after attempting to tag those there are far less that actually need to be added.
2 Likes
yes u are correct, since my complaining that 1 album by another album is very slow
yep, the acoustIDs fail to find it takes about 3 hours to search and nothing
MB so far has plenty of mainstream music but if you leave that is quite missing for example Eduardo Paniagua - MusicBrainz and the edits are not quite good 
for example is missing plenty of berber music, slavic, even Moldavian if uses Cyrillic, altaic, tartar, azeri, georgian, armenian, aromanian, bulgarian, serbian, etc etc
long story short it would be faster if i could add a artist profile from itunes and every album single ep get imported or even if it open in a new tab it reduces the copy paste quite allot
Searched for an itunes JP release but it finds the not-JP name for the release and combines it with the JP track name: Vulgar by 鬱P & Ci flower | a‐tisket: A multi‐source seeder for MusicBrainz
The problem is that the iTunes API returns the non-Japanese name for the release title (collectionName property of the first result with a "wrapperType": "collection" property).
I don’t know whether this result depends on the region or the request headers of the requester, i.e. whether it only does this for requests from outside of Japan.
Strangely enough it does return the Japanese release title for the track item, usually the tracks collectionName property has the same value as the release item:
$ curl -s 'https://itunes.apple.com/jp/lookup?id=1698252930&entity=song' | jq '{release: .results[0].collectionName, track: .results[1].collectionName}'
{
"release": "Vulgar - Single",
"track": "下品 - Single"
}
I’m not sure whether that’s a sign that we should prefer the value from the track(s), this would need further testing.
3 Likes
I am not sure if this has been mentioned here before (search didn’t yield anything relevant) but digital release dates before 2001 should be rejected right at the tool level. None of the services that atisket supports came even existed before 2001 and these instances of “Digital releases from the analogue era” are pretty much flooding the database with low quality data because lots of users are essentially running in autopilot.
4 Likes
I think this has been mentioned a few times here on the forums…
I don’t think it should block submissions of 200X releases, but perhaps it should blank (or at the very least suggest blanking) the release date field for these releases (I think this has been the general consensus)
7 Likes
Yeah, this is what I actually implied but my wording wasn’t clear enough.
Have a quick check at history on Wikipedia and you’ll see Spotify, Deezer, etc are all long after 2001. There are also the contract arguments that kept artists like Radiohead, The Beatles, etc away from digital release for a lot longer than that.
It is a long old debate in this and other threads. Frustrating that users don’t understand the damage they are doing. They just blindly believe the data they are fed without even making a basic sanity check.
5 Likes
The following countries have name changes in MB that could be reflected in the annotations here as well. Czech Republic is now Czechia, Swaziland is now Eswatini & Turkey is now Türkiye.
1 Like
I’m realising just now that my point below was posted only in the other thread, so I will bring it up here too as I still run into this issue regularly.
Having English as default option in a-tisket’s language field leads certain users to not bother selecting the correct language using the release editor before submitting a release. This is an area where this (otherwise excellent) tool leads to lower data quality. I would just remove the field altogether and let users manually set the language using the release editor, or leave the field blank if in doubt.
6 Likes
between this and the Bandcamp importer doing similarly, even I often forget to set the language and script fields… I’ll second this change wholeheartedly~
4 Likes
My preference would be to move it to somewhere more prominent, like where the tracklist is. It’s something I rarely need to change, but I always forget to because it’s hiding at the bottom of the page and gets overlooked.
1 Like
Hello
Thank you for hosting this website.
I have found the tool incredibly useful and would like to contribute some code to add new features as well improve QoL for the existing ones. Is the source available on github or some other place?
Fixed.
The default setting of English has been removed, but the drop down left in place. I added Korean as a list option as quite a few people seem to be using a-tisket to import K-pop releases.
I appreciate some people won’t like this change as it means 1 more click - I may consider adding a preference to set the default language in future but it will intentionally require some sort of manual action to set (e.g. copying code into the developer tools console).
I also converted the script option to a drop down list but left Latin as the default.
I’ve moved the language and script options to directly below the tracklist so they are much more prominent.
A few other general changes have been made:
- Dropped the excessive amounts of vertical whitespace above headers and sections. This reduces the amount of scrolling needed without impacting readability.
- Fixed a bug where the wrong Apple Music release was selected and an incorrect number of tracks was listed. This was due to the iTunes API returning multiple releases for a UPC search. Here is an example of a release that triggered the issue - note the single release in the “Other Versions” section under the tracklist.
11 Likes
The use of Serif fonts on the site has always grated a bit for me. I’d like to switch all the fonts to Sans Serif and increase the size very slightly to improve readability, see the screenshots below:
However this change is obviously very subjective so I thought I’d run a little poll to see if there is any consensus:
- Change the font to Sans Serif
- Leave the fonts as they are
0
voters
5 Likes
To my surprise the poll was unanimous so I’ve just made the change. You may need to clear your cache for the updated CSS to load. Hopefully everyone finds the site a bit easier to read now.
7 Likes
Small regression. It’s no longer possible to deselect Latin.
2 Likes
Thanks, I’ve added an empty option to the script dropdown.
2 Likes
I wasn’t sure if this would warrant a new topic or not, but has anyone else encountered Spotify having seemingly identical but separate releases for India and everywhere else?
To give an example of what I mean, I added https://musicbrainz.org/release/c477420d-9931-4ecf-b0c3-5d58762c6121 (Spotify link) today. It’s the same label and barcode as https://musicbrainz.org/release/425e1c90-9530-43b5-8624-65c3a4e84ab7 (Spotify), but they have different Spotify IDs. The former is only available in India and the latter is available everywhere else. https://www.deezer.com/album/445802055 has the same label and barcode, but https://api.deezer.com/track/2298903865 lists India as an available country. Meanwhile, ÁTTA - Album by Sigur Rós - Apple Music has a different barcode, but it’s the same Apple Music ID in India.
The label in question is BMG Rights Management (UK) Limited. Note that https://musicbrainz.org/release/e10d12be-a02c-4abf-9fa3-2087b693919a, https://musicbrainz.org/release/127e1027-ffce-4e7c-b918-4b89c9424ee6, Release “I Wish I Could Hate You” by HRVY - MusicBrainz and https://musicbrainz.org/release/48973cdf-51e8-4de7-8c22-fd2c2b4ffa34 don’t appear to be available in India either.
So is this a Spotify quirk? A label quirk? Both? And do they warrant separate MB releases or should they be merged?
1 Like