From 3414e3d0b9d5c6de100865dfc7c2b26b5a45c007 Mon Sep 17 00:00:00 2001 From: Mark Nauwelaerts Date: Sat, 22 Mar 2014 17:07:46 +0100 Subject: [PATCH] matroskademux: segment closing not needed in 1.x ... as sender should keep track of segment base accumulation. Rather, it may have some adverse effects as a spurious segment event, e.g. in collectpads. --- gst/matroska/matroska-demux.c | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/gst/matroska/matroska-demux.c b/gst/matroska/matroska-demux.c index 68f428c815..1d867774c1 100644 --- a/gst/matroska/matroska-demux.c +++ b/gst/matroska/matroska-demux.c @@ -4520,20 +4520,6 @@ pause: gst_element_no_more_pads (GST_ELEMENT (demux)); } - /* Close the segment, i.e. update segment stop with the duration - * if no stop was set */ - if (GST_CLOCK_TIME_IS_VALID (demux->last_stop_end) && - !GST_CLOCK_TIME_IS_VALID (demux->common.segment.stop) && - GST_CLOCK_TIME_IS_VALID (demux->common.segment.start) && - demux->last_stop_end > demux->common.segment.start) { - GstSegment segment = demux->common.segment; - GstEvent *event; - - segment.stop = demux->last_stop_end; - event = gst_event_new_segment (&segment); - gst_matroska_demux_send_event (demux, event); - } - if (demux->common.segment.flags & GST_SEEK_FLAG_SEGMENT) { gint64 stop;