[gstreamer-bugs] [Bug 564863] New: Caps are not propagated from a ghostpad's target to the ghostpad
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Wed Dec 17 07:03:21 PST 2008
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=564863
GStreamer | gstreamer (core) | Ver: HEAD CVS
Summary: Caps are not propagated from a ghostpad's target to the
ghostpad
Product: GStreamer
Version: HEAD CVS
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gstreamer (core)
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: alessandro.d at gmail.com
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: Unspecified
GNOME milestone: Unspecified
The attached patch fixes the following case:
src = gst_pad_new_from_template (src_template, "src");
ghost_src = gst_ghost_pad_new ("ghostsrc", src);
sink = gst_pad_new_from_template (sink_template, "sink");
fail_unless (gst_pad_link (ghost_src, sink) == GST_PAD_LINK_OK);
caps1 = gst_caps_from_string ("meh");
fail_unless (gst_pad_set_caps (src, caps1));
caps2 = GST_PAD_CAPS (ghost_src);
fail_unless (gst_caps_is_equal (caps1, caps2));
gst_caps_unref (caps1);
The bug is noticeable with decodebin2. Once you get a new decoded pad
with unfixed caps, if you connect to the pad's notify::caps signal the callback
is never called even if there is data flow.
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=564863.
More information about the gstreamer-bugs
mailing list