[gst-devel] Catching signal interrupt on gst-launch

[sudarshan bisht]

Hi ,

 Are you sure that you have correctly implemented and registered
_change_state function in "tih264"  element ? Because that is the only
element introduced in first pipeline besides standard gstreamer
elements .


On Tue, Apr 20, 2010 at 6:20 AM, John Tobias <jtobias at viaas.com> wrote:
> Hi Guys,
> I have a problem running this command: gst-launch v4l2src ! tih264  !
> fakesink
> The gst-launch did not catch the signal interrupt when I hit the ctrl+c. The
> pipeline exited immediately instead of going through the _change_state
> transition of the pipeline.
> Then, I tried the gst-launch v4l2src ! fakesink, it works correctly.
> Setting pipeline to PAUSED ...
> Pipeline is live and does not need PREROLL ...
> Setting pipeline to PLAYING ...
> New clock: GstSystemClock
> <-- gst-launch detected the interrupt here..->
> Caught interrupt -- handling interrupt.
> Interrupt: Stopping pipeline ...
> Execution ended after 1710703481 ns.
> Setting pipeline to PAUSED ...
> Setting pipeline to READY ...
> clean stopped pipeline<6>
> Starting of vpfe_release...<6>
>  doing full release, started is 0
> Setting pipeline to NULL ...
> Freeing pipeline ...
> I don't understand why the gst-launch giving me two different behavior with
> regards to the signal handling.
> Can anyone tell me why I am getting different behavior?
> Thanks,
> John
> ------------------------------------------------------------------------------
> Download Intel&#174; 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.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>
>



-- 
Regards,

Sudarshan Bisht