QUOTE(atici @ Oct 13 2005, 12:37 PM)
QUOTE(bryant @ Oct 13 2005, 12:02 PM)
The issue with 4.2 is exceedingly rare and can only occur when the -h and -x modes are used together.
I've been using 4.2 on 16 bit 44.1 kHz files. I thought this bug only affected files with larger resolution/frequency. Is there a way to verify if I am affected by this bug without reripping.
QUOTE(bryant @ Oct 13 2005, 12:02 PM)
I am finishing up 4.3 now, and that will be a full release with sources (including *nix).
Sweet. Would you briefly tell us what to expect in the new version?

It is much more likely to happen with 24-bit data that has been oversampled (i.e. DVD-audio). I tried to generate a file that would make it happen with 16-bit data and failed, but I am not willing to say it's impossible. Considering how much 16-bit data has gone through WavPack 4, it doesn't seem very likely.
However, just doing a -v verify with wvunpack will make sure your files are okay. And, like I said before, even if you do find a bad one, the new decoder will fix it.
In addition to the above fix, the enhancements for 4.3 are actually not too sexy. They include new options to run at low priority and discard extra RIFF chunks (a la FLAC), the metadata-from-file improvements from Synthetic Soul and Martin H, an error-handling change also suggested by Synthetic Soul, the integration of the "debug" mode into the standard version (by just renaming the .exe), some enhancements to the robustness of the playback code, a feature to make using the library to create WavPack files easier, and probably some little things I can't think of.
I wanted to put in the smart noise-shaping feature suggested by Shadowking (and I actually developed it) but then decided after some discussion with another HA member that breaking the decoder would be a bad idea. I will still be able to implement the noise-shaping change in the existing framework, but it will require more effort and I didn't want to delay this release any longer.