From 36972aec535354c70b68021935bb7d238442b1cd Mon Sep 17 00:00:00 2001 From: Niklas Haas Date: Fri, 18 Aug 2023 14:16:29 +0200 Subject: vo_gpu: allow --hdr-peak-decay-rate=0.0 This completely disables all smoothing. Despite what the manual claims, a decay rate of 1.0 does *not*. It's worth pointing out that this depends on the following commit to work properly in --vo=gpu-next, but I don't think working around such a minor detail is worth the trouble, considering people building nightly mpv are probably also building nightly libplacebo it should just work (tm). See-Also: https://github.com/haasn/libplacebo/commit/1c464baaf4c6228dcfac87f19db1dafc22e328c8 See-Also: https://github.com/haasn/libplacebo/commit/83af2d4ebd5086a56f7b1a2f86628ada3612ee7c --- DOCS/man/options.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'DOCS/man') diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index 5ac17947c2..71e133e7ff 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -6707,12 +6707,12 @@ them. range of scenes with very bright isolated highlights. Values other than 100 come with a small performance penalty. (Only for ``--vo=gpu-next``) -``--hdr-peak-decay-rate=<1.0..1000.0>`` +``--hdr-peak-decay-rate=<0.0..1000.0>`` The decay rate used for the HDR peak detection algorithm (default: 100.0). This is only relevant when ``--hdr-compute-peak`` is enabled. Higher values make the peak decay more slowly, leading to more stable values at the cost of more "eye adaptation"-like effects (although this is mitigated somewhat - by ``--hdr-scene-threshold``). A value of 1.0 (the lowest possible) disables + by ``--hdr-scene-threshold``). A value of 0.0 (the lowest possible) disables all averaging, meaning each frame's value is used directly as measured, but doing this is not recommended for "noisy" sources since it may lead to excessive flicker. (In signal theory terms, this controls the time -- cgit v1.2.3