[Bug 763491] New: Typefind behavior has changed on have-type signal

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Fri Mar 11 10:29:06 UTC 2016


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

            Bug ID: 763491
           Summary: Typefind behavior has changed on have-type signal
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: All
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: romain.picard at oakbits.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

We have an application that queries the caps of the typefind source pad in the
context of the "have-type" signal callback.

This worked well on 0.10 and on 1.4.5. We are currently updrading to 1.6.3 and
we see that the behavior of gst_pad_query_caps have changed in this case, since
the bug 735896.

Before this commit, it was possible to query the pad caps because the object
method handler was called first. So the caps were already set when our signal
handler was called. 

A possible fix in our application is to use the caps provided in the signal.
But since the code querying the caps is not directly in the handler but in some
more generic code, we will have to add a specific behavior for this.

Looking at the description and commit of bug 735896 it seems that being able to
query the pad caps in the signal handler is incompatible with the aim of
setting them after the signal handlers have been called. Do you see any way to
allow both ?

-- 
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