The strategy that I use to hone in on relevant logging is to iteratively set GST_DEBUG=*:4, grab some logging, check what isn't relevant, change the GST_DEBUG definition, setting those to :1, loop. You will quickly get a concise set if elements that you need to look at.<br>
<br><div class="gmail_quote">On Wed, Feb 20, 2013 at 11:40 AM, Chuck Crisler <span dir="ltr"><<a href="mailto:ccrisler@mutualink.net" target="_blank">ccrisler@mutualink.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Selectively log (first) GST_ELEMENT_PADS:4 and/or GST_PADS:4<div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">On Wed, Feb 20, 2013 at 11:30 AM, johnwesting <span dir="ltr"><<a href="mailto:john.blank.westing@gmail.com" target="_blank">john.blank.westing@gmail.com</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is there any way to display the failing capabilities when 2 elements cannot<br>
link using gst-launch? I've tried -v and --gst-debug-level=2 (higher than 2<br>
prints too much information). It's a common problem I've had throughout<br>
GStreamer development and it would help me debug problems.<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://gstreamer-devel.966125.n4.nabble.com/Display-Failing-Capabilities-tp4658669.html" target="_blank">http://gstreamer-devel.966125.n4.nabble.com/Display-Failing-Capabilities-tp4658669.html</a><br>


Sent from the GStreamer-devel mailing list archive at Nabble.com.<br>
_______________________________________________<br>
gstreamer-devel mailing list<br>
<a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank">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>
</blockquote></div><br>
</div></div></blockquote></div><br>