search

atj / userscripts

A collection of userscripts primarily relating to to importing and editing releases on MusicBrainz.
MIT License
27 stars 5 forks source link

d.ontun.es is down #213

Open YoGo9 opened 2 months ago

YoGo9 commented 2 months ago

The last few days it seems like the domain expired therefore it does no longer work, is it possible to update the link that it should send to https://magicisrc.kepstin.ca/ instead?

Lioncat6 commented 2 months ago

https://isrchunt.com/spotify/importisrc

ISRC hunt also works great with Spotify links!

If you want to modify the script yourself until an official fix exists: Line 54: elem.href = `https://isrchunt.com/spotify/importisrc?releaseId=${spotifyId}`; image

Lioncat6 commented 2 months ago

I'll probably make a pull later to propose this change

Lioncat6 commented 2 months ago

https://github.com/atj/userscripts/pull/216

arsinclair commented 1 month ago

@atj Could you take a look at the PR above please! This would help greatly.

atj commented 1 month ago

Does anyone know how ISRC Hunt matches MB recordings to Spotify? I don't really like the fact that we just pass a Spotify ID and not a MBID...

Lioncat6 commented 1 month ago

As for MBID's, it's preforming a Lookup based on url resource. The MB api has a ton of things you can look up a release by. It works simular to the way I've made SAMBL, though by album and not artist

Lioncat6 commented 1 month ago

I want to make an open source api for this that would allow specification of an MBID in case of 2 releases with the same spotify id

arsinclair commented 1 month ago

@Lioncat6 are you a maintainer of that project?

that would allow specification of an MBID in case of 2 releases with the same spotify id

How such conflict is currently handled? Does it present the user with a choice, or it just rejects the import since it's ambiguous?

Lioncat6 commented 1 month ago

@Lioncat6 are you a maintainer of that project?

I am not, just peiced together how it works

that would allow specification of an MBID in case of 2 releases with the same spotify id

How such conflict is currently handled? Does it present the user with a choice, or it just rejects the import since it's ambiguous?

I have no clue, I'll check in a bit

Lioncat6 commented 1 month ago

This is the thread of the person who created isrchunt if you want to ask here: https://community.metabrainz.org/t/isrchunt-is-a-songs-isrc-already-in-musicbrainz/656127?page=2

arsinclair commented 1 month ago

Thank you for the information. The tools appears to be a bit buggy, I just went through 25-30 releases of mine and tried importing, and in 10 cases the tool returned 500 Server Error.

Still, I guess it's better than nothing...

Lioncat6 commented 1 month ago

Like I said, I want to make my own version specifically for Spotify importing. May or may not be integrated into SAMBL directly, not sure yet.

arsinclair commented 1 month ago

Okay, it seems when there's two or more releases it just takes the first one, it doesn't resolve the conflicts 😢

Here's an example where two releases by mistake were linked to a spotify page, and it doesn't do a good job: https://isrchunt.com/spotify/importisrc?releaseId=0GAeZ2HCkJ1GL5LaosklAG

arsinclair commented 1 month ago

I want to make my own version specifically for Spotify importing. May or may not be integrated into SAMBL directly, not sure yet

I wasn't able to find a repository for https://isrchunt.com, so I guess it's closed source. It would make sense to have an open source one.