Pipeline Debugging.

Tiago Katcipis katcipis at inf.ufsc.br
Fri May 11 08:22:51 PDT 2012


On Wed, May 9, 2012 at 6:11 PM, Stefan Sauer <ensonic at hora-obscura.de>wrote:

>  On 05/07/2012 03:18 PM, Tiago Katcipis wrote:
>
> 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).
>
> and use the gst-debug-viewer (see
> http://cgit.freedesktop.org/~cymacs/gst-debug-viewer/) for long log files.
>

Awesome,

this is new to me, is there any reference of it on gstreamer website ?


>
> Stefan
>
>
> Debug in general:
>
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/section-checklist-debug.html
>
> Identity element:
>
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-plugins/html/gstreamer-plugins-identity.html
>
> Debug elements that may be useful:
>
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good-plugins/html/gst-plugins-good-plugins-plugin-debug.html
>
> Hope this helps.
>
> Best regards,
> Tiago Katcipis
>
> On Sat, May 5, 2012 at 9:36 AM, Richard <tuxbox.guru at gmail.com> wrote:
>
>> 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
>> gstreamer-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>>
>
>
>
> _______________________________________________
> gstreamer-devel mailing listgstreamer-devel at lists.freedesktop.orghttp://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
>
>
> _______________________________________________
> 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/20120511/816a7ca9/attachment-0001.html>


More information about the gstreamer-devel mailing list