mbcollection: MusicBrainz API error

[cemmec]

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!

[sampsyo]

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?

[cemmec]

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:
C:\Users\Eduardo\Downloads>beet -v mbupdate
user configuration: C:\Users\Eduardo\AppData\Roaming\beets\config.yaml
data directory: C:\Users\Eduardo\AppData\Roaming\beets
Sending event: pluginload
library database: C:\Users\Eduardo\AppData\Roaming\beets\library.db
library directory: C:\Users\Eduardo\Music\Collection
Sending event: library_opened
Updating MusicBrainz collection 63b52b5f-589e-311b-bd7d-11722fcc3c18...
error: MusicBrainz API error: caused by: HTTP Error 400: Bad Request

My config.yaml
directory: C:\Users\Eduardo\Music\Collection
import:
write: no
copy: no
move: no
resume: no
autotag: no
log: beetslog.txt
plugins: mbcollection
musicbrainz:
user: myuser
pass: mypass

[sampsyo]

Thanks for the confirmation; I can reproduce this. Looks like a MusicBrainz API must have changed. Investigating…

[sampsyo]

Should be fixed now. It was indeed the MB API (specifically, they added "event collections" in addition to release collections). Thanks again for reporting!

[cemmec]

Sorry for this simples question, but how do I update it?

[sampsyo]

@cemmec, please see the FAQ about running from source.

[cemmec]

Working... Thanks for the quick response...

[tiagoad]

A site like Musicbrainz, that is meant to have a powerful API, should probably think about implementing API versions...