summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2019-05-17 22:29:27 +0200
committerwm4 <wm4@nowhere>2019-09-19 20:37:04 +0200
commit455c0855388f87de3e358f185835f50fac33d887 (patch)
tree830dd664acc9c5d81ceab4b86f20119b623cec59
parenta3991078bde2266184fa3eb71b0e6228975f55db (diff)
downloadmpv-455c0855388f87de3e358f185835f50fac33d887.tar.bz2
mpv-455c0855388f87de3e358f185835f50fac33d887.tar.xz
manpage: remove double fw-bytes documentation
It was documented two times, with different text. Merge them and reword it a little.
-rw-r--r--DOCS/man/input.rst9
1 files changed, 3 insertions, 6 deletions
diff --git a/DOCS/man/input.rst b/DOCS/man/input.rst
index 99c8a3893b..814d7a6825 100644
--- a/DOCS/man/input.rst
+++ b/DOCS/man/input.rst
@@ -1458,7 +1458,9 @@ Property list
cached.
``fw-bytes`` is the number of bytes of packets buffered in the range
- starting from the current decoding position.
+ starting from the current decoding position. This is a rough estimate
+ (may not account correctly for various overhead), and stops at the
+ demuxer position (it ignores seek ranges after it).
When querying the property with the client API using ``MPV_FORMAT_NODE``,
or with Lua ``mp.get_property_native``, this will return a mpv_node with
@@ -1491,11 +1493,6 @@ Property list
Sum of packet bytes (plus some overhead estimation) of the entire packet
queue, including cached seekable ranges.
- ``fw-bytes``
- Sum of packet bytes (plus some overhead estimation) of the readahead
- packet queue (packets between current decoder reader positions and
- demuxer position).
-
``demuxer-via-network``
Returns ``yes`` if the stream demuxed via the main demuxer is most likely
played via network. What constitutes "network" is not always clear, might