Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

d.ontun.es is down #213

Open
YoGo9 opened this issue Sep 12, 2024 · 14 comments
Open

d.ontun.es is down #213

YoGo9 opened this issue Sep 12, 2024 · 14 comments

Comments

@YoGo9
Copy link

YoGo9 commented Sep 12, 2024

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
Copy link
Contributor

Lioncat6 commented Oct 3, 2024

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
Copy link
Contributor

Lioncat6 commented Oct 3, 2024

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

@Lioncat6
Copy link
Contributor

Lioncat6 commented Oct 3, 2024

#216

@arsinclair
Copy link

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

@atj
Copy link
Owner

atj commented Oct 24, 2024

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
Copy link
Contributor

Lioncat6 commented Oct 24, 2024

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
Copy link
Contributor

Lioncat6 commented Oct 24, 2024

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
Copy link

@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
Copy link
Contributor

@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
Copy link
Contributor

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
Copy link

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
Copy link
Contributor

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
Copy link

arsinclair commented Oct 25, 2024

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
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants