NVM, seems to be working again.
1 Like
Hi, everyone. I have just uploaded some updates for the tool:
- It now queries individual tracks for Deezer. It assumes that only the countries where all the tracks are available are the ones where the album was released. This may not be very accurate, so let me know if you think this is adequate or not.
- It removes “(feat. …)” from tracks titles and add them to the artist credits with the separators indicated in the parentheses. The separators (besides “feat.”, “ft.”, and “featuring” are “, ” and “ & ”); this may be problematic if a featured artist includes “ & ” in its name.
It also means that artists appearing in the credits but not in the title (e.g. remixers) will not be considered. - It is possible to use a url as parameter (e.g. https://etc.marlonob.info/atisket/?url=https://open.spotify.com/album/0KZsf82vQ6Yo59fgVjsF3Q). Useful for bookmarklets or to easily create a link to the tool without actually visiting it.
I hope that this changes don’t introduce new bugs, but if they do, please let me know (sorry my response time is not adequate, I haven’t had much free time lately).
This should only happen if there is (at least) one country that 1) is not available in any of the services 2) At least one of the services is licensed in. If you want to set it to [worldwide], it generally exists an option to “Set only to XX”, you may use that and then change XX to XW in the MB creation page. If I misunderstood, then please provide a url and a description of the expected behavior.
6 Likes
Wow. Great work. Still must pay attention, but not any more so than the iTunes importer as far as track listing, i.e. some ETI omitted if after (feat. artist), etc. I have no idea how you do this, but I can’t express how much time this will save.
1 Like
Thank you marlonob for the Deezer update.
Here’s an example of limited release reported as [XW]: https://etc.marlonob.info/atisket/?cached=190295389284-d_118623542
208 is correct. But US isn’t one of the licensed territories for this release.
view-source:https://web.archive.org/web/20200109125646/https://www.deezer.com/us/album/118623542
<meta property="og:restrictions:country:disallowed" content="AN">
<meta property="og:restrictions:country:disallowed" content="CU">
<meta property="og:restrictions:country:disallowed" content="IR">
<meta property="og:restrictions:country:disallowed" content="KP">
<meta property="og:restrictions:country:disallowed" content="UM">
<meta property="og:restrictions:country:disallowed" content="US">
track level exception list: AD AN AW AX BL BM BS BZ CU DO FO GF GG GI GL GP GY HT IM IR JE KP LI MC MF MO MQ NC PF PM PR RE SH SM SR TF TT UM US VA WF YT
I think you compared total number of territories with a fixed number of Spotify in the code.
Thanks again for your excellent tool. It saves us years. I can help if needed.
2 Likes
So the internal server error thing happened to me again today. I kept trying the same link over and over again over the course of four hours and kept getting the same error message.
I posted in the topic for the Spotify ISRC script about this, but I wanted to mention it here because I’m beginning to suspect something in this seeder is causing these errors (e.g. pythonanywhere is selectively blocking certain requests).
What a good idea!
I was considering embarking on a small project for very similar reasons.
Fixed. Thank you.
That’s one of the changes, the featured artists for tracks 6 and 8 only get registered because the iTunes release has them in the track title. I’ve got to figure out a better way to do this.
Thanks, fixed.
I think it’s fixed now. Also it seems that my list of Deezer available territories is incomplete.
Edit: It now uses the list in https://developers.deezer.com/guidelines/countries
The link provided by atisket is generic, I don’t think pythonanywhere knows its coming from this script, but from the IP address of your connection. You may try copying the link and paste it in a new tab, or do it manually using this schema for the url: https://tatsumo.pythonanywhere.com/album/[Spotify album ID] without the brackets, and then paste the MB release ID in the box at the bottom.
5 Likes
Thanks @marlonob!
Just see another bug, video tracks aren’t detected like for this example where a-tisket give 17 instead of 19 tracks (2 bonus video):
1 Like
Durations over 1 hour aren’t being displayed properly.
See first track of https://etc.marlonob.info/atisket/?cached=8718857793595-s_4IjDYedM3v0ZTsNs25DEeM and last track of https://etc.marlonob.info/atisket/?cached=5054281460119-s_7i9Q8jw0lHFtCEZiiftqHR-d_9307228-i_948321525
They are being seeded correctly thankfully.
2 Likes
Marlonob, I sent you an email last week regarding a way to improve the iTunes UPC lookup. Please let me know if you got it.
See more information in this forum topic here: iTunes UPC Database
2 Likes
Yeah, it appears Deezer is actually available in more countries than they even list on the link I provided earlier. If you right click and view source on the deezer releases website, it will tell you where it’s NOT available. I just check there and then selected Worldwide only if there’s no countries that it’s not available, (with exception of AN, which shows on almost all releases as not available, which is no longer a country, even though rarely it does show up as an available country itself). Now that they figured out how to collapse the country lists (yeah!) there’s no reason not to just add all the countries unless it truly isn’t excluded in any countries.
One more issue with track artist seeding.
This release has two release artists.
That is seeded correctly. But the track artists are both of them joined as one artist:
<input type="hidden" name="mediums.0.track.0.artist_credit.names.0.name" value="Balkonien Gang & Berky">
1 Like
I have a question regarding spotify artist uniqueness. This is important coz this tool uses spotify artist link for artist identification, so u dont need to enter them manually. It seems the spotify just combine artists with the same name under one “roof”. Here are some examples i encountered:
Some “old” artist combined with production music composer, which is probably couldnt be right
Again production music composer combined with John Stafford Smith, who is author of the USA national hymn, which ofc incorrect.
I suppose there are many more examples of this. I think there was a discussion about this in the spotify community, but the issue still remains so far:
3 Likes
You never actually state a question though… 
But yes, Spotify has an issue where multiple artists with the same name will get the same Spotify ID (e.g., spotify:artist:5KEjVMaEdZ1tHgaAIkZCVp). Spotify is a lot better than Deezer though (same artist as Spotify ID, but Deezer URL) and will sometimes have proper unique IDs even for artist that have the same name. E.g., there are multiple “Yasmin” artists on Spotify, even if some individual ones of them are actually multiple "Yasmin"s conflated.
Well, yeah, the question then - should i assign spotify artist links for such artist, coz from one side this will allow tool to fill them on release creation stage, but from other side - it could possibly link to wrong artist.
I would, and do (as evidenced by my links in my previous post). 
The links are still correct: You can find their music to stream for free via this link… the link just also lets you listen to other artists as well. When I am aware that an external ID covers multiple MusicBrainz IDs though, I try and make sure to link it to at least two of these, so anyone doing a “reverse lookup” (ie., tries to get the MBID from the external ID) are shown that the external ID is ambiguous and they should proceed with care. E.g., Yasmin was created specifically so I could link her to the Spotify ID so anyone looking up the Spotify ID could tell it didn’t cover only a single artist.
5 Likes
You are correct. On some artist it is either combined or wrong. Happens on iTunes and Deezeras well. Main thing to remember, and I use this awesome tool every day, is to double check and not rely 100% on the tools or scripts. I noticed that Khalid has the same issue on some releases.