diff options
| author | wm4 <wm4@nowhere> | 2015-10-27 20:56:49 +0100 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2015-10-27 20:56:49 +0100 |
| commit | c24921d56b08116965ac6aed4d334342eb6b30d1 (patch) | |
| tree | bab384ea5035753c3fc36193dba33fff8295f4fd /player | |
| parent | aaec2aba3890e1b2ea8f4dc158d884bc85a59517 (diff) | |
| download | mpv-c24921d56b08116965ac6aed4d334342eb6b30d1.tar.bz2 mpv-c24921d56b08116965ac6aed4d334342eb6b30d1.tar.xz | |
player: fix display-sync A/V calculation on high playback speeds
This is all kinds of stupid - update_avsync_after_frame() will multiply
this value with the speed at a later point, and we only update this
field for this function. (This should be refactored.)
Diffstat (limited to 'player')
| -rw-r--r-- | player/video.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/player/video.c b/player/video.c index 3ea5607b35..f4affbd51d 100644 --- a/player/video.c +++ b/player/video.c @@ -1037,6 +1037,7 @@ static void handle_display_sync_frame(struct MPContext *mpctx, // align frame timings on the vsync boundaries. This is unavoidable, and // for the sake of the video sync calculations we pretend it's perfect. mpctx->time_frame -= mpctx->display_sync_error; + mpctx->time_frame /= opts->playback_speed * video_speed_correction; mpctx->speed_factor_v = video_speed_correction; |