Wow, this is crazy because I'm working on a streaming music player of my own, also using HTML5, Backbone and Flask. (As well as Flask-SQLAlchemy and Mutagen, but those are obvious choices given Flask.) Congrats on shipping first. How long have you been working on this? I might actually use yours until my take on this is done. It certainly looks superior to Subsonic in every way. I'm still going to finish mine, becaus…
Crazily, I have also built a (rudimentary) similar project out of Flask, Backbone, and HTML5 audio (and Mutagen, of course). It's a piece of a larger music-management puzzle: http://beets.readthedocs.org/en/1.0rc2/plugins/web.html Anyway, zx2c4's project is obvious slicker than mine. It's somewhat crazy that all the people on this thread saying "hey, me too" are only now finding each other. I think there are some pre…
beets is a great music importer. A few months ago I wanted to write something like that — looking up releases in a central repository, automatically correcting tags and renaming. But I hadn't got very far, so I abandoned the project when I saw you had already done it way better.
I would prefer if it pulled data from Discogs instead of MusicBrainz. Have you considered using the Discogs API? In my limited experience, MusicBrainz disappoints me by "correcting" tags to something wrong because there's a typo in the DB, or changing the typography ("and" -> "&", "... (Part One)" -> "..., Part 1") in a way that doesn't match the official track listing. Also a very, very large percentage of albums I run through beets aren't in the MB database at all. I think I'm spoiled by how good Discogs is: these problems would mostly go away. Last.fm's data might also be an improvement, though it's not on par with Discogs.
> it would be prudent to informally standardize a REST/JSON API for music collections
This sounds cool. If you come up with a spec for this, I'd like to know too (email in profile).