Display Failing Capabilities

[Chuck Crisler]

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.

On Wed, Feb 20, 2013 at 11:40 AM, Chuck Crisler <ccrisler at mutualink.net>wrote:

> Selectively log (first) GST_ELEMENT_PADS:4 and/or GST_PADS:4
>
>
> On Wed, Feb 20, 2013 at 11:30 AM, johnwesting <
> john.blank.westing at gmail.com> wrote:
>
>> Is there any way to display the failing capabilities when 2 elements
>> cannot
>> link using gst-launch? I've tried -v and --gst-debug-level=2 (higher than
>> 2
>> prints too much information). It's a common problem I've had throughout
>> GStreamer development and it would help me debug problems.
>>
>>
>>
>> --
>> View this message in context:
>> http://gstreamer-devel.966125.n4.nabble.com/Display-Failing-Capabilities-tp4658669.html
>> Sent from the GStreamer-devel mailing list archive at Nabble.com.
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20130220/6b93c781/attachment-0001.html>