Echoprint: Open acoustic fingerprinting

Posted Jun 30, 2011 17:35 UTC (Thu) by iabervon (subscriber, #722)
In reply to: Echoprint: Open acoustic fingerprinting by felipec
Parent article: Echoprint: Open acoustic fingerprinting

It looks to me like this is evidence of the opposite: it's great to rely on a proprietary component, because a better open-source component will arise, either before you need it or soon after. In general, it's often good to start with some dependency as a temporary measure, until there is something really good available. The fact that having your dependency be proprietary is doomed in the long run is actually a benefit here, because it means that you will actually get around to making the transition.

Echoprint: Open acoustic fingerprinting

Posted Jul 7, 2011 7:06 UTC (Thu) by jamesh (guest, #1159) [Link] (1 responses)

Of course, this isn't the first time MusicBrainz has had its proprietary fingerprinting solution disappear from under them.

The PUID system they currently use was a replacement for a different proprietary system called TRM. The company behind the TRM fingerprinting had moved on to other things, and the server software was unreliable for the load it was being put under.

It was a bit surprising to see MB switch to another proprietary solution after their prior experience, but it is good that they've finally got an open system they can rely on.

Echoprint: Open acoustic fingerprinting

Posted Jul 7, 2011 14:42 UTC (Thu) by lukaslalinsky (guest, #76480) [Link]

There were these two options:

1) Proprietary solution
2) No fingerprinting at all

I think it's a fairly obvious choice. If there was an open solution back then, MusicBrainz would have used it, but there wasn't and MB was never interested in developing its own fingerprinting technology because it's not the primary goal of the project.