Hi Richard, When i found myself in situations like yours i find useful to use the identity element before/after the element that I'm suspecting to be the one that stalled. Also, GST_DEBUG is extremely useful, if you just use GST_DEBUG=5, the amount of debug information is overwhelming, but if you use GST_DEBUG=element:level, it gets a lot more interesting (i found a lot of bugs on my elements using GST_DEBUG=my_element:5). Debug in general: <a href="http://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/section-checklist-debug.html">http://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/section-checklist-debug.html</a> Identity element: <a href="http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-plugins/html/gstreamer-plugins-identity.html">http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-plugins/html/gstreamer-plugins-identity.html</a> Debug elements that may be useful: <a href="http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good-plugins/html/gst-plugins-good-plugins-plugin-debug.html">http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good-plugins/html/gst-plugins-good-plugins-plugin-debug.html</a> Hope this helps. Best regards, Tiago Katcipis <div class="gmail_quote">On Sat, May 5, 2012 at 9:36 AM, Richard <<a href="mailto:tuxbox.guru@gmail.com" target="_blank">tuxbox.guru@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi All, Is there a method in Gstreamer to determine which component in the pipeline has stalled. Currently I have a FIFO file written to by an application, this FIFO file is read by a filesrc SRC component and after mangling the data is written to a FDSINK (which is a TCP/IP handle to a Video viewer) Randomly (it feels like it) the Gstreamer pipeline stops consuming data out the FIFO and then it overflows. I have to tear the pipeline down and re-start it for the data flow to resume. Is there callback function/callback that shows how many packets were consumed/produced as I have no idea what pipe is stalling. I am using a leaky queue before the fdsink to help protect the MPEGTSDEMUX/other components but even in this case the filesource stops reading data. I have tried using GST_DEBUG but that spams the console its almost unusable... any alternatives to find out where the holdup is occuring? Richard _______________________________________________ gstreamer-devel mailing list <a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank">gstreamer-devel@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a> </blockquote></div>