summaryrefslogtreecommitdiffstats
path: root/video/filter
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2016-07-08 19:34:24 +0200
committerwm4 <wm4@nowhere>2016-07-08 19:34:24 +0200
commit6d83455a950b7cca30bc032f52ea937ce773733a (patch)
treecd1e95f798833c587fd7db7aa1a25438fe1e8ac7 /video/filter
parent35be389031fd8c7bb555d9142d2ea0b04ee70fe6 (diff)
downloadmpv-6d83455a950b7cca30bc032f52ea937ce773733a.tar.bz2
mpv-6d83455a950b7cca30bc032f52ea937ce773733a.tar.xz
vd_d3d11vpp: remove nonsensical flush call
I made this call up because I sort of thought this makes senssssse. I'm now convinced that it does not, and even is actively harmful. I'm still quite in the dark how the DirectD 11 video API is supposed to work with synchronization, but at least for normal graphics this call would not make much sense.
Diffstat (limited to 'video/filter')
-rw-r--r--video/filter/vf_d3d11vpp.c5
1 files changed, 0 insertions, 5 deletions
diff --git a/video/filter/vf_d3d11vpp.c b/video/filter/vf_d3d11vpp.c
index 100400757e..6faf712a67 100644
--- a/video/filter/vf_d3d11vpp.c
+++ b/video/filter/vf_d3d11vpp.c
@@ -331,11 +331,6 @@ static int render(struct vf_instance *vf)
goto cleanup;
}
- // Make sure the texture is updated correctly on the shared context.
- // (I'm not sure if this is correct, though it won't harm.)
- if (p->out_shared)
- ID3D11DeviceContext_Flush(p->device_ctx);
-
res = 0;
cleanup:
if (in_view)