He Junyan 15e169fbf1 videobufferpool: don't reset surface when created internally ... The bug fixing, in commit 89f202ea, just considers the case when surface's DMABuf is set through gst_buffer_pool_acquire_buffer(), which is typically a decoder's behavior. But vaapipostproc doesn't provide any surface when calling gst_buffer_pool_acquire_buffer(), thus a surface is created when GstMemory is allocated. If the surface proxy in buffer's meta is reset at buffer_pool_reset_buffer(), that surface will be destroyed and it won't be available anymore. But GstBuffers are cached in the buffer pool and they are reused again, hence only those images are rendered repeatedly. Fixes: #232		2020-02-21 15:52:43 +00:00
..
vaapi	videobufferpool: don't reset surface when created internally	2020-02-21 15:52:43 +00:00
meson.build	vaapi: add meson build	2017-02-09 11:27:44 +01:00