Echoprint: Open-source music fingerprinting

I'm a bit confused by the database license. Why do you want people to contribute additional data specifically back to you, rather than requiring them to release it under a compatible license which would allow you to incorporate it if you wish? This is substantially different from usual copyleft licenses.<p>As an example, notice that Wikipedia does not require people to send modified articles back to the Wikimedia Foundation, or to allow them to use the data as they see fit (this is clause D. 3. d. in your license). They just require people to contribute under a copyleft license, and they can thus incorporate derivative versions published elsewhere if they want. This is nice because it ensures that the Wikipedia content can be useful even if the Wikimedia Foundation disappears.<p>Anyway, awesome work, congrats!

Given how threat-, or, let's say, notification-happy Landmark was just a while ago [1], does anyone have an idea regarding the patent situation? Is this implementation different enough to be considered (reasonably) "safe"?<p>[1] <a href="http://www.redcode.nl/blog/2010/07/patent-infringement/" rel="nofollow">http://www.redcode.nl/blog/2010/07/patent-infringement/</a>

This is really amazing, and I can't wait to see all of the possibilities it opens up now that people can create their own databases. I'm tempted to set up an app to fingerprint and dedupe all of the music spread out throughout the network here at work.

if you have any questions, let me know. we're very excited about this!

I think the fingerprinting part is similar to pHash: <a href="http://www.phash.org/" rel="nofollow">http://www.phash.org/</a> but echoprint is more focused on music and they are building a database of fingerprints.<p>I think pHash also has functions for fingerprinting music but might not be as precise since pHash is not strictly focused on music.

Echonest are some cool people. Their earlier APIs enabled the illustrious although sadly now defunct <a href="http://www.donkdj.com" rel="nofollow">http://www.donkdj.com</a> which was done by a classmate of mine as a project for a Generative Creativity course we did at uni.<p>Looks like their research has taken them a lot further!

I'd love to see a project where the data is MIT licensed too, not just the code.

A very interesting project. I've whipped up a little test program(<a href="https://github.com/regomodo/handy_scripts/blob/master/echoprint-codegen-builder.py" rel="nofollow">https://github.com/regomodo/handy_scripts/blob/master/echopr...</a>) in Python and found either the codegen or echonest to be a little buggy. Daft Punk fingerprints come back with some very unusual results. <a href="http://pastebin.com/8Tfvd0SZ" rel="nofollow">http://pastebin.com/8Tfvd0SZ</a>

Why aren't the fingerprints in the database covered by the recording copyright on the song that they were derived from?

Woah. This is going to be massive. The amount of things that could potentially be built on top of this is scaring me.

How is this different from Shazam?

This is huge. I've been mulling some ideas for awhile that would require music fingerprinting, but I've always been too overwhelmed by the available options, from a licensing and implementation standpoint. I can't wait to play with this!! :D

Looks incredible! One note though, the page seems to partially break for me in Safari on the Mac (the sidebar overlaps onto the content as I scroll horizontally).<p>But the tech looks incredible. Good work for releasing this!

for more on the whys, here is the EN blog post: <a href="http://blog.echonest.com/post/6824753703/announcing-echoprint" rel="nofollow">http://blog.echonest.com/post/6824753703/announcing-echoprin...</a>

Holy balls you guys are awesome for releasing this.