diff options
author | wm4 <wm4@nowhere> | 2015-07-08 22:04:35 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2015-07-08 22:04:35 +0200 |
commit | 23220db92443a5748cb034edf29b4c3b428bee5a (patch) | |
tree | fc49c36cf2a3b828a06d5dbed7a3136aa6e3e02f /DOCS/man | |
parent | 15581f2209898bdd1747d4a32f57a00ba5098fdd (diff) | |
download | mpv-23220db92443a5748cb034edf29b4c3b428bee5a.tar.bz2 mpv-23220db92443a5748cb034edf29b4c3b428bee5a.tar.xz |
player: disable seeking even if the cache is enabled
Until now, if a stream wasn't seekable, but the stream cache was enabled
(--cache), we've enabled seeking anyway. The idea was that at least
short seeks would typically fall within the cache. And if not, the user
was out of luck and terrible things happened. In other words, it was
unreliable.
Be stricter about it and remove this behavior. Effectively, this will
for example disable seeking in piped data.
Instead of trying to be clever, add an --force-seekable option, which
will always enable seeking if the user really wants it.
Diffstat (limited to 'DOCS/man')
-rw-r--r-- | DOCS/man/options.rst | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index da0038bfbf..8a0587e383 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -2229,6 +2229,11 @@ Demuxer ``--demuxer-readahead-bytes=<bytes>`` See ``--demuxer-readahead-packets``. +``--force-seekable=<yes|no>`` + If the player thinks that the media is not seekable (e.g. playing from a + pipe, or it's a http stream with a server that doesn't support range + requests), seeking will be disabled. This option can forcibly enable it. + For seeks within the cache, there's a good chance of success. Input ----- |