mirror of
https://github.com/FFmpeg/FFmpeg.git
synced 2026-08-10 17:14:41 +00:00
pts_correction_num_faulty_pts and pts_correction_num_faulty_dts were not cleared by ff_decode_flush_buffers(), so they survived avcodec_flush_buffers(). After a seek, guess_correct_pts() therefore kept biasing its reordered-pts vs dts choice on pre-seek history instead of starting fresh as it does after ff_decode_preinit(), which already zeroes both counters. This could yield an incorrect AVFrame.best_effort_timestamp on the frames following a seek. Reset both counters on flush, next to the existing last_pts/last_dts reset, so the decoder's timestamp-correction state is fully reinitialized. Fixes: ticket #11645 Reported-by: keks51 Signed-off-by: Bogdan Lisman <bogdan@pydevsolutions.com>
79 KiB
79 KiB