[XviD-devel] 1.0 bug
Radek Czyz
syskin at ihug.com.au
Sun Apr 4 04:03:31 CEST 2004
Hey,
> By the way, we should keep in mind that if "DX50" p-vop becomes an
> n-vop, GOP is not closed anymore. This might happen even at zero frame
> drop ratio, because any p-vop will be changed into n-vop if all its MBs
> are not coded (logical).
Actually it's still b0rked :(
Look at the following sequence in encoder: P B N N I
Because of closed GOP, gets changed to P P N N I
...and the N-vops suddenly get a new reference. Not to mention that
encoding order is wrong, N-vops are already in the bitstream when we
code the pvop.
What do we do what do we do...
I think we need a stupid hack that will get rid of the problem for 1.0.
And we need it quick.
Radek
More information about the XviD-devel
mailing list