As strange as it might sound, the Acoustid submission API can now also accept PUIDs instead of MBIDs . I had the idea of using PUIDs to help bootstrap the Acoustid database for a long time, but I avoided implementing it, because I was afraid of bringing all the PUID↔MBID matching errors to the database. The topic came up yesterday and I realized that with having the audio fingerprints, MBIDs and MusicBrainz metadata in the same database, I can pretty easily remove any suspicious matches.

Since I announced the Acoustid project, I got over 1.1 million fingerprint submissions (mostly from MusicBrainz editors ), covering about 580 thousand unique MusicBrainz track IDs. In the background I was running a process that imported the raw submissions and merged similar tracks. All this was done on a virtual machine with 1GB of RAM. It wasn’t very fast, but I was surprised it was even able to handle such amount of data.

After posting about the beta version of Acoustid Fingerprinter, some people successfully used it to submit fingerprints and I also started using it as the main tool for submitting fingerprints, so I think it’s time for a proper release. More details on the wiki: Acoutid Fingerprinter 0.1 Chromaprint 0.1 If you are using Windows, you can simply download and unzip the binary package. On Ubuntu (Lucid, Karmic and Maverick), you can install it from my PPA:

Since my last Acoustid-related post, I was working on a GUI application for submitting fingerprints. It’s far from finished, but I think it has reached the state where it can do something useful without breaking on trivial problems. Those who used the old Last.fm fingerprinter will know where I got the inspiration for the UI. :) There isn’t much functionality. You copy&paste; your Acoustid API key , select which directories to scan and let the application do its job.

Some news on the Acoustid project… New website 🔗At first I wanted to do everything on the server side in Java, but as I was delaying it, I realized I better quickly just hack something up in PHP and then maybe write a better solution later. So I spent last weekend working on the website and came up with this . Nothing fancy, but the I needed the website only for API key management.

After asking for fingerprint test data in my last post about Chromaprint I received about 270k fingerprints from. This helped me to perform some larger tests on the proof-of-concept lookup server I had implemented using Java and PostgreSQL. I had to do some technical changes, but the main idea seemed to work pretty well. I wasn’t sure about this when I was working on Chromaprint, but now I believe that I can realistically run an audio recognition service.

After several months of reading research papers, learning and weekend coding, I’m very happy to make the half-finished code of my audio fingerprinting library public. :) I’m doing this mostly for selfish reasons, because it will force me to stop thinking in “hacker mode” and hopefully properly finish it, and I also hope to get some help and feedback from other people. There is nothing for regular users yet though, just for developers or people not afraid of the command line.