[XviD-devel] 1.0 bug

[pete]

hi,

On Sun, 04 Apr 2004 11:33:31 +0930 Radek Czyz <syskin at ihug.com.au>
wrote:
> 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.

i believe that packed bframes _with_  frame drop threshold>0 is an
invalid combination, because theres no way to differentiate a "packed
marker nvop" from a "real nvop".

> 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.

consider adding a max_bframes==0 condition within the framedrop
threshold check.

-- pete