diff options
| author | wm4 <wm4@nowhere> | 2019-05-16 17:14:34 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2019-09-19 20:37:04 +0200 |
| commit | 53cf4e27d48c783d4dc0103d9d082597a1266c0f (patch) | |
| tree | a5e1102cb7dda9d0182e6bc8ff95fc75bba18d49 /libmpv | |
| parent | 2d2d96f00b9b055d996bb9ba875be72491a3a74b (diff) | |
| download | mpv-53cf4e27d48c783d4dc0103d9d082597a1266c0f.tar.bz2 mpv-53cf4e27d48c783d4dc0103d9d082597a1266c0f.tar.xz | |
demux: adjust reader_head on range joining
I'm not sure about this, but it looks like a bug. If a stream didn't
have packets, but the joined range does, the stream should obviously
read the packets added by the joined range. Until now, due to
reader_head being NULL, reading was only resumed if a _new_ packet was
added by actual demuxing (in add_packet_locked()), which means the
stream would suddenly skip ahead, past the original end of the joined
range.
Change it so that it will pick up the new range.
Also, clear the skip_to_keyframe flag. Nothing useful can come from this
flag being set; in the first place, the first packet of a range (that
isn't the current range) should start with a keyframe. Some code
probably enforced it (although it's fuzzy).
Completely untested.
Diffstat (limited to 'libmpv')
0 files changed, 0 insertions, 0 deletions