[XviD-devel] divx5, bframes and non-coded vops

peter ross xvid-devel@xvid.org
Thu, 03 Oct 2002 08:44:10 +1000


>ive patched xvidcore to give improve compatbility with the divx5
>decoder. the bug where-by p-vops with [pb]-frames bug are decoder
>immediality still exissts.

^^ i really need to get a new keyboard.

to clarify, the divx5.02 decoder handles multiple bframe sequences
correcly; PBB PBBB, etc.

xvid correctly writes-outs the startcodes. and as michaeln said, the
mpeg-4 standard (vlc and headers) ensures the start_code sequence
does not appear within the texture/mv/header bitstream.

>* divx5 does not to detect the b-vop start code. maybe theres some
>   magic bits between the p-vop and b-vop; maybe it has to be 8-bit
>   padded, OR not padded?

what iam saying is "there are some bits between the last p-vop
coefficient AND the b-vop startcode". these bits are written,
so that the start_code is byte aligned.
e.g.
       BitstreamPad(bs)
       BitstreamWriteVopHeader(bs,...)

xvid sets the padding bits to zero, whilst in "most" circumstances
divx5 sets them to all to 1.

maybe this is the problem? but i somehow doubt it.

-- pete


_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com