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 4.3 released (Read 48169 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

WavPack 4.3 released

David Bryant released today WavPack 4.3

WavPack is a high quality, efficient and featureful lossless/lossy/hybrid compressor. It is available for free, including source code released under a very liberal license.

Changelog is available in next post.

Obtain the Win32 binaries and plugins at WavPack's official site:
http://www.wavpack.com/
And compiles for several *nix platforms at RareWares:
http://www.rarewares.org/lossless.html

WavPack 4.3 released

Reply #1 –
WavPack release 4.3 changelog:


wavpack.exe (command-line encoder) - 4.3
----------------------------------------
  fixed: bug causing termination error with very wide screen widths
  added: command-line option (-l) to use low priority for batch operation
  added: command-line option (-r) to generate a fresh RIFF header
  added: debug mode (rename to wavpack_debug.exe)
  added: automatically detect lower resolution data even without -x1
  added: src and dst dirs are searched also for tag source files (handy for EAC)
  added: wildcard accepted for tag source files (handy for EAC)
  added: handle non-standard sampling rates
  improved: returns error status for any error
  improved: use longer blocks in multichannel files (better "high" compression)

wvunpack.exe (command-line decoder) - 4.3
-----------------------------------------
  fixed: very rare decoding bug causing overflow with hi-res files
  fixed: bug causing termination error with very wide screen widths
  fixed: formatting error in duration display
  added: command-line option (-ss) to include tags in summary dump
  added: command-line option (-l) to use low priority for batch operation
  added: debug mode (rename to wvunpack_debug.exe)
  improved: returns error status for any error
  improved: more robust decoding of damaged (or invalid) files

in_wv.dll (winamp plugin) - 2.3
nxWavPack.dll (Nero plugin) - 1.2
WavPack_Apollo.dll (Apollo plugin) - 1.3
cool_wv4.flt (CoolEdit / Audition filter) - 2.6
-----------------------------------------------
  fixed: very rare decoding bug causing overflow with hi-res files
  improved: handle ID3v1.1 tags (now includes track number)
  improved: more robust decoding of damaged (or invalid) files
  added: handle non-standard sampling rates

foo_wavpack.dll (foobar plugin) - 2.3
-----------------------------------------------
  fixed: any error during WavPack file open caused crash if wvc file present
  fixed: very rare decoding bug causing overflow with hi-res files
  improved: more robust decoding of damaged (or invalid) files
  added: handle non-standard sampling rates

WavPack Library Source Code - 4.3
---------------------------------
  fixed: very rare decoding bug causing overflow with hi-res files
  added: automatic generation of RIFF wav header during encoding
  added: new functions to access tags by index (instead of item name)
  added: automatically detect lower resolution data during encoding
  added: handle non-standard sampling rates
  improved: more robust decoding of damaged (or invalid) files
  improved: use longer blocks in multichannel files (better "high" compression)
  improved: two structures renamed to avoid namespace conflict
  removed: legacy code for Borland compiler

WavPack 4.3 released

Reply #2 –
WELCOME to the new baby, and a great THANK-YOU to David! (Yes, to you too, Roberto!  )

Sergio
Sergio
M-Audio Delta AP + Revox B150 + (JBL 4301B | Sennheiser Amperior | Sennheiser HD598)

WavPack 4.3 released

Reply #3 –
Thanks, Roberto. 

BTW, another important item not in the changelog is the new plugin for Steinberg's WaveLab 5 that's available. Anyone who got the first one should grab the latest updated beta:

http://wavpack.gl.tter.org/

WavPack 4.3 released

Reply #4 –
Thank you David !

WavPack 4.3 released

Reply #5 –
Muchas gracias, David!

Quote
added: wildcard accepted for tag source files (handy for EAC)


Now all we need is for Andre to fix the file-extension error in EAC, and voila!, single step rip/compression/cue-embedding!

EDIT: added "rip".
we was young an' full of beans

WavPack 4.3 released

Reply #6 –
Thank You David.

That -l switch will shure come in handy for archiving the mixes of our show here.

WavPack 4.3 released

Reply #7 –
Thanks a lot! There's still the filename bug though, where a file with special chars in its name is "not found":
Code: [Select]
$ wvunpack "00 - [untitled].wv"

 WVUNPACK  Hybrid Lossless Wavefile Decompressor  Linux Version 4.3  2005-11-01
 Copyright (c) 1998 - 2005 Conifer Software.  All Rights Reserved.

file 00 - [untitled].wv not found!


On another topic, the detection of oversampled content works beautifully. I tested the stereo mix of the R.E.M. - In Time DVD-Audio with wavpack -hm; version 4.2 produced 2.659 GiB worth of data, versus 1.846 GiB for v4.3, for the same encoding time :-)

WavPack 4.3 released

Reply #8 –
Quote
Now all we need is for Andre to fix the file-extension error in EAC, and voila!, single step rip/compression/cue-embedding!

The file extension issue doesn't stop you doing any of these.

I don't think foobar pays any attention to the FILE command in an embedded cuesheet.
I'm on a horse.

WavPack 4.3 released

Reply #9 –
thanks alot for your great work.

WavPack 4.3 released

Reply #10 –
Great work bryant! Much appreciated.
Quote
I also have not implemented shadowking's noise-shaping improvement because I wanted to do it in a backward compatible way (which was more work). But it's scheduled.
[snip]
However, I believe that the existing -x mode could be overhauled in a way that would give a significant improvement to compression of real music without the huge speed penalty that exists now. Well see... 
[a href="index.php?act=findpost&pid=337447"][{POST_SNAPBACK}][/a]

