[Bug 755072] vaapi: expose memory:DMABuf capsfeature

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=755072

--- Comment #40 from Víctor Manuel Jáquez Leal <vjaquez at igalia.com> ---
(In reply to Julien Isorce from comment #39)

> In your detailed downstream sequence (1, 2, 3, 4) for me it means that you
> will export every-time a buffer is pushed (instead of exporting once for all
> at pool configuration), so the same surface will be exported with a
> different fd and downstream element will not be able to do caching. What I
> am missing ?

My first approach will be to assume that the surface's derive image will always
export the same fd, and to cache the dmabuf-based exported buffer as a vaapi
buffer qdata.

> Is 4) to call vaReleaseBufferHandler at the proper time ?

That's why we need to cache the dmabuf-based buffer as a vaapi buffer qdata, to
release it before processing it.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.