search for: rice2

...gnal as 32-bit signed int. And there > are the following comments in stream_encoder.c: The residual is stored as a Golomb/Rice code. As far as I know, that is not limited to 32-bit in the format itself, only in the implementation. However, there are two residual coding methods now: rice and rice2. rice2 was added when it turned out rice (with a 4 bit rice parameter) wasn't able to cope with the larger residuals that 24-bit material. It looks like a 5-bit rice parameter is enough for 32-bit material as well (highest divisor is 2^30, whereas a 4-bit parameter is limited to 2^14), but...

...it was fixed. It seems the encoding support >> was actually added later in 1.2.1, so there was a short time for >> adoption of the new decoder. It should be added to the changelog. > It's still a bit of a mystery to me what should be added. Clues? In short: FLAC 1.2.0 added the RICE2 residual coding method (http://flac.sourceforge.net/format.html#partitioned_rice2) to the format and the decoder, but this wasn't in the changelog. This breaks forward compatibility for 24-bit files RICE2 was added because when trying to encode a 24-bit file the residual wouldn't fit i...

Miroslav Lichvar wrote: > On Thu, May 02, 2013 at 09:31:25PM +0200, Martijn van Beurden wrote: > > I don't know why this isn't on the changelog, but it is probably still a > > good idea to add it. This only breaks compatibility for 24-bit streams. > > (So: decoders older than 1.2.0 might not be able to decode 24-bit FLAC > > files made by libFLAC 1.2.0 or

On 16/07/13 8:10 PM, Erik de Castro Lopo wrote: > Leigh Dyer wrote: > >> Certainly -- I've uploaded the analysis files for both the -6 and -7 >> encodes, in case you wanted to compare: >> >> http://wootangent.net/~lsd/blah/6.ana >> http://wootangent.net/~lsd/blah/7.ana >> >> The encode seems to proceed normally until 59% of the way through the

...somewhere in the process of transferring it as a WAVE-file. You might want to check this with the band that uploaded it to you. In any case, it looks like these damaged areas triggered some unwanted FLAC behaviour. You've exposed at least two very serious FLAC bugs, namely a malfunctioning RICE2-partition encoder and a bug concerning choosing verbatim frames over fixed/lpc frames. One last remark for anyone who didn't notice yet, this >4GB flac file consists mostly of zeros, zipping it reduces the file to 6.8MB. Looking at it with a hex-editor reveals this has to be an error wit...

...ks on the last pre-release when I tried test_streams.sh with FLAC 1.3.0 encoding and an older version (1.1.0 or something like that) decoding. This failed for 24-bit samples and I wondered why. After quite some tests and hex-editors, I found out this is because older decoders do not support the RICE2 partition. This was added with FLAC 1.2.0, but it's not in the changelog. I found this e-mail on the list which I think is related: http://lists.xiph.org/pipermail/flac-dev/2007-April/002179.html It looks like RICE2 was implemented in the decoder just before the release of 1.2.0. (See htt...

Martijn van Beurden wrote: > You've exposed at least two very serious FLAC bugs, > namely a malfunctioning RICE2-partition encoder and a bug concerning > choosing verbatim frames over fixed/lpc frames. The second, not choosing verbatim frames over fixed/lpc frames is almost certainly a direct result of the first problem. The fix was changing one local variable from FLAC_uint32 to FLAC_uint64 in function...

Hi all, I just noticed this: https://sourceforge.net/p/flac/feature-requests/91/ a request for support of 32 bit audio data. The request has been around since 2008. Had two inial impressions: * Would adding this break brackwards compatibility too badly? Obviously decoding of 32 bit encoded data would not work with older versions of flac. * This is nuts. 24 bits has a dynamic range of

...o Lopo: > Had two inial impressions: > > * Would adding this break brackwards compatibility too badly? Obviously > decoding of 32 bit encoded data would not work with older versions of > flac. Probably not. I know that Josh at some point added a second residual coding method (rice2) to support 24-bit, but that only broke backward compatibility for 24-bit files back then. > * This is nuts. 24 bits has a dynamic range of ~140dB which is roughly > the difference between a quiet whisper in a quiet room, to the sound > of a jet engine at 10 meters. Surely that is...