Displaying 4 results from an estimated 4 matches for "bits_consumed".
2009 Jun 01
0
Bug in bitreader for short reads?
It seems that the bitstream reader is not working as it should
(verified in version 1.2.0 and 1.2.1).
The problem is as follows: if the data read by the read callback is
not a multiple of 4, the bit reader will end up in a very bad state,
where the bits_consumed field will grow without ever being reset to 0,
and that causes everything to fail.
This is not a case that's encountered very often, because in general
(like for example when reading from a file), the read callback will
return as many bytes as were asked for, which happens to be a multipl...
2009 Jun 04
0
Bug in bitreader for short reads?
...une 1, 2009, 10:16 AM
> It seems that the bitstream
> reader is not working as it should (verified in version
> 1.2.0 and 1.2.1).The problem is as follows: if the data
> read by the read callback is not a multiple of 4, the bit
> reader will end up in a very bad state, where the
> bits_consumed field will grow without ever being reset to 0,
> and that causes everything to fail.This is not a
> case that's encountered very often, because in general
> (like for example when reading from a file), the read
> callback will return as many bytes as were asked for, which
> happe...
2009 Jun 01
0
Bug in bitreader for short reads?
It seems that the bitstream reader is not working as it should
(verified in version 1.2.0 and 1.2.1).
The problem is as follows: if the data read by the read callback is
not a multiple of 4, the bit reader will end up in a very bad state,
where the bits_consumed field will grow without ever being reset to 0,
and that causes everything to fail.
This is not a case that's encountered very often, because in general
(like for example when reading from a file), the read callback will
return as many bytes as were asked for, which happens to be a multipl...
2009 Jun 04
0
Bug in bitreader for short reads?
...ay 31, 2009, 10:40 PM
> It seems that the bitstream
> reader is not working as it should (verified in version
> 1.2.0 and 1.2.1).The problem is as follows: if the data
> read by the read callback is not a multiple of 4, the bit
> reader will end up in a very bad state, where the
> bits_consumed field will grow without ever being reset to 0,
> and that causes everything to fail.This is not a
> case that's encountered very often, because in general
> (like for example when reading from a file), the read
> callback will return as many bytes as were asked for, which
> happe...