I don't think it means it's corrupt, just something the DLL doesn't like about it. I don't know all the things, but it won't do certain file types, for example.

Thank you once again for your modifications. I like having a message in the field informing why the PUID was not generated. Very cool.

The "unanalyzable" does not 'make perfect sense to me'. What could it mean?

Does it mean that my audio file is corrupt?
Does it mean that my *.mp3 extension is false and that it is really an *.mp2 file? This was mentioned in other help files.
Does it mean that....

If there is something I could do to clean up the file so that it could be analyzed, I would surely do it.

Thanks again.
Cheers

I'm not sure, I think it means that they haven't confirmed the PUID yet.

OK, I feel stupid... I had about 600 songs in my library that came back blank, so I reran them with the put status in option.

Unanalyzable makes complete sense, but what does Pending mean?

Will they ever change? Do I have to wait and rerun them?

Can I do anything with good old MusicIP mixer or something to work around this?

Some are mainstream stuff sort of and at least a few years old... like Bad Religion: 30 Years Live, Phantom of the Opera SF cast, Shakira Live from Paris... Eclectic, I know....

[quote="trixmoto"]Great. I'll probably create a separate script to handle this then, rather than trying to build it into this one.[/quote]
Sweet!

Great. I'll probably create a separate script to handle this then, rather than trying to build it into this one.

Lukáš Lalinský (the inventor of AcoustID and chromaprint) answered on another forum:[quote]...The comment [about uncompressed data] is specifically about the Chromaprint library, that is if you use it from your application. The fpcalc utility handles both the decoding and the fingerprinting. If a program simply calls fpcalc.exe and reads the output, it doesn't need to decode the files nor link to Chromaprint directly.[/quote]
So yes, I'm sure. :wink:
If you wanna be sure: Create a fingerprint under windows with fpcalc.exe from a well known track. Try the [url=http://acoustid.org/webservice#lookup]lookup[/url] function with this fingerprint from the acoustid webservice and you should get an answer with at least the AcoustID. If you add the meta parameter 'recordings' you get the MusicBrainzID as well.

Are you sure that fingerprint is correct? The link you pointed me to says that this tool is designed to only work with uncompressed data and not .mp3 files.

Just run "fpcalc.exe" to the audiofile(s) and you get 3 values:[code]FILE=C:\Users\MyName\Music\01 - test.mp3
DURATION=356
FINGERPRINT=AQADtEmS.....[/code]The second and third line are the one who should be written back to the audiofile.

Thanks, I'm glad you've found it useful.

It seems the biggest problem with using AcousticID is that the script "needs to find a way to decode audio files (MP3, MP4, FLAC, etc.) and feed the uncompressed data to Chromaprint". I'm not sure this is possible, without getting you to convert all of your tracks to .wav files first, unless I can find another application to do that. If I could get over that technical hurdle then I guess it should be possible.

Thank you for this update, trixmoto! Another fine piece of excellent software! :wink:

What do you think about a version for AcoustID?
Could I replace the external tool to calculate the PUID with the one to calculate the AcoustID ([url=http://acoustid.org/chromaprint]fpcalc.exe[/url])?

New version (2.5) is now available to download from my website. Changes include...

- Fixed getting short path with new API method
- Added option to tag with status if no PUID available

I never touch the Tempo field.

Hey Trix,

Noticed something odd when running PUID Gen.: Any item in the Tempo field gets placed into the Comments field. Just thought I'd let you know.

I've added this to my list, I'll take a look when I've got a chance.