Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: The BlockSize of WavPack (Read 5308 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

The BlockSize of WavPack

The acceptable blocksize of WavPack is from 1 to 131072 and I think most people would like to use the "default" blocksize.
But when I set the blocksize to very small value such as 1, I got a huge WaPpack file, the filesize is about 25 times of the original WAV file. Wavpack seems not to be an audio compressor but "inflator".
Personally, I think the minimium acceptable blocksize should be set to 256 or so, too small blocksize is meaningless.

 

The BlockSize of WavPack

Reply #1
The acceptable blocksize of WavPack is from 1 to 131072 and I think most people would like to use the "default" blocksize.
But when I set the blocksize to very small value such as 1, I got a huge WaPpack file, the filesize is about 25 times of the original WAV file. Wavpack seems not to be an audio compressor but "inflator".
Personally, I think the minimium acceptable blocksize should be set to 256 or so, too small blocksize is meaningless.

Yeah, you're right, very small block size are not useful in WavPack. However, with the new "merge-blocks" option, blocks down to about 32 samples make some sense. I may put a more reasonable lower limit on the range for that option, or I might have the code prevent the average blocksize from falling below a certain limit (this already exists for the --dns option).

Thanks for pointing this out. I don't want people generating these huge files (and they might not even play in some cases)...