Please -- someone who knows a lot more about .wav files and checksums and the like than I do -- is this a feasible idea?

It's feasible, but I'm not sure you could get IASCA to go along with it.

The problem is that checksums aren't secure. You know the old saying "locks only keep honest people out"? Checksums are even less secure than locks. Checksums are only useful for verifying file integrity, and only marginally useful at that. They assume that all the software wants to do is make sure the file is okay, and that the software performing the checking at both ends is trusted.

As soon as distrust enters into the equation, you need something more than a checksum. IASCA would have no way of verifying whether or not you modified the software to display a false checksum.

___________
Tony Fabris