summaryrefslogtreecommitdiffstats
path: root/mpvcore
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2013-08-20 16:11:07 +0200
committerwm4 <wm4@nowhere>2013-08-20 16:11:07 +0200
commitd69b39512ded2f4d02249c811785e307962034e5 (patch)
tree865c84a83ea05255d289f560ca757a6fa5f57ded /mpvcore
parentf05206f89981872873841f6233b7a5e26031718f (diff)
downloadmpv-d69b39512ded2f4d02249c811785e307962034e5.tar.bz2
mpv-d69b39512ded2f4d02249c811785e307962034e5.tar.xz
vf_eq: fix behavior when changing parameters
Using -vf eq and changing brightness, contrast, etc. using key bindings with e.g. "add brightness 1" didn't work well: with step width 1, the property gets easily "stuck". This is a rounding problem: e.g. setting gamma to 3 would actually make it report that gamma is set to 2, so the "add" command will obviously never reach 3 with a step width of 1. Fix this by storing the parameters as integers. This was broken in cac7702. This commit effectively changed these properties to use the value as reported by vf_eq, instead of the previously set value for the "add" command. This was more robust, but not very correct either, so we keep the new behavior and make vf_eq report its parameters more accurately.
Diffstat (limited to 'mpvcore')
0 files changed, 0 insertions, 0 deletions