[Bug 768161] New: impossible for application to set GstVaapiDisplay/x11 display with vaapipostproc/vaapisink with gst_parse_launch()

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 768161
           Summary: impossible for application to set GstVaapiDisplay/x11
                    display with vaapipostproc/vaapisink with
                    gst_parse_launch()
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer-vaapi
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: ystreet00 at gmail.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
                CC: bsreerenj at gmail.com, vjaquez at igalia.com
     GNOME version: ---

(Ignoring the fact that this functionality is not technically exposed)

Have a pipeline with either vaapipostproc or vaapisink created using
gst_parse_launch() what happens is this.

vaapisink will want a vaapi display on GstElement::set_bus which is called when
adding the element to a bin/pipeline.  This seems to have been added because of
the next issue so that vaapisink creates the display first.

vaapipostproc wants a display on any caps queries which by default happen when
linking elements together.  This really should not have been added in the first
place.  If you don't have a display, just return the pad template instead.

This all works in decodebin/playbin because 1. it links manually and 2. without
checks.

When using gst_parse_launch(), both of these operations happen before the
pipeline is returned the the caller so there is no chance to attach a sync bus
message handler to respond to the need-context message.

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