On Thu, 11 Jan 2018 09:11:08 +0800
Jun Zhao <mypopy...@gmail.com> wrote:
> On 2018/1/11 8:45, wm4 wrote:
> > On Tue, 2 Jan 2018 13:59:12 +0800
> > Jun Zhao <mypopy...@gmail.com> wrote:
> >
> >> From e030510864c28d4b17c8d1eb09ab00f274bf5dcc Mon Sep 17 00:00:00 2001
> >> From: Jun Zhao <jun.z...@intel.com>
> >> Date: Tue, 2 Jan 2018 13:55:29 +0800
> >> Subject: [PATCH] doc/codecs: Add missing documentation for hwaccel_flags.
> >>
> >> document the hwaccel_flags option for decoding.
> >>
> >> Signed-off-by: Jun Zhao <jun.z...@intel.com>
> >> ---
> >> doc/codecs.texi | 27 +++++++++++++++++++++++++++
> >> 1 file changed, 27 insertions(+)
> >>
> >> diff --git a/doc/codecs.texi b/doc/codecs.texi
> >> index 7e20374334..190f03b293 100644
> >> --- a/doc/codecs.texi
> >> +++ b/doc/codecs.texi
> >> @@ -1254,6 +1254,33 @@ ffprobe -dump_separator "
> >> Maximum number of pixels per image. This value can be used to avoid out of
> >> memory failures due to large images.
> >>
> >> +@item hwaccel_flags @var{flags} (@emph{decoding,video})
> >> +Set hardware accelerated decoding flags. (if active)
> >> +
> >> +Possible values:
> >> +@table @samp
> >> +@item ignore_level
> >> +Ignore level, should be used for decoding even if the codec level used is
> >> unknown
> >> +or higher than the maximum supported level reported by the hardware
> >> driver.
> >> +
> >> +It's generally a good idea to pass this flag unless you have a specific
> >> +reason not to, as hardware tends to under-report supported levels.
> >> +@item allow_high_depth
> >> +Allow to output YUV pixel formats with a different chroma sampling than
> >> 4:2:0
> >> +and/or other than 8 bits per component
> >> +@item allow_profile_mismatch
> > This applies only to the legacy vdpau API. (The doxygen should probably
> > be updated about this.)
> I think VA-API decoder used the allow_profile_mismatch.
I meant the allow_high_depth flag.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
