Can I have more information about how "-m" works? 2018-11-27 18:41:00 From http://www.wavpack.com/wavpack_doc.html we have:Quote-m = compute & store MD5 signature of raw audio dataCalculate and display the MD5 checksum of the uncompressed audio data and store it in the compressed file. These sums are commonly used in file trading communities to compare versions of tracks, and as such the sums generated by WavPack match those of FLAC, OptimFROG, Shntool, and get_id3(). They can also be used by WvUnpack during decompression to verify the data integrity of lossless files.I've decided to create a simple script (Linux/Unix only) to prove this but I'm having different md5 signatures. The script creates a wav on the fly using sox:Code: [Select]#!/usr/bin/env bashsox -c1 -n result.wav synth 00:00:02 whitenoisemd5sum result.wavwavpack -hh -m -t -v result.wavwvunpack -v result.wvwvunpack -o result_unpacked.wav result.wvmd5sum result_unpacked.wavrm -f result.wav result.wv result_unpacked.wavOutput:Quote29e36143187f0a616f27d337fc652e5c result.wav WAVPACK Hybrid Lossless Audio Compressor Version 5.1.0 Copyright (c) 1998 - 2017 David Bryant. All Rights Reserved.original md5 signature: cc1d6436f019d37dd3591a7733bcb5a4created (and verified) result.wv in 0.06 secs (lossless, -0.96%) WVUNPACK Hybrid Lossless Audio Decompressor Version 5.1.0 Copyright (c) 1998 - 2017 David Bryant. All Rights Reserved.verified result.wv in 0.02 secs (lossless, -0.98%) WVUNPACK Hybrid Lossless Audio Decompressor Version 5.1.0 Copyright (c) 1998 - 2017 David Bryant. All Rights Reserved.restored result_unpacked.wav in 0.02 secs (lossless, -0.98%)29e36143187f0a616f27d337fc652e5c result_unpacked.wavYou can see that the md5 from md5sum from the wav and the uncompressed wv are the same, but why do we have different md5 checksums from md5sum and "original md5 signature"? What am I missing here?