diff options
author | wm4 <wm4@nowhere> | 2019-11-25 01:16:03 +0100 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2019-11-25 01:16:03 +0100 |
commit | 13afc2150beeb1117e9c1724b2910e41ee4cc28b (patch) | |
tree | 65652f65f0dfce9b0c0abba27842e827acef5fa9 /DOCS/interface-changes.rst | |
parent | f5daae12ff600b1c109d66efeca5e18176089b90 (diff) | |
download | mpv-13afc2150beeb1117e9c1724b2910e41ee4cc28b.tar.bz2 mpv-13afc2150beeb1117e9c1724b2910e41ee4cc28b.tar.xz |
command: change af/vf property behavior wrt. filter creation failures
The behavior is slightly different in a messy way. The change is in line
with the option-to-property bridge removal mentioned some commits ago
and thus is deemed necessary.
Diffstat (limited to 'DOCS/interface-changes.rst')
-rw-r--r-- | DOCS/interface-changes.rst | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/DOCS/interface-changes.rst b/DOCS/interface-changes.rst index 0e9ca4998a..a33bfd8be2 100644 --- a/DOCS/interface-changes.rst +++ b/DOCS/interface-changes.rst @@ -47,6 +47,10 @@ Interface changes property now is unavailable if no VO exists (or the VO did not return a display FPS), instead of returning the option value in this case. The property will keep existing, but writing to it is deprecated. + - the vf/af properties now do not reject the set value anymore, even if + filter chain initialization fails. Instead, the vf/af options are always + set to the user's value, even if it does not reflect the "runtime" vf/af + chain. --- mpv 0.30.0 --- - add `--d3d11-output-format` to enable explicit selection of a D3D11 swap chain format. |