[gst-devel] How to properly handle a disconnected (abruptly ended) input video stream?

Thomas Vander Stichele thomas at apestaart.org
Tue Mar 14 04:55:18 CET 2006

On Tue, 2006-03-14 at 13:21 +0100, Andy Wingo wrote:
> Hi,
> On Sun, 2006-03-12 at 16:02 +0100, Ola Theander wrote:
> > sometimes the application's user disconnects the
> > composite video cable without properly turn of the recoding in my
> > application.
> There is an element message posted to the bus when bus resets happen
> (i.e., when the set of nodes on the bus changes). You can catch it in
> your message handler. Can't recall what its name is tho, check the docs
> or gst-launch -m dv1394src ! fakesink when replugging. When you get the
> message you can do what you like, including setting the pipeline to NULL
> -- it should unlock properly.

Zaheer knows - he should reply :)

One thing he ran into is that the message happens on every bus reset, so
also when other devices get plugged/unplugged.  Do you think the element
should filter these, so that it specifically only messages for
disconnectcs/connects on its devices ? If not, what's a good way to
relate it to the actual device being used getting disconnected ?


Dave/Dina : future TV today ! - http://www.davedina.org/
<-*- thomas (dot) apestaart (dot) org -*->
If I'd rain for you
It would just be water
<-*- thomas (at) apestaart (dot) org -*->
URGent, best radio on the net - 24/7 ! - http://urgent.fm/

More information about the gstreamer-devel mailing list