~ Access Features for Music Using AcoustID, Musicbrainz and AcousticBrainz» By Joren on Friday 08 May 2015
This post describes how to connect music in your library with precomputed features. Say, for example, you are developing a DJ application and you want to facilitate mixing tracks. To provide a seamless mix you perhaps want information about beats and about the key the music in your library is in. Since vast databases of features are already available you probably want to access those, instead of using your own feature extractors and database. The problems that need to be addressed are:
- Automatically identify the music in your library without relying on incomplete meta-data (tag information).
- Connect the music with a data-base of meta-data. Preferably a large and well curated database.
- Fetch pre-computed features for the music. The features should be extracted using algorithms that are currently state of the art or at least perform well. The features and the audio itself should be synchronized, otherwise beat information, for example, is not of much use.
To help with these task there are several open source tools and services available.
To identify music a condensed representation of musical audio is created. This process is known as acoustic fingerprinting. On the website AcoustID a tool is available to create such fingerprint. The library is called Chromaprint and the command line client is called
fpcalc. Currently the latest version is Chromaprint version 1.2 and static binaries for
fpcalc are available on the AcoustID website. A packages for Debian (and probably Ubuntu) can be installed by calling
apt-get install libchromaprint-tools. Once this tool is correctly installed a fingerprint for a piece of music can be created:
fpcalc music.mp3 FILE=music.mp3 DURATION=168 FINGERPRINT=AQADtEmi..hADAAOCGAQghZRgQByjAEAICSMWYME
A fingerprint by itself is not of much use. The AcoustID webservice translates a fingerprint into one or more MusicBrainz identifiers. One fingerprint can result in multiple identifiers because the same audio can be released on several albums. There is documentation for AcoustID webservice available. To use the webservice an API key is needed. Confusingly, the AcoustID service has two types of API keys. One for end-users and one for developers. The last type is needed to translate ID’s. To request a developer API key, log in on the AcoustID website and “add an application”, there you can find the correct API key. Substitute
dev_api_key in the following URL. Also change the fingerprint and duration to match the information provided by the
fpcalc application. The webservice should reply with a set of MusicBrainz identifiers:
AcousticBrainz provides features for a subset of music that has a MusicBrainz identifier. Currently about a million tracks are analyzed but more are added every day. The API for the webservice is straightforward:
GET http://acousticbrainz.org/96685213-a25c-4678-9a13-abd9ec81cf35/low-level GET http://acousticbrainz.org/96685213-a25c-4678-9a13-abd9ec81cf35/high-level
The low-level features include beat positions and chroma information. For the hypothetical DJ-application this is the information that would be used.
If you find the services useful please consider contributing to MusicBrainz, AcoustID and AcousticBrainz.
A small Ruby script to automatically fetch features for audio can be downloaded here. It needs Ruby and a RubyGems to parse JSON. On Debian this can be installed with
apt-get install ruby and
rubygems install json. Once these dependencies are installed the script can be ran as follows:
ruby mbid_lookup.rb example.mp3 Found 6 musicbrainz identifiers! Not found in AcousticBrainz: 0afcd4a1-3709-499b-b76f-0d5491f839a5 Beat positions for 3d49fab8-fd08-42be-b0d2-9f1dc884d902: 0.522448956966,1.05650794506,1.57895684242,2.10140585899,2.61224484444,3.13469386101 Not found in AcousticBrainz: 448258f0-aa5a-4968-8efd-8c9348d5142e Not found in AcousticBrainz: adcd7079-57d9-49bd-a36b-a20fa27b02b1 Beat positions for d1cd1321-0b66-4848-935e-f3afba6c7356: 0.441179126501,0.905578196049,1.369977355,1.83437633514,2.29877543449,2.76317453384 Not found in AcousticBrainz: e1f433be-af6b-4b5d-a969-4b53f014c395