From 234d63292092d1450120abde1dce8843c2188bf0 Mon Sep 17 00:00:00 2001 From: wm4 Date: Mon, 19 Jan 2015 18:00:41 +0100 Subject: video: fix waiting for last frame/format reconfig We still need to send the VO a duration in these cases. Disabling framedrop has logically absolutely nothing to do with these cases; it was overlooked in commit 918b06c4. So we always send the frame duration (or a guess for it), and check whether framedropping is actually enabled in the VO code. (It would be cleaner to send framedrop as a flag, but I don't care about that right now.) --- player/video.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'player') diff --git a/player/video.c b/player/video.c index 05c5fd42e1..6369428871 100644 --- a/player/video.c +++ b/player/video.c @@ -824,7 +824,7 @@ void write_video(struct MPContext *mpctx, double endpts) diff = vpts1 - vpts0; if (diff < 0 && mpctx->d_video->fps > 0) diff = 1.0 / mpctx->d_video->fps; // fallback to demuxer-reported fps - if (opts->untimed || vo->driver->untimed || !(opts->frame_dropping & 1)) + if (opts->untimed || vo->driver->untimed) diff = -1; // disable frame dropping and aspects of frame timing if (diff >= 0) { // expected A/V sync correction is ignored -- cgit v1.2.3