path: root/DOCS/man/options.rst
diff options
Diffstat (limited to 'DOCS/man/options.rst')
1 files changed, 9 insertions, 91 deletions
diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst
index 9c66ca35cb..c8e75556c0 100644
--- a/DOCS/man/options.rst
+++ b/DOCS/man/options.rst
@@ -3836,97 +3836,15 @@ TV
- Set the size of the cache in kilobytes, disable it with ``no``, or
- automatically enable it if needed with ``auto`` (default: ``auto``).
- With ``auto``, the cache will usually be enabled for network streams,
- using the size set by ``--cache-default``. With ``yes``, the cache will
- always be enabled with the size set by ``--cache-default`` (unless the
- stream cannot be cached, or ``--cache-default`` disables caching).
- May be useful when playing files from slow media, but can also have
- negative effects, especially with file formats that require a lot of
- seeking, such as MP4.
- Note that half the cache size will be used to allow fast seeking back. This
- is also the reason why a full cache is usually not reported as 100% full.
- The cache fill display does not include the part of the cache reserved for
- seeking back. The actual maximum percentage will usually be the ratio
- between readahead and backbuffer sizes.
- Set the size of the cache in kilobytes (default: 10000 KB). Using ``no``
- will not automatically enable the cache e.g. when playing from a network
- stream. Note that using ``--cache`` will always override this option.
- Playback will start when the cache has been filled up with this many
- kilobytes of data (default: 0).
- If a seek is to be made to a position within ``<kBytes>`` of the cache
- size from the current position, mpv will wait for the cache to be
- filled to this position rather than performing a stream seek (default:
- 500).
- This matters for small forward seeks. With slow streams (especially HTTP
- streams) there is a tradeoff between skipping the data between current
- position and seek destination, or performing an actual seek. Depending
- on the situation, either of these might be slower than the other method.
- This option allows control over this.
- Size of the cache back buffer (default: 10000 KB). This will add to the total
- cache size, and reserved the amount for seeking back. The reserved amount
- will not be used for readahead, and instead preserves already read data to
- enable fast seeking back.
- Create a cache file on the filesystem.
- There are two ways of using this:
- 1. Passing a path (a filename). The file will always be overwritten. When
- the general cache is enabled, this file cache will be used to store
- whatever is read from the source stream.
- This will always overwrite the cache file, and you can't use an existing
- cache file to resume playback of a stream. (Technically, mpv wouldn't
- even know which blocks in the file are valid and which not.)
- The resulting file will not necessarily contain all data of the source
- stream. For example, if you seek, the parts that were skipped over are
- never read and consequently are not written to the cache. The skipped over
- parts are filled with zeros. This means that the cache file doesn't
- necessarily correspond to a full download of the source stream.
- Both of these issues could be improved if there is any user interest.
- .. warning:: Causes random corruption when used with ordered chapters or
- with ``--audio-file``.
- 2. Passing the string ``TMP``. This will not be interpreted as filename.
- Instead, an invisible temporary file is created. It depends on your
- C library where this file is created (usually ``/tmp/``), and whether
- filename is visible (the ``tmpfile()`` function is used). On some
- systems, automatic deletion of the cache file might not be guaranteed.
- If you want to use a file cache, this mode is recommended, because it
- doesn't break ordered chapters or ``--audio-file``. These modes open
- multiple cache streams, and using the same file for them obviously
- clashes.
- See also: ``--cache-file-size``.
- Maximum size of the file created with ``--cache-file``. For read accesses
- above this size, the cache is simply not used.
- Keep in mind that some use-cases, like playing ordered chapters with cache
- enabled, will actually create multiple cache files, each of which will
- use up to this much disk space.
- (Default: 1048576, 1 GB.)
+ Decide whether to use network cache settings (default: auto).
+ If enabled, use the maximum of ``--cache-secs`` and ``--demuxer-max-bytes``
+ for the cache size. If disabled, ``--cache-pause`` and related are
+ implicitly disabled.
+ The ``auto`` choice sets this depending on whether the stream is thought to
+ involve network accesses (this is an imperfect heuristic).
Turn off input stream caching. See ``--cache``.