[Bug 790999] New: only vaapisink should query for app context

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 790999
           Summary: only vaapisink should query for app context
    Classification: Platform
           Product: GStreamer
           Version: unspecified
                OS: All
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer-vaapi
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: vjaquez at igalia.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
                CC: bsreerenj at gmail.com, vjaquez at igalia.com
     GNOME version: ---

Right now there are two contexts that are queried by GstVaapi:

the old gst.vaapi.Display which contains a GstVaapiDisplay object

and the new gst.vaapi.app.Display which contains a VADisplay opaque structure
and a native display object (right now X Display, but soon wl display).

The purpose of the last one is to applications to set their own VADisplay
when using vaapisink in overlay mode, since gstreamer-vaapi doesn't expose
a library for GstVaapiDisplay.

Currenty all gstreamer-vaapi elements query for both context types, though 
the first one is desgined to be shared among the pipeline, and the second
only make sense when vaapisink is used, and creates it's own GstVaapiDisplay
object (which most be shared among the pipeline afterwards).

I think there is a bug: only vaapisink should query for gst.vaapi.app.Display,
and the rest of vaapi elements for gst.vaapi.Display. Even more, when 
vaapisink creates its own GstVaapiDisplay from gst.vaapi.app.Display, it 
should be propagated (the GstVaapiDisplay context not the other one).

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