[XviD-devel] Different length reading sprite-trajectory

[Christoph Lampert]

Okay, if I'm not mistaken, it's XviD's fault, because 
leading bits 11111110=0xFE means len=10 (table B-33).

gruel

On Wed, 6 Aug 2003, Christoph Lampert wrote:
> there is a mismatch between FFmpeg and XviD when decoding length of
> sprite_trajectory.
> 
> >From the bitstream 
> 
> fe ef d2 c3
> 
> XviD reads (and writes):  length=9 x=-272  
> in mbcoding.c (bs_get_spritetrajectory())
> 
> whereas ffmpeg reads   :  length=10 x=959   (using get_vlc())
> in h263.c (mpeg4_decode_sprite_trajectory())
> 
> Can some guru check which is correct? The standard says
> just that it's unsigned integer, most significant bit first. 
> 
> gruel
> 
> 
> _______________________________________________
> XviD-devel mailing list
> XviD-devel at xvid.org
> http://list.xvid.org/mailman/listinfo/xvid-devel
> 
>