diff options
author | wm4 <wm4@nowhere> | 2015-11-10 16:06:42 +0100 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2015-11-10 16:06:42 +0100 |
commit | 9a6ec9de2f5e80010ffd81bfba72abb4b02f8b9d (patch) | |
tree | 9fa10d1aecfb55df1e299f8fffebb7ef3d978a93 /player | |
parent | 4682b0147e66f2e9b573510ae21f701a851d355a (diff) | |
download | mpv-9a6ec9de2f5e80010ffd81bfba72abb4b02f8b9d.tar.bz2 mpv-9a6ec9de2f5e80010ffd81bfba72abb4b02f8b9d.tar.xz |
vd_lavc: be more careful with flushing the decoder
Until now, we've relied on the following things:
- you can send flush packets to the decoder even if it's fully flushed,
- you can send new packets to a flushed decoder,
- you can send new packers to a partially flushed decoder.
("flushing" refers to sending flush packets to the decoder until the
decoder does not return new pictures, not avcodec_flush_buffers().)
All of these are questionable. The libavcodec API probably doesn't
guarantee that these work well or at all, even though most decoders have
no issue with these. But especially with hardware decoding wrappers
(like MMAL), real problems can be expected. Isolate us from these corner
cases by handling them explicitly.
Diffstat (limited to 'player')
0 files changed, 0 insertions, 0 deletions