WavPack 4.40 released
Reply #25 – 2006-12-13 00:16:38
However, with this release, I would recommend using either -x or -hx. They improve the compression over the default about 0.5% (with no decode penalty) and 1.25% (with 1/2 the decode penalty of -hh), respectively. The -x about doubles the encode time, but it's still faster than most rippers. My top goals for this release were to greatly reduce the use of -hh and greatly increase the use of -x (that's why you see what you see in the "short" help version). I used -hm in the last version before 4.40 and that was equal to the new -hh. The -x is asymmetric favoring decode time over encode. Compared to LAME encode times, WavPack only encodes for several seconds on my machine anyway even with the -hh equivalent. It flat out flies compared to LAME, but then LAME is shrinking my files to ~15% of their original size even at very high quality VBR. So it looks like -hxm would get me the most bang for the buck compression/decompression wise and with a md5 checksum. Thanx David. This program is amazing and after I did some research early this year, I decided WavPack was the best lossless codec for me. I don't even bother ripping CDs with lossy anymore except when compiling mp3 CDs for the car. Then I just transcode the .wv files. Here's my cmd line for EAC/WavPack v4.40. Please point out any errors.-w "Artist=%a" -w "Title=%t" -w "Album=%g" -w "Year=%y" -w "Track=%n" -w "Genre=%m" -hxm %s %d What does %s %d do BTW?