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: WavPack 3.95 (Read 6453 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

WavPack 3.95

http://www.wavpack.com/
WavPack 3.95
Hybrid Lossless Audio Compression

5/7/2002: A great new Windows frontend has been created for WavPack. Now there's no need to remember all the WavPack options because all the major modes and features are directly visible, plus there's better support for filenames with international characters. WavPack 3.95 is required for this new frontend, and it has a couple of new features as well. It can now do batch processing from a list file in cases where wildcards aren't applicable, and WvUnpack can restore directly to stdout for use with certain encoders that don't require an intermediate wav file. Finally, some problems were fixed that caused 3.94 to run slowly sometimes.
Juha Laaksonheimo


WavPack 3.95

Reply #2
has anybody used it yet??

WavPack 3.95

Reply #3
Quote
Originally posted by iwod
has anybody used it yet??
Yes, I did. It works

WavPack 3.95

Reply #4
for a 4 min of pop music... how big is the hypid file and the correction file??

WavPack 3.95

Reply #5
Its has a interesting hybrid mode(lossy)...
Can anyone tell me about the quality of that(at 320), compared to Lame, at the same bitrate?
The compression speed is very good.
WavPack can go over 320(lossy)...Any advantage?

LIF
"Jazz washes away the dust of everyday life" (Art Blakey)

WavPack 3.95

Reply #6
Quote
Originally posted by iwod
for a 4 min of pop music... how big is the hypid file and the correction file??

The size of the lossy file plus the size of the correction file are just 1 or 2 percent larger than the size of a pure lossless file. So, if a pop track gets typically 40% lossless compression then that means that an original 40 meg wav file would be 24 meg lossless. In the hybrid mode (at 320 kbps) the lossy file would be about 9 meg and the correction file would be about 16 meg. For quieter music (like classical or acoustic jazz) the lossy and correction files tend to be closer to the same size.

Quote
Can anyone tell me about the quality of that(at 320), compared to Lame, at the same bitrate? 
Its much faster. 
WavPack can go over 320...Any advantage?

I have done some testing with the EAQUAL program and listening and think that the quality of the hybrid mode at 320 kbps is about the same as Lame at 192 kbps. The quality of the hybrid mode drops pretty quickly below 320 kbps, but I would guess that at 265 it’s still about the same as Lame at 128.

However, it is somewhat difficult to compare the quality to Lame or other high complexity encoders because the artifacts are very different. WavPack’s hybrid mode has absolutely no time smearing and always has ruler flat frequency response. The only possible artifact is added quantization noise (which is modulated by the signal) and I find this to be less irritating (when audible) than most other artifacts.

Going over 320 kbps does improve the quality (384 tests almost perfect in EAQUAL). If you use the “-n” option you can see that the noise added drops about 1 dB for every 15 kbps and that continues all the way up to lossless. So, while there’s no doubt that the result is proportionally closer to the original, at some point the benefit becomes only psychological.

BTW, I posted this over on r3mix also. Feel free to post again if you have more questions...