From 7520d39e8bcc0c359f6fcccf08f45313058e5740 Mon Sep 17 00:00:00 2001 From: wm4 Date: Mon, 18 Aug 2014 21:56:31 +0200 Subject: vaapi: we need more surfaces Playing with high framedrop could make it run out of surfaces. In theory, we wouldn't need an additional surface, if we could just clear the vo_vaapi internal surface - but doing so would probably be a pain, so I don't care. --- video/decode/vaapi.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/video/decode/vaapi.c b/video/decode/vaapi.c index 9625987eb4..5f9002762f 100644 --- a/video/decode/vaapi.c +++ b/video/decode/vaapi.c @@ -44,10 +44,11 @@ * - 1 decode frame * - decoding 2 frames ahead (done by generic playback code) * - keeping the reference to the previous frame (done by vo_vaapi.c) + * - keeping the reference to a dropped frame (done by vo.c) * Note that redundant additional surfaces also might allow for some * buffering (i.e. not trying to reuse a surface while it's busy). */ -#define ADDTIONAL_SURFACES 4 +#define ADDTIONAL_SURFACES 5 // Magic number taken from original MPlayer vaapi patch. #define MAX_DECODER_SURFACES 21 -- cgit v1.2.3