[gst-devel] EOS only on SIGINT and not on socket error causes file created by 'filesink' element to be invalid

[Robert Krakora]

On Mon, Sep 27, 2010 at 1:07 PM, Robert Krakora <
rob.krakora at messagenetsystems.com> wrote:

> Hello All,
>
> When I execute this pipeline from the command line...
>
>  gst-launch -e rtspsrc location=rtsp://192.168.1.211:8109/camera.sdp !
> rtpmp4vdepay ! mpeg4videoparse ! mp4mux ! filesink location=myfile
>
> ...and send a SIGINT to the process I get a file that is playable because I
> specified the '-e' which indicates that EOS on shutdown.
>
> However, if I execute the same pipeline from the command line and remove
> the RTSP server (i.e. force a socket error) the process exits without
> performing an EOS on shutdown.  A quick look at the code in "gst-launch.c"
> confirmed my suspicion that EOS on shutdown is only performed on a SIGINT.
> What if my application has recorded valuable video data and the network goes
> down, does this mean I have lost all of that data since the file will not be
> viewable due to the absence of EOS on shutdown processing on anything that
> is not a SIGINT?
>
> Thanks in advance.
>
> Best Regards,
>
> --
> Rob Krakora
> Senior Software Engineer
> MessageNet Systems
> 101 East Carmel Dr. Suite 105
> Carmel, IN 46032
> (317)566-1677 Ext. 206
> (317)663-0808 Fax
>



-- 
Rob Krakora
Senior Software Engineer
MessageNet Systems
101 East Carmel Dr. Suite 105
Carmel, IN 46032
(317)566-1677 Ext. 206
(317)663-0808 Fax
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20100927/758aadde/attachment.htm>