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

[booblers]

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: http://www.mediafire.com/file/dwjhzih0i ... 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.

[booblers]

reserved for faq

[MMuser2011]

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?