diff options
| author | wm4 <wm4@nowhere> | 2015-06-05 19:25:25 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2015-06-05 22:34:16 +0200 |
| commit | e0f0f6f3e9820150a5c188e4e78f001617449f82 (patch) | |
| tree | 601f0d698476d2510904864c6a1d5fe01d7a4a8f /video/vdpau_functions.inc | |
| parent | 650469d65b6c0b18630ee4f7e7da4fad10c6dfbc (diff) | |
| download | mpv-e0f0f6f3e9820150a5c188e4e78f001617449f82.tar.bz2 mpv-e0f0f6f3e9820150a5c188e4e78f001617449f82.tar.xz | |
vo_vdpau: directly get surface size from surface for screenshots
The previous code was not wrong, but I'd claim this makes the code more
robust. If a situation could happen in which the passed surface size is
incorrect, we could have passed a too small image, and
VdpOutputSurfaceGetBitsNative could have randomly overwritten memory.
Diffstat (limited to 'video/vdpau_functions.inc')
| -rw-r--r-- | video/vdpau_functions.inc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/video/vdpau_functions.inc b/video/vdpau_functions.inc index a89fe4acd6..22c612c4ce 100644 --- a/video/vdpau_functions.inc +++ b/video/vdpau_functions.inc @@ -47,3 +47,4 @@ VDP_FUNCTION(VdpVideoSurfaceGetBitsYCbCr, VDP_FUNC_ID_VIDEO_SURFACE_GET_BITS_Y_C VDP_FUNCTION(VdpVideoSurfaceGetParameters, VDP_FUNC_ID_VIDEO_SURFACE_GET_PARAMETERS, video_surface_get_parameters) VDP_FUNCTION(VdpVideoSurfaceQueryCapabilities, VDP_FUNC_ID_VIDEO_SURFACE_QUERY_CAPABILITIES, video_surface_query_capabilities) VDP_FUNCTION(VdpOutputSurfaceQueryCapabilities, VDP_FUNC_ID_OUTPUT_SURFACE_QUERY_CAPABILITIES, output_surface_query_capabilities) +VDP_FUNCTION(VdpOutputSurfaceGetParameters, VDP_FUNC_ID_OUTPUT_SURFACE_GET_PARAMETERS, output_surface_get_parameters) |