AcoustId Generator [MM3/MM4] v1.0 2012-01-28

Post a reply

In an effort to prevent automatic submissions, we require that you complete the following challenge.
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review

Expand view Topic review: AcoustId Generator [MM3/MM4] v1.0 2012-01-28

Re: AcoustId Generator [MM3/MM4] v1.0 2012-01-28

by Compulsive247 » Fri Jan 02, 2015 3:51 pm

Just wanted to say that I love this script. I'm a bit obsessive when it comes to my tagging. After generating my acoustid, I append before it, and I now have a working link to the Acoustid web page for a particular songs submission results. Most of the time, the more results listed, the more confidence I have that a track has been correctly identified. Then I can navigate to the recording information for that track on This helps to gather the accurate release information.

I know this thread is old but... What I'm curious about, is if this script could be modified to also return a track's MusicBrainz ID, and populate a custom field with said MBID?

Re: AcoustId Generator [MM3/MM4] v1.0 2012-01-28

by mhendu » Wed Jul 24, 2013 12:09 am

They're cleared up now - I reran the script today and all the tracks were tagged. Must've been a processing issue on their end. Hopefully not a recurring problem - I remember running into this type of issue with PUIDs in the past and at one point it was months before the tracks were tagged.

Re: AcoustId Generator [MM3/MM4] v1.0 2012-01-28

by MMuser2011 » Tue Jul 23, 2013 8:41 am

Are this missing tracks all available in MusicBrainz? What's about theyr duration?

If yes, you could ask Lukáš Lalinský in the Google Group:!forum/acoustid if he can check this specific cases (provide the trackid from MusicBrainz)

Re: AcoustId Generator [MM3/MM4] v1.0 2012-01-28

by mhendu » Tue Jul 23, 2013 7:19 am

Thanks - I tested this with a song that's not in the database as far as I can tell and while I got a response it failed to return an id. I enabled logging for the script and it looks like the status is pending for the tracks I am trying to submit via the API. So I gather that basically things are working on my end but the service is failing to generate the AcoustID for these tracks, which usually it does within an hour or so but in this case it's been a few days.

Re: AcoustId Generator [MM3/MM4] v1.0 2012-01-28

by MMuser2011 » Tue Jul 23, 2013 3:19 am

To test if the service is running, you can call the "official" windows commandline tool fpcalc.exe with one of your audiofiles.
You should get the DURATION and the FINGERPRINT.

With the Values for DURATION and FINGERPRINT, you can make a call to the AcoustID webservice: ... ABz0qUkZK4....
This client API-Key is for demonstration only!

If the service is running, you get back a JSON or XML response like this:
"status": "ok",
"results": [{
"id": "9ff43b6a-4f16-427c-93c2-92307ca505e0",
"score": 1.0

For further informations, please have a look at:

Re: AcoustId Generator [MM3/MM4] v1.0 2012-01-28

by mhendu » Tue Jul 23, 2013 12:25 am

It seems that songs I'm trying to tag with the AcoustID that are not in the database are not updating with an AcoustID now - I had this working on multiple PCs as of a week ago and now it's not working on any of them. Either my API key has been invalidated, the script needs to be updated or something's broken at AcoustID. It looks like AcoustID is continuing to receive submissions so it doesn't seem to be an issue on their end.

Any thoughts?

Re: AcoustId Generator [MM3/MM4] v1.0 2012-01-28

by MMuser2011 » Thu Apr 05, 2012 1:49 am

If a track already contains the calculated fingerprint in the id3tag, do you skip this song or do you re-calculate the data?

Is there a possibility to read/import existing Fingerprints (+ID, +Duration) from tracks to "your" SQL table?

Re: AcoustId Generator [MM3/MM4] v1.0 2012-01-28

by booblers » Sat Jan 28, 2012 11:39 am

reserved for faq

AcoustId Generator [MM3/MM4] v1.0 2012-01-28

by booblers » Sat Jan 28, 2012 11:39 am

This script is based on Trixmoto's Generate PUID script. The framework of the script comes from his original but it has been updated to work with AcoustId.

Download: ... MM3-4.mmip

The goal is essentially the same. To generate the unique identifiers related to AcoustId and store them in various places. There are some differences:

-The time to generate a fingerprint and save it to the various places is 1-2 seconds (depending on your system)
-You can choose to use Writetag to save the information to community standard "custom" tags.
-You can choose to save the information to SQL tables that can be used in other scripts (like my MusicBrainz NGS + AcoustId Tagger)
-You can choose to save the actual fingerprints and/or the associated unique identifiers
-You can enter a User API key and contribute to the AcoustId Database.

It is also still possible to save the AcoustId unique identified to an MM field of your choosing.

There are some caveats/warnings associated with writing the custom tags. You can read about them in the first post of the thread the MusicBrainz NGS tagger linked above.

I haven't tested this extensively on file formats that I don't use (like m4b, wma, etc) - I'm not sure how it will react in those situations. Please let me know how it does with those if you have any to test with. In principle one should be able to tag an entire library with the acoustid identifiers and then the MusicBrainz NGS tagger will detect the embedded tags and give you speedy results in the future.

Usage Notes:
Tools->Scripts->AcoustId Generator (after selecting the files you'd like to tag/analyze)

When testing new file formats you might want to leave logging on - but in general it should be off because it slows things down.

In order to cut down on requests the script is making batch requests to the Acoustid server. After fingerprinting 10 files (or reaching the end of the list) it will request unique ids from the server. This means that if you terminate the script you can lose up to 9 calculated fingerprints. Not a huge deal but someone might wonder why some weren't saved.