From 273afdc3a4dc775e427b282f0e30c9a6ae167e06 Mon Sep 17 00:00:00 2001 From: wm4 Date: Mon, 30 Mar 2015 22:33:30 +0200 Subject: 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. --- DOCS/man/vf.rst | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) (limited to 'DOCS/man/vf.rst') 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: ```` Format name, e.g. rgb15, bgr24, 420p, etc. (default: don't change). ```` - Format name that should be substituted for the output. If this is not - 100% compatible with the ```` 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. -- cgit v1.2.3