[Bug 786054] mapping vaapi buffer slow
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Tue Oct 31 22:08:20 UTC 2017
https://bugzilla.gnome.org/show_bug.cgi?id=786054
--- Comment #17 from sreerenj <bsreerenj at gmail.com> ---
(In reply to Víctor Manuel Jáquez Leal from comment #16)
> Created attachment 362662 [details] [review]
> plugins: direct rendering on memory:VASurface
>
> As buffers negotiated with memory:VASurface caps feature can also be
> mapped, they can also be configured to use VA derived images, in other
> words "direct rendering".
>
> Also, because of the changes in dmabuf allocator as default allocator,
> the code for configuring the direct rendering was not clear.
>
> This patch cleans up the code and enables direct rendering when the
> environment variable GST_VAAPI_ENABLE_DIRECT_RENDERING is defined,
> even then the memory:VASurface cap feature is negotiated.
Push it :)
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list