[gst-devel] blocked glib idle/timeout

[Arnout Vandecappelle]

On Thursday 26 March 2009 09:53:59 Dan Taylor wrote:
> I may be overstressing this point, but the ONLY difference between a
> trial run that works, including the callbacks being run, and one in
> which the timeout is NEVER called (and the idle stops after a second) is
> that the program number given to the demultiplexer  exists in the stream
> or it doesn't.  It is even the same transport stream in the case of
> filesrc.

 When g_idle_... isn't called, this can only mean that the mainloop is blocked 
somewhere.  Maybe you can check with a debugger where it is blocked.  You 
could also check if any output produces, but I guess that when the program 
number doesn't exist there is no output anyway, right?

 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  D206 D44B 5155 DF98 550D  3F2A 2213 88AA A1C7 C933