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

WavPack 4.1 released

WavPack version 4.1 is released. It includes some fixes and some added features based mostly on HA user's input. There is also (finally) a real change log. The Linux version has been updated with the new sources, but I have not compiled it.

WavPack website
changelog for 4.1

Thanks to everyone who helped in the development with testing or suggestions... 

WavPack 4.1 released

Reply #1 –
Great to see the new version online. I hope this version fixes all the previous bugs. I've been waiting for this to encode my albums.
Again, I want to thank you for your dedication and effort, bryant. Your work is really appreciated.

WavPack 4.1 released

Reply #2 –
Thanks bryant for this new release. New versions of my favorite tools are always welcome. 

WavPack 4.1 released

Reply #3 –
Thanks you Bryant for improving this very awesome program.

WavPack 4.1 released

Reply #4 –
Cool.  Thanks for the update.

Looks like there's one small problem compiling this on Linux.

In wavpack.c, line 567, MAX_PATH should be changed to PATH_MAX.

WavPack 4.1 released

Reply #5 –
thx for the updates bryant
Allegari nihil et allegatum non probare, paria sunt.

WavPack 4.1 released

Reply #8 –
Fantastic!  Thanks, bryant!

WavPack 4.1 released

Reply #9 –
It's nice that the foobar plugin now shows all the extra info.  But where it says "version" it only shows 4 even with 4.1.  Not sure if thats intentional so I figured I'd point it out.  I like seeing the md5 in the info though.

WavPack 4.1 released

Reply #10 –
Quote
bryant, for v4.0 there is:

http://www.wavpack.com/wavpack-4.0.tar.gz

Would it be possible to put:

http://www.wavpack.com/wavpack-4.1.tar.gz  ?

Thanks 
[a href="index.php?act=findpost&pid=241996"][{POST_SNAPBACK}][/a]
Actually, it was wavpack4.0-tar.bz2, and I tried for about 20 minutes to create the 4.1 equivalent using 7-Zip. After getting "You Can't Do That!!" popups about 8 times I said "S***w it! They're getting a .zip!". 

