diff options
author | wm4 <wm4@nowhere> | 2014-09-16 22:06:27 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2014-09-16 23:59:13 +0200 |
commit | 6ef40cb91024b7d76694760a74fa2dd5b44025a1 (patch) | |
tree | 57e79ee9fbf49a74a6d775448dedc7bfdeb20da1 /video/out | |
parent | 60f5e53f605325c69a4861f732a2c1d51d5ba820 (diff) | |
download | mpv-6ef40cb91024b7d76694760a74fa2dd5b44025a1.tar.bz2 mpv-6ef40cb91024b7d76694760a74fa2dd5b44025a1.tar.xz |
video: wake up core as soon as possible
There's no reason to let the core wait until the frame is done
displaying. In practice, the core normally didn't need this additional
wakeup, and the VO was quick enough to fetch the new frame, before the
core even attempted to queue a new frame. But it wasn't entirely clean,
and the correct wakeup handling might matter in some cases.
Diffstat (limited to 'video/out')
-rw-r--r-- | video/out/vo.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/video/out/vo.c b/video/out/vo.c index 09d203ab2f..890052d67f 100644 --- a/video/out/vo.c +++ b/video/out/vo.c @@ -573,6 +573,7 @@ static bool render_frame(struct vo *vo) } else { in->hasframe_rendered = true; pthread_mutex_unlock(&in->lock); + mp_input_wakeup(vo->input_ctx); // core can queue new video now MP_STATS(vo, "start video"); |