summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2019-11-29 20:37:11 +0100
committerwm4 <wm4@nowhere>2019-11-29 20:37:11 +0100
commit90df6c79c9400d3f1c711ef5696324908a5126ce (patch)
tree27529663029c3938cc71fed61f83c93a48a37f12 /DOCS
parent053297b1ca15d7e94f746e94ea46c7399a6b097a (diff)
downloadmpv-90df6c79c9400d3f1c711ef5696324908a5126ce.tar.bz2
mpv-90df6c79c9400d3f1c711ef5696324908a5126ce.tar.xz
vf_gpu: add video filter using vo_gpu's renderer
Probably pretty useless in this form (see: the wall of warnings), but someone wanted this. I think this should be useful to perform some automated tests, maybe. Fixes: #7194
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/man/vf.rst36
1 files changed, 36 insertions, 0 deletions
diff --git a/DOCS/man/vf.rst b/DOCS/man/vf.rst
index 38b53d25fa..e2f7c9eeb8 100644
--- a/DOCS/man/vf.rst
+++ b/DOCS/man/vf.rst
@@ -710,3 +710,39 @@ Available mpv-only filters are:
Print computed fingerprints the the terminal (default: no). This is
mostly for testing and such. Scripts should use ``vf-metadata`` to
read information from this filter instead.
+
+``gpu=...``
+ Convert video to RGB using the OpenGL renderer normally used with
+ ``--vo=gpu``. This requires that the EGL implementation supports off-screen
+ rendering on the default display. (This is the case with Mesa.)
+
+ Sub-options:
+
+ ``w=<pixels>``, ``h=<pixels>``
+ Size of the output in pixels (default: 0). If not positive, this will
+ use the size of the first filtered input frame.
+
+ .. warning::
+
+ This is highly experimental. Performance is bad, and it will not work
+ everywhere in the first place. Some features are not supported.
+
+ .. warning::
+
+ This does not do OSD rendering. If you see OSD or subtitles, then these
+ have been renderer by the VO backend (or the ``sub`` video filter). This
+ is normally done in software, and potentially questionable quality.
+
+ .. warning::
+
+ If you use this with encoding mode, keep in mind that encoding mode will
+ convert the RGB filter's output back to yuv420p in software, using the
+ configured software scaler. Using ``zimg`` might improve this, but in
+ any case it might go against your goals when using this filter.
+
+ .. warning::
+
+ Do not use this with ``--vo=gpu``. It will apply filtering twice, since
+ most ``--vo=gpu`` options are unconditionally applied to the ``gpu``
+ filter. There is no mechanism in mpv to prevent this.
+