From d4c1ddd6b166ff2d883a9d2b80c11f9cbf028226 Mon Sep 17 00:00:00 2001 From: wm4 Date: Sun, 2 Apr 2017 18:47:36 +0200 Subject: video: add automatic libavfilter bridge to option parsing Now you can for example do "--vf=hue=h=60" - there is no "hue" filter in mpv, so libavfilter's will be used. This has certain caveats (see manpage). The point of this is providing a relatively smooth transition path to removing our own filter stuff. --- DOCS/man/vf.rst | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'DOCS/man/vf.rst') diff --git a/DOCS/man/vf.rst b/DOCS/man/vf.rst index 28fd7d7e8e..f2bd16033c 100644 --- a/DOCS/man/vf.rst +++ b/DOCS/man/vf.rst @@ -59,6 +59,13 @@ normal filter parameters. in mpv (such as filters which deal with mpv specifics, or which are implemented in mpv only). + If a filter is not builtin, the ``lavfi-bridge`` will be automatically + tried. Keep in mind that this filter does not support positional arguments + like ``--vf=name=arg1:arg2``. Instead, you must use + ``--vf=name=arg1name=arg1value:...``. This bridge also does not support + help output, and does not verify parameters before the filter is actually + used. + Video filters are managed in lists. There are a few commands to manage the filter list. -- cgit v1.2.3