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.
This commit is contained in:
Mark Nauwelaerts 2014-03-22 17:07:46 +01:00
parent 9a30726226
commit 3414e3d0b9

View file

@ -4520,20 +4520,6 @@ pause:
gst_element_no_more_pads (GST_ELEMENT (demux)); 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) { if (demux->common.segment.flags & GST_SEEK_FLAG_SEGMENT) {
gint64 stop; gint64 stop;