Ouch, your mail was picked up by some filter and didn't read it until just now, after I've already solved the problem... But thanks anyway! :-)<div><br><div>For future reference, the bug was indeed inside decodebin elements.</div>
<div><br></div><div>I made some tests. These are the contents of decodebin after the pipeline is initialized:<div> - 0.10.29: typefind ! ffdec_h264</div><div> - 0.10.36: typefind ! h264parse ! ffdec_h264</div><div>It turns out, for 0.10.36 I was installing the -bad package (which provides the h264parse element), while for 0.10.29 I was not installing it.</div>
<div><br></div><div>Simply removing the -bad package, that element is not inserted inside decodebin anymore, and most of my problems have disappeared (custom events removed, also recorded video playing at infinite rate, and other things).</div>
<div><br></div><div><br></div><div><br><div class="gmail_quote">On Tue, Oct 2, 2012 at 2:56 PM, Jan Schmidt <span dir="ltr"><<a href="mailto:thaytan@noraisin.net" target="_blank">thaytan@noraisin.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, 2012-10-02 at 08:04 +0200, Bruno Gonzalez wrote:<br>
> Hi all,<br>
> I'm using the python bindings to create a pipeline like this:<br>
> rtspsrc queue rtph264depay capsfilter tee decodebin tee<br>
> videocrop tee videoscale tee capsfilter x264enc tee custom_bin<br>
><br>
> I insert a gst.EVENT_CUSTOM_DOWNSTREAM in<br>
> the tee between capsfilter and decodebin (using tee.send_event(my_event) ).<br>
><br>
> I have added event_probes to all elements' "sink" and "src" pads, in<br>
> order to track the life of the custom event.<br>
><br>
> In gstreamer 0.10.29, the event travels through all elements until it<br>
> reaches my custom_bin element, where I process it.<br>
> In gstreamer 0.10.36, the event arrives at the decodebin sink pad, but<br>
> does not arrive at its src pad, or any other elements after it (so it<br>
> never reaches my custom_bin).<br>
<br>
</div>In general, this is a bug in a specific element that decodebin is<br>
plugging. In your case there's probably only 2 elements to check:<br>
h264parse and ffdec_h264 ?<br>
<div class="im"><br>
J.<br>
><br>
><br>
> My code remains exactly the same, the only change is the gstreamer<br>
> version that is installed.<br>
><br>
><br>
> Other events, such<br>
> as GST_EVENT_NEWSEGMENT or GST_EVENT_LATENCY traverse all elements<br>
> with no problems in both 0.10.29 and 0.10.36.<br>
><br>
><br>
> Any hints as to why the custom event would be stopping at<br>
> the decodebin element in 0.10.36?<br>
><br>
><br>
> Thanks in advance!<br>
><br>
><br>
> --<br>
> Saludos,<br>
> Bruno González<br>
><br>
> _______________________________________________<br>
> Jabber: stenyak AT <a href="http://gmail.com" target="_blank">gmail.com</a><br>
> <a href="http://www.stenyak.com" target="_blank">http://www.stenyak.com</a><br>
</div>> _______________________________________________<br>
> gstreamer-devel mailing list<br>
> <a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a><br>
> <a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Jan Schmidt <<a href="mailto:thaytan@noraisin.net">thaytan@noraisin.net</a>><br>
<br>
_______________________________________________<br>
gstreamer-devel mailing list<br>
<a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
</font></span></blockquote></div><br></div></div></div>