Re: Xvid encodings and nvop

Hi Elio,

I haven't verified with xvid_encraw right now but I believe there are just
two ways how nvops can be introduced:

1) packed b-frames: In packed b-frame mode there are fake nvops written
to the output by the encoder. Those are not real nvops but are rather
supposed to be totally ignored by the decoder. As such it is not really
a proper use of nvops but it's become the defacto standard how the b-frame
encoder delay got handled with the AVI container. If you don't want to
mux your output into AVI, use the "-nopacked" switch and there should be
no fake nvops added anymore.

2) dropped frames: If the encoder is allowed to drop frames, it will output
an nvop whenever a frame got dropped. Frame dropping in xvid_encraw is
controlled via the "-drop" switch. If set to "0" (=no frame drops), there
should be no frames that get dropped and hence also no nvops produced.

Best regards,
Michael


Quoting Elio Blanca <[email protected]>:

> Hi, I'm actually seeing that xvid_encraw provides useful global   
> informations about produced frames
> in a brief summary.
> Now, the informations it prints differ from those detected by   
> mpeg4modifier (both in the gui version
> and in the cli version), the point is nvop usage: often xvid_encraw   
> reports they were written, yet
> mpeg4modifier doesn't detect them.
> Now I wonder: which is right? (I don't trust gspot 'cause it seems   
> to be abandonware)
> And then I ask: how can I set an encoding in order to be sure nvops   
> will get written? And how to set
> it in order they won't?
> Thank you
> Elio
>
> _______________________________________________
> Xvid-devel mailing list
> [email protected]
> http://list.xvid.org/mailman/listinfo/xvid-devel
>
>