QUOTE (zgx @ Mar 5 2007, 02:31)

- Problem 1: compression ratio
The thing is that the original .wav was 4.351.430.444 bytes and the wavpack file I got was 4.312.098.510 bytes. So hardly any compression at all.
If I make the wave-file smaller I can encode it with FLAC. But I do know that it does not have "WAVE_FORMAT_EXTENSIBLE". I got the .wav by converting a .raw file with sox (sox -r48000 -t .raw -c 6 -w -s test.raw z:\test.wav).
- Problem 2: Playback
The file does play in zoomplayer with a DS filter. But zoomplayer tells me the file is only one and a half minute long but it should be close to two hours.
When I encoded the file it quickly went to 99% after just a few seconds and like a hundred MB then it continued to encode for quite some time until I got a 4GB file and then it went from 99% to 100%.
Something is very wrong here.
The WAV format can only handle up to 4 gig and your file is slightly over that. What I think is happening is that sox is creating a WAV header with size fields that overflow (because they're 32-bit). This makes it look like a very short WAV with a bunch of stuff afterward. WavPack encodes the audio, then stores the rest uncompressed because it doesn't know it's audio. That would explain all your symptoms.
I think it might work if you added the -i option to your command line. This will cause WavPack to ignore the sizes in the WAV header and encode anyway (the WavPack format itself has a much higher length limit). You might get an error at the end when it tries to generate a WAV header, but I doubt that error would be fatal.
The resulting file will
not be unpackable into a valid WAV (because a WAV file can't be that long) but should be playable (assuming the players don't have similar overflows).
I am planning an extension to WavPack to be able to read and write at least one of the new 64-bit WAV variants or raw files, both of which would fix this problem.
BTW, you might want to take off the -x while you're still trying to get it to work. You can always experiment with that once everything is actually working.

Hope this helps...
David