From 6d30b82054220d4eea03b2914ff668d93d68601d Mon Sep 17 00:00:00 2001 From: Edward Hervey Date: Tue, 7 Jan 2025 09:31:26 +0100 Subject: [PATCH] splitmuxsrc: Ensure only a single stream-start event is pushed Since we are simulating a single output, we want to ensure only a single stream-start is pushed downstream. We do *not* want to send a (potentially) new stream start event after flushing (like after seeks). Fixes https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/4146 Part-of: --- subprojects/gst-plugins-good/gst/multifile/gstsplitmuxsrc.c | 1 - 1 file changed, 1 deletion(-) diff --git a/subprojects/gst-plugins-good/gst/multifile/gstsplitmuxsrc.c b/subprojects/gst-plugins-good/gst/multifile/gstsplitmuxsrc.c index df0ddc42db..8d9a162eeb 100644 --- a/subprojects/gst-plugins-good/gst/multifile/gstsplitmuxsrc.c +++ b/subprojects/gst-plugins-good/gst/multifile/gstsplitmuxsrc.c @@ -1489,7 +1489,6 @@ gst_splitmux_push_flush_stop (GstSplitMuxSrc * splitmux, guint32 seqnum) gst_event_ref (e); gst_pad_push_event (GST_PAD_CAST (target), e); target->sent_caps = FALSE; - target->sent_stream_start = FALSE; target->sent_segment = FALSE; } SPLITMUX_SRC_PADS_RUNLOCK (splitmux);