From 23220db92443a5748cb034edf29b4c3b428bee5a Mon Sep 17 00:00:00 2001 From: wm4 Date: Wed, 8 Jul 2015 22:04:35 +0200 Subject: 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. --- DOCS/man/options.rst | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'DOCS/man/options.rst') 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=`` See ``--demuxer-readahead-packets``. +``--force-seekable=`` + 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 ----- -- cgit v1.2.3