[gstreamer-bugs] [Bug 523334] New: qtdemux loses on multiple segment seeks

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=523334

  GStreamer | gst-plugins-good | Ver: 0.10.7
           Summary: qtdemux loses on multiple segment seeks
           Product: GStreamer
           Version: 0.10.7
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: wingo at pobox.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Steps to reproduce:

 1. Set up a pipeline with qtdemux and multiple streams, for example with audio
and video. Set it to paused.
 2. Attach an asynchronous handler for message::segment-done. Configure the
stream for looping via sending it a flushing segment seek. Play the pipeline.
 3. When you get segment-done, send a non-flushing segment seek *to the
pipeline* setting start=0.

Expected results:

 1. Playback loops, accumulating the old segment.

Actual results:

Since we send the seek to the pipeline and not to only one sink, there is a
race condition betweeen the two seeks arriving at qtdemux, and the streaming
thread running in qtdemux. If the second seek arrives before the first seek's
new segment was pushed out, the accumulated play time is lost.

The fix is to be more clever in qtdemux. For now I will just send a seek to one
sink.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=523334.