Quoting Mark Thompson (2017-04-30 23:13:26)
> ---
> doc/filters.texi | 98
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 98 insertions(+)
>
> diff --git a/doc/filters.texi b/doc/filters.texi
> index 947fd7915..f57fbf6c4 100644
> --- a/doc/filters.texi
> +++ b/doc/filters.texi
> @@ -1657,6 +1657,104 @@ A floating point number which specifies chroma
> temporal strength. It defaults to
> @var{luma_tmp}*@var{chroma_spatial}/@var{luma_spatial}.
> @end table
>
> +@section hwdownload
> +
> +Download hardware frames to system memory.
> +
> +The input must be in hardware frames, and the output a non-hardware format.
> +Not all formats will be supported on the output - it may be necessary to
> insert
> +an additional @option{format} filter immediately following in the graph to
> get
> +the output in a supported format.
> +
> +@section hwmap
> +
> +Map hardware frames to system memory or to another device.
> +
> +This filter has several different modes of operation; which is used depends
> on
which one?
> +the input and output formats:
> +@itemize
> +@item
> +Hardware frame input, normal frame output
> +
> +Map the input frames to system memory and give them to the output. If the
'pass them to the output' sounds better to me
> +original hardware frame is later required (for example, after overlaying
> +something else on part of it), the @option{hwmap} filter can be used again
> +in the next mode to retrieve them.
retrieve _it_, or alternatively 'original hardware frames_s_' above
Otherwise LGTM
--
Anton Khirnov
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
