summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2016-09-03 13:05:19 +0200
committerwm4 <wm4@nowhere>2016-09-03 13:05:19 +0200
commit9bc39b352e66dafa092d574c72ab1ce9d9393e71 (patch)
treec83b022a00d3b63db497a9b716066b291b8d1e4f
parentece86d1061d17bd6c3d778029ca2cec1478b9539 (diff)
downloadmpv-9bc39b352e66dafa092d574c72ab1ce9d9393e71.tar.bz2
mpv-9bc39b352e66dafa092d574c72ab1ce9d9393e71.tar.xz
manpage: document another option/property inconsistence
-rw-r--r--DOCS/man/input.rst13
1 files changed, 13 insertions, 0 deletions
diff --git a/DOCS/man/input.rst b/DOCS/man/input.rst
index 84166a565f..faf52fd4b1 100644
--- a/DOCS/man/input.rst
+++ b/DOCS/man/input.rst
@@ -2082,6 +2082,19 @@ caveats with some properties (due to historical reasons):
If a VO is created, this will return either the actual display FPS, or
an invalid value, instead of the option value.
+``audio-file``, ``sub-file``, ``external-file``
+ These options/properties are actually lists of filenames. To make the
+ command-line interface easier, each ``--audio-file=...`` option appends
+ the full string to the internal list. However, when used as properties,
+ every time you set the property as a string the internal list will be
+ replaced with a single entry containing the string you set. ``,`` or other
+ separators are never used. You have to use ``MPV_FORMAT_NODE_ARRAY`` (or
+ corresponding API, e.g. ``mp.set_property_native()`` with a table in Lua)
+ to set multiple entries.
+
+ Strictly speaking, option access via API (e.g. ``mpv_set_option_string()``)
+ has the same problem, and it's only a difference between CLI/API.
+
``demuxer``, ``idle``, ``length``, ``audio-samplerate``, ``audio-channels``, ``audio-format``, ``fps``, ``cache``
These behave completely different as property, but are deprecated (newer
aliases which don't conflict have been added). After the deprecation period