[Bug 661049] New: matroskademux: support seek with start_type NONE

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=661049
  GStreamer | gst-plugins-good | git

           Summary: matroskademux: support seek with start_type NONE
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: davidsf at axis.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=198407)
 View: https://bugzilla.gnome.org/attachment.cgi?id=198407
 Review: https://bugzilla.gnome.org/review?bug=661049&attachment=198407

support seek with start_type GST_SEEK_TYPE_NONE

We want to do a seek on a matroskademuxer that updates the stop position of the
current segment, but does not affect the start or the current playback. We seek
like this:

gst_event_new_seek (1.0, GST_FORMAT_TIME, GST_SEEK_FLAG_ACCURATE,
GST_SEEK_TYPE_NONE, -1, GST_SEEK_TYPE_SET, new_stop_time)

The current effect when we try this is that the demuxer restarts playback from
the start of the current segment, so buffers that have already been played are
played again. A newsegment event for closing the currently running segment is
sent out with start as the current start, and stop as the current last_stop (as
we expected). But then a newsegment is sent out with start as the current start
of the segment, and stop as the new end of the segment. We had expected the
start of the second newsegment event to be the same as the end of the first
newsegment event.

The attached proposed patch handles the following when start_type is
GST_SEEK_TYPE_NONE: let playback continue, and use the end of the first
newsegment event as the start of the second newsegment event.

When start_type is GST_SEEK_TYPE_NONE, gst_matroska_demux_move_to_entry is not
called. Furthermore, gst_message_new_segment_start is not called on segment
seeks. From the documentation we understood this as the correct behaviour.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.