I currently run all three WavPack binaries during encoding and am wondering if maybe the third one isn't needed, perhaps? Here is what I process for my encodes (in this order):

1. wavpack.exe (encode)
2. wvgain.exe (calculate and insert Replay Gain values in the tags)
3. wvunpack.exe -v (to verify integrity)

I guess this is probably the most complete and thorough way to ensure my Wavpack file(s) are in good shape, but I wonder if wvgain.exe will not complete successfully on a file that is (for some reason) corrupt. If so, technically, it is validating that the file can be read/decoded properly. If that is the case, I can save a few moments of encoding each time by eliminating the third step and my files should be fine as long as the wvgain.exe process finished without error.

Does anyone have any experience here?

Thanks,
Scott

Hi Scott!

I checked the code for wvgain and it will definitely return an error code if it encounters any error in decoding (including crc errors). In album mode it will terminate after the file with an error (and not write any ReplayGain info); otherwise it will process the rest of the files, but still return an error at the end of the batch.

In case you'd like to experiment with this, I am attaching a WavPack file that contains 4 errors that I use for my testing.

David

Excellent - I figured this may be the case. Thanks for checking and getting back to me so quickly!


This will be useful - I will try it out and save it for future testing as well.

Thanks for the help, David. You are always great to work with!

Scott