[MPlayer-DOCS] [PATCH] XviD documentation reaching almost completeness
Diego Biurrun
diego at biurrun.de
Tue Sep 7 02:20:22 CEST 2004
Guillaume POIRIER writes:
> Le lun 06/09/2004 à 16:14, The Wanderer a écrit :
> >
> > >>+High values make RC compensate very hard the overflow, this can have a
> > >
> > > High values make RC compensate the overflow very hard
> >
> > Isn't that "compensate for"?
> I don't think so, I prefer what Diego suggests.
Nevertheless, The Wanderer is right. My English may be good, but -
you know - there's always a bigger fish ;-)
> Other than that, when Diego says:
> > > +.B quant_type=<h263|mpeg>
> > > +Sets the type of quantizer to use.
> > > +For high bitrates, you will find that MPEG quantization preserves >
> > more detail.
> > > +For low bitrates, the smoothing of H.263 will give you less block >
> > noise.
> > > +When using custom matrices, MPEG must be used.
> >
> > I'm not sure if we shouldn't write mpeg and h263 here since the text
> > refers to the parameters passed to XviD. It's not completely clear
> > in which way it is meant to be understood, though.
>
> What I'm trying to say here is that the only current parameters allowed
> here are: h263 or mpeg. For the rest, I guess it's just a matter of
> taste.
Yes. And if you are talking about the quant_type parameters they
should be written lowercase to avoid confusion. IOW mpeg is the
parameter that turns on MPEG quantization. Does this make things more
clear?
Diego
P.S.: Guillaume, it would help the readability of your mails if you
could leave a blank line between a quote and your answer. Thanks.
More information about the MPlayer-DOCS
mailing list