Open Content Music Database Launched
An anonymous reader writes "The open source music database MusicBrainz was launched officially today. The data is partly in the public domain, partly under an open content like license. It includes artist/album/track information, with more to come. There's support for CDDB-like CD identification (actually, a lot of the current data was imported from freedb), but also identification of single tracks via audio fingerprints (TRMs). Help both in adding new content by tagging your music collection and consolidating the existing data is welcome. Also check out some technical information on the XML database at IBM developerWorks."
I find the idea of a program that can identify my MP3s by audio fingerprint, and will submit that information to somewhere on the Internet a little creepy...
I had brought up to my friends several times, how it would be great to start something similiar. The metaratings are a great idea, providing the database openly to the public is great, and i'm falling in love with their tagging utility.
And it's all non-profit! (and will likely get better each and every day now that it has all this slashdot traffic)
I am this close to posting the 28 meg mysql database on my school account, but I think the coe admins would kill me!!
hooray! it's a sex wiki
example image
hooray! it's a sex wiki
I looked at this project about 8 months ago and planned to use this setup for an open source media utility.
:
I stopped short at that time because
1) the TRM (song fingerprint) technology was owned by a seperate entity and was closed/private.
*Paranoid pondering* what if the TRM tech owners decided to charge for future use after the database was largely used and accepted. Although the database would remain open, they could charge for new fingerprints (song IDs). Not neccessarily a bad thing but we've all seen things how f'd up these situations can get.
2) the TRM generation took place on the server. Doing a batch of fingerprints would tie up a connection for quite a while.
My brainz a bit fuzzy on this but I think a portion of the actual audio data is uploaded and then processed on the server. I figured that generating TRMs completely client side and then uploading/matching song data to the server would do better for scalability.
Just the same I haven't looked a the project recently and it may have since changed.
Regardless I think its a pretty cool idea.