If any kind soul would be willing to take the .zip and make this for me (with Kuniko's change too, and maybe the one on line 116 also to be consistent) I would be internally grateful... 

Quote
It's nice that the foobar plugin now shows all the extra info. But where it says "version" it only shows 4 even with 4.1. Not sure if thats intentional so I figured I'd point it out. I like seeing the md5 in the info though.
Yes, that's intentional. The pre-4.0 versions did not store enough version information to be more specific than that (3.0 can generate the exact same file as 3.98b), so I figured I'd keep it clean.

Thanks, guys! 

WavPack 4.1 released

Reply #11 –
Hi Bryant,

Ah yes, it was .bz2 -- my mistake.

Here, I made the .tar.bz2 file for you.  I wrapped it inside abc.zip to be able to upload 

If possible, can you upload it with the same convention as 4.0 ? The official gentoo ebuild would expect it to be at http://www.wavpack.com/wavpack-4.1.tar.bz2 ).  Thanks for this new version !

PS:  While I was editing wavpack.c (see kuniklo's post) I noticed a few unchecked malloc()'s   
Only modification I made, was to replace that instance of MAX_PATH to PATH_MAX.

WavPack 4.1 released

Reply #12 –
Quote
Here, I made the .tar.bz2 file for you.  I wrapped it inside abc.zip to be able to upload  

If possible, can you upload it with the same convention as 4.0 ? The official gentoo ebuild would expect it to be at http://www.wavpack.com/wavpack-4.1.tar.bz2 ).
[a href="index.php?act=findpost&pid=242206"][{POST_SNAPBACK}][/a]

Okay, I uploaded the file and also updated my page to point to it instead. Thanks NumLOCK and Kuniklo!

Quote
PS:  While I was editing wavpack.c (see kuniklo's post) I noticed a few unchecked malloc()'s   

Yes, I admit I'm a little lazy about that, and I know it's bad form. However, I don't think it's nearly as important to check as it used to be. Back in the DOS days, you could quite easily run out of memory (like if someone ran too many TSRs) and you could actually do damage by writing to NULL pointers.

In these days of virtual memory management, a NULL return from malloc() probably means that your program (or the OS) has already crashed, and displaying some [probably incorrect] message about "out of memory" is probably less helpful than just using the NULL pointer and generating a GPF.

Hmm. I think I can rationalize just about anything! 

WavPack 4.1 released

Reply #13 –
If any Linux user doesn't feel like compiling, here are the binaries. They are verified to work correctly on Slackware 10 and Mandrake 10, so I think they will work on any modern Linux distribution.

WavPack 4.1 binaries

WavPack 4.1 released

Reply #14 –
Quote
If any Linux user doesn't feel like compiling, here are the binaries. They are verified to work correctly on Slackware 10 and Mandrake 10, so I think they will work on any modern Linux distribution.


Also works onFedora Core 2. Thanks bryant and Speek!
Any word on an XMMS plugin?
--
Eric

WavPack 4.1 released

Reply #15 –
Quote
Any word on an XMMS plugin?
[a href="index.php?act=findpost&pid=242269"][{POST_SNAPBACK}][/a]

XMMS definetaly needs a plugin.  I know there is a way to write a script to play the files, but a proper plugin would be great.  I think if wavpack had libs like flac does there'd be one by now, but i'm not terribly linux educated, I just use it for lopster.

WavPack 4.1 released

Reply #16 –
Quote
I think if wavpack had libs like flac does
[a href="index.php?act=findpost&pid=242273"][{POST_SNAPBACK}][/a]


wavpack has libs

WavPack 4.1 released

Reply #17 –
Quote
Quote
I think if wavpack had libs like flac does
[a href="index.php?act=findpost&pid=242273"][{POST_SNAPBACK}][/a]


wavpack has libs
[a href="index.php?act=findpost&pid=242278"][{POST_SNAPBACK}][/a]

So there is something like libwavpack?  If there is such a thing i'd like to know where to get it.  For example, to compile lopster with support for reading Flac file bitrates/track times it requires you have libflac.  To compile lopster to read wavpack file bitrates and such you pretty much have to stick part of the decoder code into it rather than just referencing the libs that don't seem to exist.  But if there are libs life would be easier

WavPack 4.1 released

Reply #19 –
Quote
[/url]                     --------------------------------
                     Release 4.1 - September 14, 2004
                     --------------------------------
...

wvunpack.exe (command-line decoder) - 4.1
-----------------------------------------
  fixed: hybrid mode decoding bugs (very obscure situations)
  added: -s option to dump file summary to stdout
  added: -t option to preserve timestamps
  added: error summary for batch mode

...


Great, you have respected a  forum user's wish!  - So cool...!

I already have made a short test with a hybrid wavpack file, deleting its wvc/correction file before:

Code: [Select]
X:\>wvunpack -s "Tom Petty & The Heartbreakers - Into The Great Wide Open (1991) - 01 - Learning To Fly.wv"

 WVUNPACK  Hybrid Lossless Wavefile Decompressor  Win32 Version 4.1  14-9-04
 Copyright (c) 1998 - 2004 Conifer Software.  All Rights Reserved.


file name:         Tom Petty & The Heartbreakers - Into The Great Wide Open (1991) - 01 - Learning To Fly.wv
file size:         15177424 bytes
source:            16-bit ints at 44100 Hz
channels:          2 (stereo)
duration:          0:04:1.86
modalities:        hybrid lossy, high
compression:       64.43%
ave bitrate:       502 kbps
encoder version:   4
original md5:      c1e355c04430d7300875894798bf0ecd


Thanks again!

WavPack 4.1 released

Reply #20 –
I'm trying to use Wavpack 4.1 with foobar and foo_clienc, and from some reason i always get at the end of the encoding "ERROR (foo_clienc) : Encoding failed"

Commandline used "-h - %d", when i tried to use a temp file instead of piping it works.

Ideas?
You can fool some of the people all of the time, and all of the people some of the time, but you can not fool all of the people all of the time.

- Abraham Lincoln

WavPack 4.1 released

Reply #21 –
Quote
I'm trying to use Wavpack 4.1 with foobar and foo_clienc, and from some reason i always get at the end of the encoding "ERROR (foo_clienc) : Encoding failed"

Commandline used "-h - %d", when i tried to use a temp file instead of piping it works.

Ideas?
[a href="index.php?act=findpost&pid=242324"][{POST_SNAPBACK}][/a]

You don't mention if you are encoding directly (from line-in) or transcoding from other files. If transcoding, you have to make sure the "encoder requires accurate length" box is checked and everything should work fine.

If you are recording directly then there is a problem because the length cannot be known in advance. There are two solutions, one of which is using the intermediate file (like you tried).

There's another solution that I just tried and it works great. Use foo_nero and set it up to use the Nero plugin for WavPack. Obviously you have to have some subset of Nero installed plus the new WavPack Nero plugin. The disadvantage of this is that there's no configuration for the Nero WavPack plugin so you only can get the default lossless mode.

I have been thinking about having a WavPack option to not require the accurate length. The problem with that is that if the resulting WavPack file is unpacked to .wav it will still have incorrect length in the RIFF header because WavPack (unlike FLAC) stores the RIFF header in the WavPack file instead of generating a new one on decode.

Hope this helps... 

WavPack 4.1 released

Reply #22 –
Quote
Quote
I'm trying to use Wavpack 4.1 with foobar and foo_clienc, and from some reason i always get at the end of the encoding "ERROR (foo_clienc) : Encoding failed"

Commandline used "-h - %d", when i tried to use a temp file instead of piping it works.

Ideas?
[a href="index.php?act=findpost&pid=242324"][{POST_SNAPBACK}][/a]

You don't mention if you are encoding directly (from line-in) or transcoding from other files. If transcoding, you have to make sure the "encoder requires accurate length" box is checked and everything should work fine.



I didn't mention two important things indeed:

1. "encoder requires accurate length" WAS checked
2. The source track was originally an MP3

I've just tested with other sources (For instance lossless) and it works. However as you already mentioned there some cases Wavpack can't handle 

Quote
If you are recording directly then there is a problem because the length cannot be known in advance. There are two solutions, one of which is using the intermediate file (like you tried).

...

I have been thinking about having a WavPack option to not require the accurate length. The problem with that is that if the resulting WavPack file is unpacked to .wav it will still have incorrect length in the RIFF header because WavPack (unlike FLAC) stores the RIFF header in the WavPack file instead of generating a new one on decode.

Hope this helps... 
[a href="index.php?act=findpost&pid=242470"][{POST_SNAPBACK}][/a]


Well, when encoding with other lossless formats like flac/ape there isn't such a problem, and imho if this limits Wavpack to this extent, this behaviour should be changed.
You can fool some of the people all of the time, and all of the people some of the time, but you can not fool all of the people all of the time.

- Abraham Lincoln

WavPack 4.1 released

Reply #23 –
flac solves this by making a quick second pass after encoding to fix the wave chunk sizes when the output is seekable.

this is one of the drawbacks of making a full wave file compressor instead of a generic audio compressor.  if wavpack gets traction on the mac you'll have to go through this all again with aiff, because aiff is ubiquitous there and just close enough to wave that people expect it to work, and just different enough to make it a pain.  however you are storing the riff headers hopefully can be tweaked enough to support aiff without another format change.

Josh

edit: PS if you ever want to see the fixup/aiff code, it's in flac's src/flac/decode.c, maybe there will be something there you can use.

WavPack 4.1 released

Reply #24 –
Respecting the depth of the thread my request must seem very insignificant...

...but is there any own icon/symbol for wavpack files?


Actually the standard Winamp icon is used at me for wavpack files too. I would like to distinguish file types at first sight and till now i associate that Winamp icon with Mp3.
But there is a 'slight' difference between wavpack and Mp3