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

Qobuz importer button does not show #482

Open
Annis3110 opened this issue Apr 19, 2022 · 4 comments
Open

Qobuz importer button does not show #482

Annis3110 opened this issue Apr 19, 2022 · 4 comments

Comments

@Annis3110
Copy link

I've tried on both the qobuz store and the qobuz web player but couldn't find the button on either of them. I've logged in to both my qobuz account (free account with no subscription) and musicbrainz account.
IMG_20220419_202316_431
IMG_20220419_202448_011
I'm using Violetmonkey's and edge's latest version. Please tell me if you need the version number of violetmonkey extension and edge.

@sleepuntilspring
Copy link

im having the same issue as well

@redactedscribe
Copy link

Still broken. Easiest way I've found for the time-being to get the bare minimum into MusicBrainz is the highlight and copy the tracklisting in full, put it into a text editor like VS Code, then use Alt + Click (or whichever other method) to define cursors for each track, and then batch sort the lines into the MBz track parser format:

1. Title - Artist (00:00:00)
2. Title - Artist (00:00:00)
...

Then just paste it into the track parser on the MBz Add Release page and fill the rest.

Some links about the broken script:

https://community.metabrainz.org/t/qobuz-importer-script/569614
https://community.metabrainz.org/t/qobuz-script/585934

@Serene-Arc
Copy link

So I did a bit of poking and the reason that this script is failing is quite simple and rather inescapable. Qobuz has decided to unpublish their API and seems to be phasing it out. The API call that the script waits for never comes and there's no documentation or way to make a call ourselves.

From what I can tell, the only way forwards for this userscript vis-a-vis Qobuz is to parse the page directly, which will lead to less and lower-quality information. Unfortunately there's not currently a way around that.

@realbaylen
Copy link

:(

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

5 participants