#beets

sampsyo_, got any thoughts on file locking in regards to mutagen? Would ir

Would it providing any guarantees help beets?

lazka: Good question. At the moment, beets itself avoids concurrent file modifications, but maybe there could be strange situations when interoperating with other software?

sampsyo_, generally we only could protect against mutagen modifying the same file in different threads

file locks are advisory only

Right, good point, so other software would need to respect them too.

I think the answer is that it would not be a big deal for beets—since the concurrency we use internally wouldn't need file locks.

sampsyo_, ok, thanks.

As an aside, thanks for all your work on Mutagen lately! Awesome progress.

do I need to to anything else than start a musicbrainz vm and enter localhost:500 in the beets config before I can use it with beets? :)

rotzbouw: You will likely want to setup replication on the VM.

Freso: hm, i'll look into that, thanks

Freso: doesn't that just pull in all updates from the main db?

Yep.

okay, then I wasn't specific enough. I think I just have a connection problem. I can access localhost:5000 via browser but beets seems to fail to connect

e.g. it says "Error: MusicBrainz not reachable in release search with query {u'release': u'next stop soweto 4: zulu rock, afro-disco & mbaqanga 1975-1985', u'tracks': u'15', u'artist': u'various artists'}"

with a preceding Python error: "NetworkError: retried 8 times, caused by: HTTP Error 503: Service Unavailable"

rotzbouw: There's no particular reason why beets would engender a 503 while your browser doesn't -- you may want to look at the logs for the MB server inside your VM.

yeah. the rate may be too high or sth. i'll look into it. thanks.