--------------------------
Update - September 1, 2005
--------------------------

wavpack.exe (command-line encoder) - 4.22
cool_wv4.flt (CoolEdit / Audition filter) - 2.5
-----------------------------------------------
fixed: possible corrupt files written (24 or 32-bit + "extra" mode)

Download wavpack-4.22

Cheers.

Nice to see the problem addressed so swiftly. Good work and thanks to Bryant and Kazuma for reporting.

edit: I think file should be renamed wavpack-4.22.zip as opposed to wavpack-4.2.zip

Thank You!

Have compression ratios or encoding/decoding speed been improved ?

That link is for WavPack 4.2... David has allready given the link for wavpack.exe 4.22 + CoolEdit / Audition filter on the thread where the problem where discussed, and he has said that if it works out fine for people he will update the binaries on the WavPack site...

Thread where issue is discussed :

http://www.hydrogenaudio.org/forums/index....showtopic=36535

-Martin.

No, it's just a fix for the specific issue Martin H mentioned.

The zip file says 4.2, but it's actually 4.22 that is in there. I just checked.

Sorry for the confusion on this! I did update the standard WavPack release files because I would like people to start using the new version ASAP. I didn't rename the .zip file because several outside sites link directly to the zip file and I want them to update too (I got almost 2800 downloads of wavpack.zip in August and I haven't used that name for years, but I keep it updated!)

Decoder hasn't changed i take it ? No need to update our CoreWavpack DShow decoder filters ?

Not yet. The actual overflow here did happen in the decoder (and that will be fixed next release) but I was able to prevent the "extra" mode from generating frames that would cause the error. When I release a new decoder an update would be nice, but it's certainly not a priority because offending files should be virtually non-existent.

BTW, thanks to you and Toff and the other Matroskers for all your continuing support. It was great to play these 5.1/24/96 WavPack test files in WMP!

hmm... Before i wrote that it was the wrong version i had first downloaded the package from the link, and then run wavpack.exe on the commandline to check the version number and it said v4.2 and the date was from 2005-04-02... I have just downloaded the package again and tested it again, and the same thing happens... But, anyways, David has confirmed it, so i apologise for my mistake...

-Martin.

You should probably empty all cache and such before redownloading. Firefox usually gives you old files if you don't empty cache and downloads first, and the same goes to other browsers AFAIK.

Thank you very much Mr_Rabid_Teddybear... I have just emptyed my cache in firefox, and tryed again, and this time it showed v4.22... Sorry everyone for posting wrong info...

-Martin.

Remind me to teach you about how to use Apache's mod_rewrite functions

I've found a (more or less) bug in wavpack if you use it with a non-standard command line window width.
After the encoding it keeps scrollig endlessly, it seems to output an infinite amount of eol's.

I always set my command line window to a very large width, because several command line utils make use of it.

It's probably 1min work to fix it

BTW: used v4.22.

Actually, I have heard about this a couple times, but have never been able to reproduce it. If I again fail to reproduce it, maybe you can help me track it down?

Weird, made my own build from the sources and no problem now ?

The build is also a bit faster (compiled with Intel 9) for my pc (Pentium4), I've should have done this earlier

Yeah, this is a weird problem. It's very similar to a problem that Josh found a long time ago that had to do (I think) with cygwin. That was fixed (and it was a bug in the screen handler somewhere), but obviously something is still going on. I tried again to reproduce it so I can fix it easily here, but still could not.

What size window exactly are you using (screen and window)? Is there anything else I should know about your setup (the other user said it was XP)?

Maybe I should just buy a newer compiler, but I love VC++ 6 so!!

Thanks...

I use WinXP SP1.

Screen Buffer Size - Width: 196
Screen Buffer Size - Height: 9999
Window Size - Width: 196
Window Size - Height: 92

I'm working at resolution 1600x1200.

BTW: you can try a tial version of Intel 9 it integrates perfectly with VC++.

If you would like it I could put an intel build at my website between the other builds of open source compressors.

http://studwww.ugent.be/~jdebock/win32_compressor_builds.htm

>Maybe I should just buy a newer compiler, but I love VC++ 6 so!!

Same here, waiting for VS 2005 (November?) with native 64 bit compiler before jumping ship.

Ahh, that does it!

Now I can reproduce the problem easily, but I can't read a thing. If a moth lands on my screen it eclipses a whole paragraph...

It'll be fixed for 4.3. Thanks again!

Hmm, sounds interesting. Maybe we can go in 50-50 on a copy!

Nice, thanks.