flac 1.3.0 pre-release Options

[romor]

Announced here: http://lists.xiph.org/pipermail/flac-dev/2...rch/003695.html

Git change log: https://git.xiph.org/?p=flac.git;a=summary

[lvqcl]

When ValidBitsPerSample=16: yes, FLAC just throws away these padding bytes. But when ValidBitsPerSample=17...24 then FLAC doesn't discard bits but simply shifts all input samples by (BitsPerSample - ValidBitsPerSample) bits and only then calculates MD5.

I don't think that such behavior is better than the simple (and straightforward) algorithm of WavPack, TAK and OFR.

This post has been edited by lvqcl: Mar 14 2013, 18:29

[ktf]

When ValidBitsPerSample=16: yes, FLAC just throws away these padding bytes. But when ValidBitsPerSample=17...24 then FLAC doesn't discard bits but simply shifts all input samples by (BitsPerSample - ValidBitsPerSample) bits and only then calculates MD5.

Ah, sorry, I misunderstood/misread. Raw data of course can't be 22-bits or something like that, so indeed, MD5sum should be the same for 17 through 24 bits, as they are all packed as 24bit in raw audio. However, I don't understand why WavPack, TAK and OptimFrog can have the same MD5 for 16 bit and 24 bit. It would be stupid to pack 16-bit audio in a 24-bit container, true, but still, it looks like they just ignore wValidBitsPerSample?

Other news: The FLAC git has seen some changes on 2GB file limits on Windows. I didn't full understand the mailing list conversation, but apparently the limit was raised to 4GB and this can't be fixed until 1.3.1. Not really sure though. https://git.xiph.org/?p=flac.git;a=commit;h...ad983e3ec7fdb4f

This post has been edited by ktf: Mar 14 2013, 20:59