-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
mbcollection: MusicBrainz API error #1152
Comments
Can you please provide the verbose log (supply the -v flag to beet)? Also, does this happen for a specific album or for any music? |
Hi, I don't know if it happens for any albuns. I have used picard to update all tags, and just add the album to beet library using beet import C:\Users\Eduardo\Music\Collection verbose.log: My config.yaml |
Thanks for the confirmation; I can reproduce this. Looks like a MusicBrainz API must have changed. Investigating… |
Should be fixed now. It was indeed the MB API (specifically, they added "event collections" in addition to release collections). Thanks again for reporting! |
Sorry for this simples question, but how do I update it? |
@cemmec, please see the FAQ about running from source. |
Working... Thanks for the quick response... |
A site like Musicbrainz, that is meant to have a powerful API, should probably think about implementing API versions... |
Hi,
When I try to use beet mbpdate I'm receiving the following error:
Updating MusicBrainz collection 63b52b5f-589e-311b-bd7d-11722fcc3c18...
error: MusicBrainz API error: caused by: HTTP Error 400: Bad Request
I'm using Windows 8.1 and I followed the guide on http://beets.readthedocs.org/en/v1.3.9/guides/main.html to install beet.
Thanks!
The text was updated successfully, but these errors were encountered: