MMuser2011 wrote:Thank you very much for this very usefull script, CarlitoGil!]
Very welcome, man! (or lady.)
MMuser2011 wrote:You should declare [...], it is not necessary to have iTunes installed on the PC, it is not necessary to have an iTunes Account to search for tracks.
I hadn't consider that. I clarify it right after this post. Thanks.
Could you please add the calculated AcoustID fingerprints to the MediaMonkey database? This would be a fantastic new possibility to find duplicate tracks - only comparing audio data, no metadata, no naming mismatch, just the plain audiodata.
Maybe you could use one of the existing custom fields (user selectable)?
This, my friend, is another great, great way to use Acoustid.
First, let me clarify that "Audio Fingerprint" and "Acoustid ID" are not the same.
A fingerprint is generated in your computer from the audio file then it's sent to acoustid.org, where they store that fingerprint and others very close to it and assign to then all the same Acoustid ID to unify their metadata. What you want to compare are the Acoustid IDs. Calling them fingerprint is fine, but to avoid confusion I'm going to call them by those terms.
So, iTunesMonkey already is able to store the Audio Fingerprints in the database under a table
called by default AcoustidFingerprints
. That information is not shown in the Properties
window. It's just a way to cache the Audio Fingerprints which can take a second or two to generate each time. That won't help you too much to identify duplicates.
I actually had one or two lines of code in my script to add the Acoustid ID to a custom field for debugging proposes. It worked great to compare duplicates.
But adding, as a feature, the Acoustid ID to custom fields seems to me to be outside of the purpose of the script. It just wouldn't be clean. And to compare the custom field you would need another script anyway. So, this is my suggestion:
Get AcoustId Generator
, which will do exactly what you're asking for. It let's you choose the field you want to fill with the Acoustid ID.
Combine that with Advanced Duplicate Find & Fix
to compare the fields, and you'll find duplicates that you may have never found otherwise.