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: [Question] About "--merge-blocks". (Read 5427 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[Question] About "--merge-blocks".

When I include the option "--merge-blocks" the following happens:
Quote
original md5: bfd5392eb5a146e806a13dc9622faf65       
verified md5: df25d44ee06b70bc222fc73e1e8e4d49       
MD5 signatures should match, but do not!

Is this normal? Or I shouldn't use "--merge-blocks"? I don't know...

Thank you! :)

[Question] About "--merge-blocks".

Reply #1 –
MD5 signatures of what? The decoded audio or the entire encoded WavPack files? If the latter, of course they differ because you have just instructed the encoder to alter its format.

[Question] About "--merge-blocks".

Reply #2 –
Code: [Select]
wavpack.exe -m --merge-blocks --blocksize=512 test.wav
wvunpack.exe -m -v test.wv

results in:

Code: [Select]
original md5:  00b0bff6862b518452b46ad994cbde11
unpacked md5:  00b0bff6862b518452b46ad994cbde11
verified test.wv in 1.04 secs (lossless, 27.38%)


Input file is 16 bit, stereo, 44.1kHz.

[Question] About "--merge-blocks".

Reply #3 –
Quote from: db1989 on
MD5 signatures of what?

MD5 signatures of the raw pcm data. That output is from WavPack program.

Quote from: lvqcl on
Code: [Select]
wavpack.exe -m --merge-blocks --blocksize=512 test.wav
wvunpack.exe -m -v test.wv

results in:

Code: [Select]
original md5:  00b0bff6862b518452b46ad994cbde11
unpacked md5:  00b0bff6862b518452b46ad994cbde11
verified test.wv in 1.04 secs (lossless, 27.38%)


Input file is 16 bit, stereo, 44.1kHz.

Strange, it doesn't work here. I always get incorrect MD5:
Quote
blueknight@bk:~/Desktop/Audio/01$ wavpack -m --merge-blocks --blocksize=512 01.wav

WAVPACK  Hybrid Lossless Audio Compressor  Linux Version 4.60.1
Copyright © 1998 - 2013 Conifer Software.  All Rights Reserved.

original md5 signature: bfd5392eb5a146e806a13dc9622faf65       
created 01.wv in 1.17 secs (lossless, 40.08%)       
blueknight@bk:~/Desktop/Audio/01$ wvunpack -m -v 01.wv

WVUNPACK  Hybrid Lossless Audio Decompressor  Linux Version 4.60.1
Copyright © 1998 - 2013 Conifer Software.  All Rights Reserved.

original md5:  bfd5392eb5a146e806a13dc9622faf65       
unpacked md5:  122c4c1e400fe8de0bbbb4a4cf89e5cc       
MD5 signatures should match, but do not!


I just want to know if "--merge-blocks" cannot be used that way or it is some kind of bug. I'm using the Linux version, if that matters (noticed your "wavpack.exe").

[Question] About "--merge-blocks".

Reply #4 –
Do you use 64-bit wavpack? Try 32-bit version.

Also you use old version (4.60.1). Maybe this bug was fixed in 4.70.0.

[Question] About "--merge-blocks".

Reply #5 –
Quote from: lvqcl on
Do you use 64-bit wavpack? Try 32-bit version.

Also you use old version (4.60.1). Maybe this bug was fixed in 4.70.0.

I will try to compile a 32-bit version...

I'm using the latest wavpack I built from source (got it from official website):
Quote
blueknight@bk:~/Desktop/Audio/01$ wavpack --version
wavpack 4.70.0
libwavpack 4.60.1


Maybe the libwavpack is old? Investigating...

EDIT: It seems I have the latest libwavpack here... If not, please let me know.

EDIT: It seems I had to disable shared when compiling, the shared library in my system is old... It is updated now:
Quote
blueknight@bk:~$ wavpack --version
wavpack 4.70.0
libwavpack 4.70.0


And now it works:
Quote
original md5:  bfd5392eb5a146e806a13dc9622faf65       
unpacked md5:  bfd5392eb5a146e806a13dc9622faf65       
verified 01.wv in 0.98 secs (lossless, 38.95%)

Simple fix, LOL...

Thanks for helping! SOLVED!