How to deal with wavpack errors? 2004-09-07 16:42:18 Hi,A few days after encoding my albums to wavpack, I used Speek's frontend to verify my files. I don't know what caused it, but at least one of my albums have corrupted songs (CRC errors found in 9 blocks). I only noticed errors in this specific album, so maybe something went wrong during encoding or tagging, I'm not sure.Anyway, i'd like to know if there's a better solution for error reporting than just wvunpack -v. You see, it is possible to batch test several files using speek's frontend, but since an error report isn't generated, is very difficult to properly identify all the files that contain errors. I could use the wvunpack -m option to display md5 checksum, but it'd be even harder to compare the original md5 against the decoded md5 (I didn't store them in the encoding process). Is it possible to make wvunpack -v generate a log file after the analysis is done? I'm also considering creating some PAR2 files for each album. What do you think the best settings are? Probably using the same block size wavpack uses?Thanks in advance.