From 91c1691b35d4bfa01cd56f181ff88358a8b23ace Mon Sep 17 00:00:00 2001 From: Nicolas F Date: Sun, 5 May 2019 19:15:01 +0200 Subject: man: clarify vavpp requirements I assume (but cannot confirm) that VA-AP-API is in fact a typo, because most if not all search engine results related to it are from mpv's manual page. By changing this to VA-API and clarifying that this requires VA-API support on a system to use it, we can hopefully make it clear to unsuspecting Windows users that this is not the filter they're looking for. Concerns #6690. --- DOCS/man/vf.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'DOCS/man') diff --git a/DOCS/man/vf.rst b/DOCS/man/vf.rst index 92c642c24b..1f8780383d 100644 --- a/DOCS/man/vf.rst +++ b/DOCS/man/vf.rst @@ -468,8 +468,9 @@ Available mpv-only filters are: other userdata type will result in hard crashes. ``vavpp`` - VA-AP-API video post processing. Works with ``--vo=vaapi`` and ``--vo=gpu`` - only. Currently deinterlaces. This filter is automatically inserted if + VA-API video post processing. Requires the system to support VA-API, + i.e. Linux/BSD only. Works with ``--vo=vaapi`` and ``--vo=gpu`` only. + Currently deinterlaces. This filter is automatically inserted if deinterlacing is requested (either using the ``d`` key, by default mapped to the command ``cycle deinterlace``, or the ``--deinterlace`` option). -- cgit v1.2.3