[Bug 780128] vaapi: playbin3 doesn't work with vaapi elements on X11

[GStreamer (GNOME Bugzilla)]

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

--- Comment #2 from Hyunjun Ko <zzoon at igalia.com> ---
(In reply to Hyunjun Ko from comment #0)
> But with playbin3, it's different.
> vpp creates vaapidisplay and shares with vaapidecoder, not vaapisink since
> it's not linked at this moment. Besides, playbin3 doesn't implement
> auto-query yet, IIRC.
> So vaapisink creates its own vaapidisplay. Finally, vaapisink get context
> query, share and use the vaapidisplay of vpp/vaapidecoder.
> 
> Meanwhile, the shared vaapidisplay is vaapidisplayglx with glx context and
> XDisplay from gst-gl.

Regarding this, I would suggest new envirnment variable just like
GST_VAAPI_ENABLE_CREATE_GL_CONTEXT or something. 
There are some cases that it creates (wrong) vaapidisplay with gl context even
though it's not necessary.

> 
> 2. XDisplay from gst-gl should be handeld by xcb probably.
> Since the
> commit(https://cgit.freedesktop.org/gstreamer/gst-plugins-bad/commit/gst-
> libs/gst/gl?id=4f6c226bd24ae3ef66bd8f4c17b001444c9b0bf1) landed, This
> XDisplay can't work in our vaapiwindow_x11.
> 
> Eventually this causes this deadlock. In wait_event in vaapiwindow_x11.c,
> it couldn't get the event MapNotify by this foreign XDisplay.

Should we implement xcb stuff?

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