[gstreamer-bugs] [Bug 635001] New: basesink: fix position reporting in PAUSED

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=635001
  GStreamer | gstreamer (core) | git

           Summary: basesink: fix position reporting in PAUSED
    Classification: Desktop
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: wingo at pobox.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


Currently, if you play a stream at e.g. 3x speed, query the position, pause the
pipeline, then query the position again, the second position is earlier than
the first. This is pretty bogus; in my app that results in time seemingly going
backwards a bit when playback resumes after a flushing seek to adjust rate back
to 1.0, but to the same timestamp.

The solution is to unify the logic for basesink position queries in PAUSED and
PLAYING. In PAUSED instead of using the base time and the clock, given that we
have neither, we use the start_time instead, in combination with the current
segment.

The two attached patches implement this refactoring.

-- 
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.