From 455c0855388f87de3e358f185835f50fac33d887 Mon Sep 17 00:00:00 2001 From: wm4 Date: Fri, 17 May 2019 22:29:27 +0200 Subject: manpage: remove double fw-bytes documentation It was documented two times, with different text. Merge them and reword it a little. --- DOCS/man/input.rst | 9 +++------ 1 file 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 -- cgit v1.2.3