qmin and qmax are generic optiopns too. Many generic options can't be
appled to specified encoders, so just add the supported options here.
Following libaom's format probally a good idea.

Gyan <ffm...@gyani.pro> 于2019年11月12日周二 下午7:04写道:
>
>
>
> On 12-11-2019 02:39 pm, Zhong Li wrote:
> > Signed-off-by: Zhong Li <zhongli_...@126.com>
> > ---
> >   doc/encoders.texi | 3 +++
> >   1 file changed, 3 insertions(+)
> >
> > diff --git a/doc/encoders.texi b/doc/encoders.texi
> > index 6b02c7798d..8f37597999 100644
> > --- a/doc/encoders.texi
> > +++ b/doc/encoders.texi
> > @@ -1394,6 +1394,9 @@ Sets the maximum quantizer to use when using bitrate 
> > mode.
> >   @item qmin
> >   Sets the minimum quantizer to use when using bitrate mode.
> >
> > +@item threads
> > +Set the number of threads to use while encoding.
> > +
> Isn't this the lavc generic option? Maybe reformat this section like the
> libaom section.
>
> >   @item qp
> >   Uses quantizer mode to encode at the given quantizer (0-255).
>
> Gyan
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to