Topic: MD5 for FLACs

[blu666z]

why not just use the verify feature?

ie.  I get original FLACs from a taper.  I decode one track to wav, do some kind of editing and reFLAC it. I send you changed track.  You do your verify and it checks out ok, but its not the same as what the original taper put out. 

I just really need to figure out what my problem is with ther verifier I wrote. 

-Kevin

[greenone]

Why not use shntool md5's? They just take the md5 of the WAVE *data* (not the .wav files) contained within your shn/flac/ape/whatever.

http://forums.etree.org/viewtopic.php?t=1948

[dnsacks]

but what does that solve -- the thread you posted indicates this is pretty much the same as a flac fingerprint.

[greenone]

Aren't they easier to verify than ffp's? Hmm. You might be right.

[macdaddy]

ffp and shntool md5 are the same things...

that is why if you eyeball it to compare - the ffp included from the taper, and the shntool md5 of the wav you created. if the match, you are in business...

all i was saying that as a quick, one-touch way to verify if a disc has been burned 100% accurately, md5s are handy. ditto for a one-touch way to verify is a download fineished successfully.

but in a seed, i always include the shntool len output, the WAV shntool md5s, and the ffp. the latter two should match exactly.

but before i even read a txt file, i would double-click on an md5 in the top directory of a bit torrent download in order to verify that i received all information from a download...

but ffp/wav shntool md5 is the way to go to verify data integrity with finality.the uses are not mutually exclusive.