Here is the official documentation on the verify (-v) option:



I am a fan of this process, because I don't want to go back to my files and find any issues, rare as this may be. But unless you are at the console watching this process run, you don’t know if it was verified successfully or if there was an error. FLAC will stop the encoding if a –V is run parallel to the encoding, so if you go back to your computer and there is no Flac file, you know to investigate. This is probably the biggest advantage Flac has over WavPack, hardware support notwithstanding. WavPack has been my lossless choice for a long time now, but I like to encode with REACT, like many of us here.

With REACT, I added a line to verify:
or
but the window closes unless you put a pause option. This won’t work for an encode of individual tracks, because each window would need a button to close out before it would move on. You would have to sit at the computer for the entire ripping/encoding process, defeating the purpose of automation.

It would be an awesome feature to have a parameter in the encode process to kill the encode if there was an error, but that would likely be a huge effort on David’s part. But maybe something involved with the way wvunpack.exe is run would help notify the user if there was a failure. It doesn’t look like the results can be put to stdout like the –S and –SS options, otherwise we could have a text file in the directory to check for results. Or maybe, some type of functionality to rename the file if there is a problem with the verify results. I suppose an AutoIT program can be set up to copy and paste the console window contents, but that would be somewhat frustrating as well.

Does anyone have any ideas on how to get your file verify results saved interactively?


Thanks!
Scott

why not just run wvunpack -v *.wv in the directory afterwards?

as it is a cli DECODER the functions you are asking for would need to be in place in the ENCODER. flac can do this as it does not have seperate executables for encoding and decoding.

how often do you have faulty wavpack encodes?


later

I petitioned David a while back to get wvunpack to return a non-zero value if verification failed. This allows me to do this in my REACT cfg (following the encode):