summaryrefslogtreecommitdiffstats
path: root/DOCS/man
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2015-03-30 22:33:30 +0200
committerwm4 <wm4@nowhere>2015-03-31 00:09:03 +0200
commit273afdc3a4dc775e427b282f0e30c9a6ae167e06 (patch)
treec03bb6ca265baf0b9686d25707d0f6e8f385ff81 /DOCS/man
parent1164dc572c7bc69e97eb92c63a89df6767d61505 (diff)
downloadmpv-273afdc3a4dc775e427b282f0e30c9a6ae167e06.tar.bz2
mpv-273afdc3a4dc775e427b282f0e30c9a6ae167e06.tar.xz
vf_format: don't crash if nonsense parameters are passed
It was "by design" possible to make mpv crash if the parameters didn't make enough sense, like "format=rgb24:yuv420p". While forcing the format has some minor (rather questionable) use for debugging, allowing it to crash is just stupid.
Diffstat (limited to 'DOCS/man')
-rw-r--r--DOCS/man/vf.rst13
1 files changed, 2 insertions, 11 deletions
diff --git a/DOCS/man/vf.rst b/DOCS/man/vf.rst
index d79774c721..984bdda656 100644
--- a/DOCS/man/vf.rst
+++ b/DOCS/man/vf.rst
@@ -209,17 +209,8 @@ Available filters are:
``<fmt>``
Format name, e.g. rgb15, bgr24, 420p, etc. (default: don't change).
``<outfmt>``
- Format name that should be substituted for the output. If this is not
- 100% compatible with the ``<fmt>`` value, it will crash.
-
- .. admonition:: Examples
-
- ====================== =====================
- Valid Invalid (will crash)
- ====================== =====================
- ``format=rgb24:bgr24`` ``format=rgb24:420p``
- ``format=yuyv:uyvy``
- ====================== =====================
+ Format name that should be substituted for the output. If they do not
+ have the same bytes per pixel and chroma subsamplimg, it will fail.
``noformat[=fmt]``
Restricts the color space for the next filter without doing any conversion.