[gstreamer-bugs] [Bug 521761] New: gstaudioclock frozen the clock value until reaches latest 'last_time'

[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=521761

  GStreamer | gst-plugins-base | Ver: HEAD CVS
           Summary: gstaudioclock frozen the clock value until reaches
                    latest 'last_time'
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: blocker
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: edgard.lima at indt.org.br
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


After change the pipeline state back to NULL,
the 'last_time' value stored in the clock it not reset.

But, the audio base classes reset the number of samples played.

Then when setting the pipeline to PLAYING again, the clock value will be frozen
'cause the clock will always return MAX(last_time, time).

The solution implemented in attached patches do:

1- create a gst_clock_reset funcion
just to make it possible to set last_time to 0 again

2- calls gst_clock_reset, when uses gst_audio_clock is the clock provided, in
change_state function from NULL to READY.

I'm just waiting the reviews and OK to commit.

Thanks


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