i find that the ease of mass-changing tags in foobar makes it seem THAT much more of a pain to manually re-make md5 files (if you use them). i would love a plugin that allowed me to highlight an album and make/remake an .md5 file inside its directory.

I'm planning to work on a plugin for crc, md5 and fingerprint* generation and verification - all I need is some free time and boredom

* fingerprint == md5 of decoded pcm data, for lossless audio files

I 2nd the request for such a plugin.
Some imho useful functions:

-Auto re-create MD5 on tag/filename change.
-Replace old MD5.
-Filename of MD5 can be formatted from tag values.

tia

That would be very cool plugin (and very useful too).

awesome. is there any chance you would look into making a checksum (md5 or sha1, i suppose) that checks only the audio portion of files? and not tags?
that way you could change tags/replaygain files and the md5's would still check out alright.

i definitely second those.

"-Filename of MD5 can be formatted from tag values."

...........or folder name

you realise, if you write the md5 to a tag in the file, the md5 of that file will change?

your better off making a seperate file with multiple lines of

filename : md5

or.. is that what your on about anyway?

sure, external file .... sfv / md5 and possibly sha1

Are you sure you want me to answer this question?

what for?

1) not feasible - can't think of any way for the plugin to keep track of changes being made to files.

2) care to elaborate on what you mean by this?

3) Guess I'll make use of tagz for filename formatting, so this one shouldn't be too much trouble.

Maybe this is not interesting to anyone, but...
Why not insert MD5 info of raw encoded file into a tag?
Then you can change filename, tags, replaygain... and you can even know if your file has changed. Of course standard MD5 programs won't be able to read this, but sure that someone does some beauty prog for store/compare the MD5 info.

Pretty much: no.

This would require knowledge of the internal structure of the file types in question - I don't feel like figuring out how to separate coded audio data from metadata, because this would be quite a mess and quite some work in various cases (think data not starting/ending on byte boundaries; formats where header data is stored in a compressed/coded form; container formats)


However, generating / verifying a checksum of the decoded PCM data (FLAC fingerprint style) will definitely be added. Certainly a good feature for lossless audio (identification of data sources is independent from formats and compression settings that way), but of course it's useless for lossy file formats.

Sure, that's a great idea. But (for reasons mentioned in my post above) that's up to anyone who's bored enough to write file parsers for all formats (s)he wants to see supported.

because its good encryption.

2) circumstance: there is already an md5 file in the directory of the album; you highlight the album in foobar and hit 'create md5'; it says "md5 already exists. replace?" and has the option of not asking next time.

"aqscript," which examines .pun files that store both tag checksums and audio checksums, could be used as an example for the mp3 format. i suppose chris myden or someone must have the source code. (the tool is available @ *****). it really would be good to have this feature... examining audio data separate from tag data would be an indispensible feature.

for starters i suppose you could only support the most popular several formats... maybe just mp3 and lossless...others could be added later.

MOD.: no links to or names of sharing groups, thank you.

And what does encryption have to do with a plugin that's meant for identification and integrity verification purposes? Nah, that can't be the reason why he requested it.

mazy?


.. no. Like I said, it's an unreasonable amount of work - not specifically in the case of simple formats like mp3, but definitely when it comes to containers. Besides, what I have in mind is a plugin that is completely independent from files and file formats. Anyway, I'll keep your request in mind when designing the plugin so that adding support for what you request can be done easily - by someone else.

I don't know whether you'll ever find someone who's bored enough to do all that, but I know one thing that's for sure: I am not the one.

Yup, that's what I meant. Concerning 1; shouldn't be such a problem to make creating a new MD5 manually after changing the filename or tags part of my routine, thx for at least having looked at it .

about sha1 ... well, md5 could do just fine, as it is message digest and not only crc. i've made crc checker long time ago myself (here) and both md5 and sha1 have been requested quite a few times ... i did some research back then and found out that it wouldn't be that hard to add.

as i said, md5 could do just fine

yea, i guess i wasn't paying enough attention. i didn't mean "good encryption," i meant a good cryptographic algorithm.