|author||wm4 <wm4@nowhere>||2014-08-18 21:56:31 +0200|
|committer||wm4 <wm4@nowhere>||2014-08-18 22:59:01 +0200|
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.
1 files changed, 2 insertions, 1 deletions
diff --git a/video/decode/vaapi.c b/video/decode/vaapi.c
index 9625987eb4..5f9002762f 100644
@@ -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