Another shameless plug: caudec SVN (upcoming version 1.7.0) can compute hashes (MD5, CRC32, SHA1/256/512) independently from the decoded WAV file (raw PCM, actually) and store them as metadata (caudec -H). It will use those when checking file integrity (caudec -t), i.e. it will decode lossless files, compute the decoded WAV file's hash, and compare it to the one stored as metadata. If decoding fails (the decoder exits with a code that's not zero), or if the hashes don't match, caudec will report an error.
Since the hashing process is completely independent from all codecs, it should be immune to such bugs. I have to say, while the bug is clearly audible in this instance, it's making me a bit paranoid. It's what prompted me to use caudec's hashing facility when testing file integrity.
Since the hashing process is completely independent from all codecs, it should be immune to such bugs. I have to say, while the bug is clearly audible in this instance, it's making me a bit paranoid. It's what prompted me to use caudec's hashing facility when testing file integrity.