Page 1 of 1

[SOLVED] Big difference in size between XR's wavpack dll and official cli tool

Posted: Sat Jun 19, 2021 1:58 am
by 1024mb
I've tried compressing DSF files into WavPack and I've noticed a big difference in size between using XR's dll and the official cli tool. This is XR settings:

Image

And this is the file it outputs:

Image

Notice the compression ratio and modalities, now this is what I got when I use:

Code: Select all

wavpack -hh -m -t -v -x6
(I'm giving exactly what I'm using, I know -t, -v and -m have nothing to do with compression)

Image

The difference in size is 111.09 MB (XR) vs 88.56 MB (cli). Why is XR's dll not compressing with -hh when I've chosen Very high?
Also why the two files give two different source formats? Is this normal?

Re: Big difference in size between XR's wavpack dll and official cli tool

Posted: Sun Jun 20, 2021 9:34 am
by admin

Re: Big difference in size between XR's wavpack dll and official cli tool

Posted: Mon Jun 28, 2021 4:40 pm
by 1024mb
Sorry for the late reply. I've tried packing some DSF files to WavPack and it works well now but I've also tried re-packing one DSF WavPack to WavPack again using the DLL (of course) and the resulting WavPack's source format is WAV instead of DSF as the source WavPack file, is this supposed to happen?

DSF -> WAVPACK = source format: DSF

WAVPACK -> WAVPACK = source format: WAV

Re: Big difference in size between XR's wavpack dll and official cli tool

Posted: Tue Jun 29, 2021 6:54 am
by admin
This is nor supported, i.e. when WavPack is decoded, it's always converted to PCM, that's why you get source format: WAV.

[SOLVED] Re: Big difference in size between XR's wavpack dll and official cli tool

Posted: Tue Jun 29, 2021 7:33 am
by 1024mb
Oh, ok. Thanks. This problem is solved now.