Have you read <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><br>
<br>gst-inspect has an option that lists the plugin debugging name.<br><br><div class="gmail_quote">On Thu, Aug 9, 2012 at 1:38 PM, Eric Montellese <span dir="ltr"><<a href="mailto:eric.montellese@videon-central.com" target="_blank">eric.montellese@videon-central.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks, in development I've run into various malformed or buggy pipelines that give this output:<div><br></div><div>
<div>gst-launch  launch ! a ! pipeline</div><div>Setting pipeline to PAUSED ...</div><div>Pipeline is PREROLLING ...</div>

</div><div><br></div><div>Generally I have debugged these issues through a mixture of brute force and intuition (looking for common sorts of problems, etc).</div><div><br></div><div>But perhaps there is a better way to determine which element has held up the pipeline?  Some swanky debug command I'm totally unaware of that shows the buffers in-flight perhaps?</div>


<div><br></div><div>Any advice?</div><div><br></div><div>Thanks,</div><div>Eric</div>
<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>
<br></blockquote></div><br>