diff options
author | wm4 <wm4@nowhere> | 2017-10-23 20:09:21 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2017-10-23 20:55:11 +0200 |
commit | 05ae571241a1623ea7b58b7cded2d2988931033b (patch) | |
tree | c77ac858d54dc4cfa48f1a1fbabb06a660b84984 /video/out/gpu/spirv.c | |
parent | 512509705e03ed0bda122e1e96cda8a40eeaf720 (diff) | |
download | mpv-05ae571241a1623ea7b58b7cded2d2988931033b.tar.bz2 mpv-05ae571241a1623ea7b58b7cded2d2988931033b.tar.xz |
demux: fix cached SEEK_FORWARD seeks into end of cached regions/EOF
Although seeking past the cached range will trigger a low level seek, a
seek into the region between cache end and last video key frame would
simply seek to the video key frame. This meant that you could get
"stuck" at the end of the file instead of terminating playback when
trying to seek past the end.
One change is that we fix this by _actually_ allowing SEEK_FORWARD to
seek past the last video keyframe in find_seek_target().
In that case, or otherwise seeking to cache buffer end, it could happen
that we set ds->reader_head=NULL if the seek target is after the current
packet. We allow this, because the end of the cached region is defined
by the existence of "any" packet, not necessarily a key frame. Seeking
there still makes sense, because we know that there is going to be more
packets (or EOF) that satisfy the seek target.
The problem is that just resuming demuxing with reader_head==NULL will
simply return any packets that come its way, even non-keyframe ones.
Some decoders will produce ugly soup in this case. (In practice, this
was not a problem, because seeking at the end of the cached region was
rare before this commit, and also some decoders like h264 will skip
broken frames by default anyway.)
So the other change of this commit is to enable key frame skipping.
As a nasty implementation detail, we use a separate flag, instead of
setting reader_head to the first key frame encounted (reader_head being
NULL can happen after a normal seek or on playback start, and then we
want to mirror the underlying demuxer behavior, for better or worse).
This change is relatively untested, so you get to keep the pieces for
yourself.
Diffstat (limited to 'video/out/gpu/spirv.c')
0 files changed, 0 insertions, 0 deletions