wm4 2bf2254248 vo_vdpau: limit output surfaces to allowed maximum dimensions ... We can't do much in this case, but at least we can not call the vdpau API functions with too large sizes. Apparently the API considers this undefined behavior, and random stuff might happen.		2015-06-05 22:34:16 +02:00
..
decode	vaapi: remove direct mapping non-sense	2015-05-29 16:28:55 +02:00
filter	vf_sub: minor simplification	2015-06-05 18:59:13 +02:00
out	vo_vdpau: limit output surfaces to allowed maximum dimensions	2015-06-05 22:34:16 +02:00
csputils.c	csputils: improve contrast semantics for limited range output	2015-04-29 22:09:09 +02:00
csputils.h	…
fmt-conversion.c	…
fmt-conversion.h	…
hwdec.h	…
image_writer.c	screenshots: add option to prevent 16 bit output	2015-04-29 21:05:04 +02:00
image_writer.h	screenshots: add option to prevent 16 bit output	2015-04-29 21:05:04 +02:00
img_format.c	…
img_format.h	…
img_fourcc.h	…
mp_image.c	…
mp_image.h	…
mp_image_pool.c	…
mp_image_pool.h	…
sws_utils.c	sws_utils: re-use avcolorspace for sws colorspaces	2015-05-04 01:34:25 +02:00
sws_utils.h	…
vaapi.c	…
vaapi.h	…
vdpau.c	vdpau: do not attempt to allocate surfaces while preempted	2015-05-29 13:48:18 +02:00
vdpau.h	…
vdpau_functions.inc	vo_vdpau: directly get surface size from surface for screenshots	2015-06-05 22:34:16 +02:00
vdpau_mixer.c	vdpau: retrieve mixer parameters directly from the hw surface	2015-05-28 21:54:02 +02:00
vdpau_mixer.h	vdpau: retrieve mixer parameters directly from the hw surface	2015-05-28 21:54:02 +02:00