How to Drop GST_EVENT_EOS and continue connecting

[vinod kesti]

Can you enable debug logs and check form which element the EOS is generated?


Sent from Yahoo Mail. Get the app 

    On Monday, 22 May, 2023 at 11:14:06 am GMT-5, Guru Govindan via gstreamer-devel <gstreamer-devel at lists.freedesktop.org> wrote:  
 
 Hi,
I am implementing a Gstreamer pipeline in rust to ingest rtsp feed from different cameras. I use the hlssink2 element to create manifest to view/store the video.

For some of the cameras, the hlssink2's splitmux element receives a GST_EVENT_EOS which results in the pipeline stopping.

This happens even if I add a bus.add_watch and capture the gst::MessageView::Eos(state_changed) event.


Is there a way to programatically block the EOS message and keep the rtsp connection on?

Here is an example pipeline for which I have a rust implementation.
gst-launch-1.0 hlssink2 name=ingest1 playlist-length=5 max-files=0 target-duration=10 \
send-keyframe-requests=true playlist-location=/tmp/manifest.m3u8 location=/tmp/video/%t.ts \
rtspsrc latency=100 location=<rtspurl> protocols=0x00000004 name=basesrc basesrc. ! rtph264depay ! tee name=t \
t.! queue  ! ingest1.video
I tried using errorignore and set the ignore-eos flag and convert-to=0. I used it right after rtspsrc element and right before hlssink2. However this seems to come from splitmuxsink inside hlssink2.

Best Regards,Guru  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20230523/5a104b5d/attachment.htm>