diff options
| author |  wm4 <wm4@nowhere> | 2017-11-10 12:37:19 +0100 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2017-11-10 12:37:19 +0100 |
| commit | 6bcdcaeeeabf3845bb69cadfb281089d434cb306 (patch) | |
| tree | c3b370ade6531a7798eaa1e31ce3aba78f86038b /DOCS | |
| parent | b0de1ac36c7b16ff4f2763421b86ebedeba2044b (diff) | |
demux: set default back buffer to some high value
Some back buffer is required to make the immediate forward range
seekable. This is because the back buffer limit is strictly enforced.
Just set a rather high back buffer by default. It's not use if
--demuxer-seekable-cache is disabled, so this is without risk.
Diffstat (limited to 'DOCS')
| -rw-r--r-- | DOCS/man/options.rst | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index 490b815415..64e467e11f 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -2866,7 +2866,9 @@ Demuxer is useful only if the ``--demuxer-seekable-cache`` option is enabled. Unlike the forward cache, there is no control how many seconds are actually cached - it will simply use as much memory this option allows. Setting this - option to 0 will strictly disable any back buffer. + option to 0 will strictly disable any back buffer, but this will lead to + the situation that the forward seek range starts after the current playback + position (as it removes past packets that are seek points). Keep in mind that other buffers in the player (like decoders) will cause the demuxer to cache "future" frames in the back buffer, which can skew the |