Acoustid fingerprinting

[GoogleCodeExporter]

There's a very exciting new project by the names Acoustid and Chromaprint:
http://acoustid.org/

The project consists of a high-quality, entirely open-source acoustic 
fingerprinting algorithm and associated database. The library might be more 
accurate and faster than Last.fm's fingerprinting and the backing database 
contains more useful information: namely, it links tracks directly to their 
MusicBrainz IDs.

We should build a plugin modeled after the "lastid" plugin that provides this 
functionality.

Original issue reported on code.google.com by adrian.sampson on 31 Mar 2011 at 10:26

[GoogleCodeExporter]

Original comment by adrian.sampson on 16 Sep 2011 at 6:05

• Added labels: Milestone-1.0b11
• Removed labels: Milestone-1.0

[GoogleCodeExporter]

"chroma" plugin added in 875c50518c22! Woohoo.

Read the docs:
http://beets.readthedocs.org/en/latest/plugins/chroma.html

Original comment by adrian.sampson on 12 Nov 2011 at 11:33

[GoogleCodeExporter]

Original comment by adrian.sampson on 12 Nov 2011 at 11:33

• Changed state: Fixed

[GoogleCodeExporter]

I'm not sure where to ask this - I hope this works.

I've gotten the binaries necessary for windows to generate an acoustid 
fingerprint for an audio file. I have not been able to get the plugin working 
in beets. I think this is because I didn't compile dynamic libraries and am 
instead using just binaries?

I wonder if the plugin might accomodate windows users who (by and large) are 
not great about compiling their own linked libraries and are much more used to 
using libraries.

There are compiled ffmpeg and chromaprint binaries available and I can use them 
both and get to the FINGERPRINT=<data> output from chromaprint but of course 
beets doesn't seem to be able to use these binaries (they are in the path).

Maybe something like: if os=windows then execute "ffmpeg -i <audiofile> -acodec 
pcm_s16le temp.wav" then execute "fpcalc temp.wav" then store output?

That would make fingerprinting much less painful for windows users... if that 
makes sense?

Original comment by michael....@gmail.com on 15 Jan 2012 at 10:46

[GoogleCodeExporter]

Hi, Michael -- you did reach me, but it might be a little less awkward if we 
continue this discussion on the mailing list:
http://groups.google.com/group/beets-users

You're totally right that beets should be able to use the publicly available 
Windows binaries for Chromaprint. At the moment, as you've guessed, it does 
assume a DLL, which is not currently provided by the author. There are two 
options I can see here:
- As you suggest, use command-line invocations instead of library calls on 
Windows.
- Alternatively, compile and distribute a Windows DLL that's easy to install.
I'll look into both of these. I am very unfamiliar with Wndows development 
tools, though, so I may need help with some of this...

Original comment by adrian.sampson on 16 Jan 2012 at 6:26