1. AcoustID
  2. AcoustID
  3. chromaprint




build status

Chromaprint is an audio fingerprint library developed for the AcoustID project. It's designed to identify near-identical audio and the fingerprints it generates are as compact as possible to achieve that. It's not a general purpose audio fingerprinting solution. It trades precision and robustness for search performance. The target use cases are full audio file identifcation, duplicate audio file detection and long audio stream monitoring.


The most common way to build Chromaprint is like this:

$ make
$ sudo make install

This will build Chromaprint as a shared library and also include the fpcalc utility (which is used by MusicBrainz Picard, for example). For this to work, you will need to have the FFmpeg libraries installed.

See below for other options.

FFT Library

Chromaprint can use multiple FFT libraries -- FFmpeg, FFTW3, KissFFT or vDSP (macOS).

FFmpeg is preferred on all systems except for macOS, where you should use the standard vDSP framework. These are the fastest options.

FFTW3 can be also used, but this library is released under the GPL license, which makes also the resulting Chromaprint binary GPL licensed.

KissFFT is the slowest option, but it's distributed with a permissive license and it's very easy to build on platforms that do not have packaged versions of FFmpeg or FFTW3. We ship a copy of KissFFT, so if the build system is unable to find another FFT library it will use that as a fallback.

You can explicitly set which library to use with the FFT_LIB option. For example:

$ cmake -DFFT_LIB=kissfft .


FFmpeg is as a FFT library and also for audio decoding and resampling in fpcalc. If you have FFmpeg installed in a non-standard location, you can use the FFMPEG_ROOT option to specify where:

$ cmake -DFFMPEG_ROOT=/path/to/local/ffmpeg/install .

While we try to make sure things work also with libav, FFmpeg is preferred.

API Documentation

You can use Doxygen to generate a HTML version of the API documentation:

$ make docs
$ $BROWSER docs/html/index.html

Unit Tests

The test suite can be built and run using the following commands:

$ cmake -DBUILD_TESTS=ON .
$ make check

In order to build the test suite, you will need the sources of the Google Test library.

Bindings, wrappers and reimplementations in other languages:


If you know about a project that is not listed here, but should be, please let me know.

Standing on the Shoulders of Giants

I've learned a lot while working on this project, which would not be possible without having information from past research. I've read many papers, but the concrete ideas implemented in this library are based on the following papers: