summaryrefslogtreecommitdiffstats
path: root/stream/stream.h
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2019-11-06 22:42:44 +0100
committerwm4 <wm4@nowhere>2019-11-06 22:42:44 +0100
commit8a0929973de15d9574595c5a098bb3446757ef16 (patch)
treeb4b2ba54e5bcb4ea7672346fb0e8d186eab29ddf /stream/stream.h
parente8aae688c3fa622dca171c77caed69732e14ede2 (diff)
downloadmpv-8a0929973de15d9574595c5a098bb3446757ef16.tar.bz2
mpv-8a0929973de15d9574595c5a098bb3446757ef16.tar.xz
vo_gpu: unconditionally clear framebuffer on start of frame
For some reason, the first frame displayed on X11 with amdgpu and OpenGL will be garbled. This is especially visible if the player starts, displays a frame, but then still takes a while to properly start playback. With --interpolation, the behavior somehow changes (usually gets worse). I'm not sure what exactly is going on, and the code in video.c is way too abstruse. Maybe there is some slight possibility that a frame with uncleared contents gets displayed, which somehow also corrupts another frame that is displayed immediately after that. If clear is unconditionally run, this somehow doesn't happen, and you see a video frame. By any logic this shouldn't happen: a video frame should always overwrite the background. So I can't exclude that this isn't some sort of driver bug, or at least very obscure interaction. Clearing should be practically free anyway, so always do it. Fixes: #7105
Diffstat (limited to 'stream/stream.h')
0 files changed, 0 insertions, 0 deletions