[Bug 766704] vaapi: sharing display handle between app and vaapi elements

[GStreamer (GNOME Bugzilla)]

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

--- Comment #14 from Hyunjun Ko <zzoon at igalia.com> ---
I've been working for a while on how to provide a way to share display handle
especially for user.
I'd been looking into using GstContext only first.
As my patches, it looks working fine in normal pipeline.

But I think there are still problems and we can't remove current internal
display cache mechanism.
Important thing is that (dec-vpp-vaapisink) has to use same VADisplay to render
properly, otherwise render fails due to invalid VASurface.
But as far as I see, we can't assure it in some cases, especially using
multiple decodebin in one pipeline

eg. the case that a pipeline has 2 (decodebin-vaapisink) pipelines just like
gst-launch-1.0 filesrc ! tee name=t ! decodebin ! vaapisink t. ! decodebin !
vaapisink. 
Or 
gst-launch-1.0 filesrc ! decodebin ! vaapisink filesrc ! decodebin ! vaapisink

In these cases, we can't make sure that 1st decoder pipeline shares one, and
2nd decoder pipeline shares another. And mostly fails when trying to render.

So to use this way (in my patch), we shouldn't allow that kindof pipeline(just
like testsuite attached) or should provide a sort of playbin including vaapidec
+ vpp + vaapisink.

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