Hydrogenaudio Forums

Lossless Audio Compression => WavPack => Topic started by: Jurg98 on 13 April, 2004, 02:39:59 AM

Title: WavPack - Foobar issues
Post by: Jurg98 on 13 April, 2004, 02:39:59 AM
Hi!

Is there a history of Foobar 0.81 refusing to play WavPack 3.97 files? I've tried using the lossless compression, I've tried the hybrid compression, and I've tried about every switch available in WavPack, but Foo won't play the file (Error opening file). It plays everything else just fine though...

So, does Foobar support WavPack, or have I downloaded a buggy WavPack encoder? Or is it a problem with the newly released 0.81 version?

Thanks!
Title: WavPack - Foobar issues
Post by: Mr_Rabid_Teddybear on 13 April, 2004, 03:32:12 AM
Just compressed a standard 44/16 wav file with wavpack 3.97 using multi frontend with the -h switch. Plays back flawlessly in fb2k 0.8.1 here (XP sp1). You do have foo_wavpack.dll (http://www.foobar2000.org/foo_wavpack.zip), don't you?
Title: WavPack - Foobar issues
Post by: Garf on 13 April, 2004, 03:39:11 AM
WavPack support in the core was dropped some time ago, see post above for the solution.
Title: WavPack - Foobar issues
Post by: Jurg98 on 13 April, 2004, 04:06:40 AM
I have the full Foobar version, so that wasn't the problem... Anyway, found the solution in the mean time though... I use EAC to rip, and then call wavpack.exe from within EAC to do the encoding... You just have to tell EAC not to add an ID3 tag to the .wv file. Seems to screw up the file somehow... <g>

Thanks Garf! Thanks TeddyBear!
Title: WavPack - Foobar issues
Post by: NRAninja on 13 April, 2004, 04:32:55 AM
Use APEv2 tags with Wavpack. Learn how to set up EAC to add them here: http://jackcomics.lunarpages.com/eac/ (http://jackcomics.lunarpages.com/eac/)
Title: WavPack - Foobar issues
Post by: bryant on 13 April, 2004, 11:49:13 AM
And it's actually just ID3v2 tags that mess up WavPack files. ID3v1 is okay.
Title: WavPack - Foobar issues
Post by: Mr_Rabid_Teddybear on 13 April, 2004, 03:37:39 PM
Quote
And it's actually just ID3v2 tags that mess up WavPack files. ID3v1 is okay.

So I guess this means that you could actually tag a wavpack file with a combo of ape2 + id3v1(.1) ...?