A new version of Chromaprint has been released. This is a fairly big release I originally intended to call 2.0, but one key feature I was planning to include is not yet finished, so I decided to go with 1.4 instead. So what’s new? The biggest feature is that all components of audio fingerprinting process now work in a streaming fashion and can provide partial results at any time. That means that it’s now possible to feed a continuous audio stream to the process and get back partial fingerprints.

A new version of Chromaprint has been released. This is a very small bug fix release fixing fpcalc crash on a corrupt file. Changes since version 1.3.1: Fixed crash on an invalid audio file that FFmpeg could not decode. Fixed build on Ubuntu 14.04 with libav. Download: Source code tarball (525 KB) Static binaries for the fpcalc tool Windows, 32-bit (1 MB) Windows, 64-bit (1 MB) Mac OS X, 32-bit, 10.

A new version of Chromaprint has been released. Changes since version 1.3: Fixed fpcalc -length to actually restrict fingerprints the requested length. Fixed SONAME version for the shared library. Download: Source code tarball (525 KB) Static binaries for the fpcalc tool Windows, 32-bit (1 MB) Windows, 64-bit (1 MB) Mac OS X, 32-bit, 10.4+ (964 KB) Mac OS X, 64-bit, 10.4+ (944 KB) Linux, 32-bit (1 MB) Linux, 64-bit (1 MB)

A new version of Chromaprint has been released. This is another small release, there are no changes to the core functionality. Changes since version 1.2: The binary packages have been built with FFmpeg 2.8.6, adding support for DSF files You can use use fpcalc -length 0 to get the full fingerprint New function chromaprint_get_fingerprint_hash for calculating SimHash from the fingerprint data Added info section to the fpcalc executable on Mac OS X Generate .

It’s hard to tell the exact date when the AcoustID project started, but if we go by the first entry in the database, it was October 8, 2010. That means project turned five this week! I thought it’s a good opportunity to gather some statistics from those five years. Back in 2010, we were starting from scratch. We had an empty database, while the solution that AcoustID was replacing (MusicDNS/PUID ) had fingerprints for 4.

It seems that some people have been using the AcoustID demo API key from the documentation page for more than just testing, so it’s time to change it. If you were using the API key and your application stopped working, please register the application properly and get your own API key.

A new version of Chromaprint has been released. This release doesn’t add any new features to the library, but there are some source code changes for better compatibility when building the library in non-standard situations. Because the functionality hasn’t changed, this a source code only release. You can use fpcalc binaries from version 1.1. Download: Source code tarball (517.2 KB) Changes since version 1.1: Fixed compilation with neither libswresample nor libavresample (#11) Fixed compilation with static libav (#10) Functions chromaprint_encode_fingerprint and chromaprint_decode_fingerprint are changed to accept const pointer as input Added support for using the Kiss FFT library (should make Android port easier) Removed obsolete dev tools from the package More compatible DEBUG() macro

A new version of Chromaprint has been released. There are a few bug fixes, fixed compilation error on OS X 10.9 and added support for compilation with libav (FFmpeg is still the preferred library to use with Chromaprint). The official binaries have been build with FFmpeg 2.1. I have switched to a more automated build system for the binaries, so there might be new problems with them. If you find they do not work as expected, please let me know.

A new version of Chromaprint has been released. There are no changes to the library, just the fpcalc utility. The main changes are support for the latest version of the FFmpeg. The official binaries have been rebuilt with FFmpeg 2.0.1, with added support for reading audio from more video formats. If they are not able to read audio from some format that you use, please let me know. Download: Source code tarball (528.

Short version: I’m sorry, but today I had to block some applications from the AcoustID web service. If you were using AcoustID and now get an “invalid API key” error, please contact me . The long version is that when doing some maintenance today, I’ve found a few applications that are using the service against the usage guidelines. I knew this would come and I would have to deal with it, I just didn’t know when.