[gst-devel] How can I catch the source of a message, sending one of my elements to the NULL state?

Zhao, Halley halley.zhao at intel.com
Sat Apr 24 04:07:08 CEST 2010

I met similar issue before, and add a queue before the sink could fix the issue.
I'm afraid the sink doesn't do "preroll" well lead to the issue.

-----Original Message-----
From: Tim-Philipp Müller [mailto:t.i.m at zen.co.uk] 
Sent: 2010年4月20日 21:07
To: gstreamer-devel at lists.sourceforge.net
Subject: Re: [gst-devel] How can I catch the source of a message, sending one of my elements to the NULL state?

On Tue, 2010-04-20 at 04:38 -0800, wl2776 wrote:

> I am manually building a pipeline.
> One of its elements, a videosink, always falls the the NULL state.
> My application doesn't send it there.
> Several graphviz dumps, created during the pipeline contruction, and debug
> messages from a bus watch, show that it changes states from READY to PAUSED,
> from PAUSED to READY, and then suddenly, from PLAYING to NULL.
> My application doesn't send the pipeline neither to the playing nor to the
> NULL state by that moment. 
> I'd like to catch, who does this (and thoroughly punish it :) )

Run your code in gdb/your favourite debugger and set a breakpoint on
whatever_video_sink_change_state()? (and continue if it's an upward
state change, obviously)


Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
gstreamer-devel mailing list
gstreamer-devel at lists.sourceforge.net

More information about the gstreamer-devel mailing list