Is this next for 4.4?
The object of mankind lies in its highest individuals.
One must have chaos in oneself to be able to give birth to a dancing star.

WavPack 4.3 released

Reply #11 –
Great work!  Hope WavPack keeps getting better and better. 

WavPack 4.3 released

Reply #12 –
An early Xmas present. Thank you!

WavPack 4.3 released

Reply #13 –
Quote
Quote
Now all we need is for Andre to fix the file-extension error in EAC, and voila!, single step rip/compression/cue-embedding!

The file extension issue doesn't stop you doing any of these.

I don't think foobar pays any attention to the FILE command in an embedded cuesheet.
[a href="index.php?act=findpost&pid=339974"][{POST_SNAPBACK}][/a]

You're right Synthetic Soul, it does work, Muchas gracias!
I had tried it with an already ripped and renamed WAV and it worked, but I thought that going straight from rip to encode to embed wouldn't work because of the extra extension.
we was young an' full of beans

WavPack 4.3 released

Reply #14 –
Haha, just a day after I finished archiving my dvd-a rips with 4.2 =)

I'll give it a run and see how it will handle them compared to 4.2.

WavPack 4.3 released

Reply #15 –
Quote
Haha, just a day after I finished archiving my dvd-a rips with 4.2 =)

What a timing

WavPack 4.3 released

Reply #16 –
OK, I reconverted one of them, and went from 4678 kbps (4.2) to 4671 kbps (4.3). Using the same settings (lossless, high).

Am I missing some kind of special switch used specifically for hires audio here?

WavPack 4.3 released

Reply #17 –
I use -hx6 for MAXIMUM compression of DVD-Audio.  I don't care how long it takes to encode, and it plays back as fast as -h that I can tell.

WavPack 4.3 released

Reply #18 –
Quote
I use -hx6 for MAXIMUM compression of DVD-Audio.  I don't care how long it takes to encode, and it plays back as fast as -h that I can tell.
Extra modes should actually be slightly faster (decoding) than -h.

WavPack 4.3 released

Reply #19 –
Interesting. I guess thats what I get for using a frontend and not checking properly the documentation. I'll try to redo it with -hx6 and see if there are any big differences.

WavPack 4.3 released

Reply #20 –
Quote
added: src and dst dirs are searched also for tag source files (handy for EAC)
added: wildcard accepted for tag source files (handy for EAC)

Could anyone explain what are these new features for and how do they work?

WavPack 4.3 released

Reply #21 –
Quote
added: src and dst dirs are searched also for tag source files (handy for EAC)
If you specify "-w CUESHEET=@cdimage.wv.cue" WAVPACK will look for cdimage.wv.cue in three folders (in addition to the folders in PATH):
  • The folder in which WAVPACK resides
  • The folder in which the source WAVE resides
  • The folder in which the WV file is to be created
Edit: obviously if you are using STDIN or STDOUT then only two folders are valid.
Quote
added: wildcard accepted for tag source files (handy for EAC)
Wildcards can be used like "-w CUESHEET=@*.cue".  This will only work if there is one .cue file in the folder.  It is useful when the cuesheet name changes per image, but you don't want to have to change your command line every time you rip.

I rip to a "clean" directory from EAC, so it is useful to me.

By using "-w CUESHEET=@*.cue" WAVPACK will first check the folder in which WAVPACK.EXE resides for a cuesheet.  When unsuccessful it will check the directory in which the temporary WAVE file resides - where it should successfully find the cuesheet EAC just created.
I'm on a horse.

WavPack 4.3 released

Reply #22 –
Quote
Interesting. I guess thats what I get for using a frontend and not checking properly the documentation. I'll try to redo it with -hx6 and see if there are any big differences.
[a href="index.php?act=findpost&pid=340237"][{POST_SNAPBACK}][/a]

May I suggest using -hx only. I have encoded few albums with -hx and -hx6 and there was only 1-2 kbps difference in bitrate but the encoding time difference was like 3x or something.
EDIT: With albums, I mean normal audio CD's.

WavPack 4.3 released

Reply #23 –
Quote
Interesting. I guess thats what I get for using a frontend and not checking properly the documentation. I'll try to redo it with -hx6 and see if there are any big differences.[a href="index.php?act=findpost&pid=340237"][{POST_SNAPBACK}][/a]


Honestly, I believe hx6 is madness. It takes ages to encode and won't do much better than, say, hx2 - that is several times faster.

WavPack 4.3 released

Reply #24 –
Quote
Quote
Interesting. I guess thats what I get for using a frontend and not checking properly the documentation. I'll try to redo it with -hx6 and see if there are any big differences.[a href="index.php?act=findpost&pid=340237"][{POST_SNAPBACK}][/a]


Honestly, I believe hx6 is madness. It takes ages to encode and won't do much better than, say, hx2 - that is several times faster.
[a href="index.php?act=findpost&pid=340334"][{POST_SNAPBACK}][/a]

I agree.  I've always used -hx2m for encoding any audio.  It's encoding speed is speed comperable to flac and compresses a good bit better in some cases. x6 is way too slow.  Generally if it takes longer than the length of the track I would consider it too slow unless it really made difference.  Glad to see 4.3 released, been busy re-ripping some stuff I ripped wrong using wavpack.  Looking forward to any improvements in speed and compression in 4.4.