[gstreamer-bugs] [Bug 581460] New: [baseaudiosrc] Reusing audio source leads to null timestamps on first buffers

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

  GStreamer | gst-plugins-base | Ver: git
           Summary: [baseaudiosrc] Reusing audio source leads to null
                    timestamps on first buffers
           Product: GStreamer
           Version: git
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: mail at renestadler.de
         QAContact: gstreamer-bugs at lists.sourceforge.net
                CC: ensonic at sonicpulse.de
     GNOME version: Unspecified
   GNOME milestone: Unspecified


When reusing a pulsesrc (or alsasrc) element (PLAYING->READY->PLAYING cycle),
starting from the second time, the timestamps of the first couple buffers are
0. It makes no difference to set the state to NULL instead of READY.

I added some extra logging to gstbaseaudiosrc.c which shows that the timestamps
are clamped to 0 because they are smaller than the basetime. Attaching test
program, small patch for extra logging and logs.

Not sure how to fix this, maybe the basetime is a bit incorrect and the
internal timestamps from the ringbuffer/clock as well, or maybe this is
expected and the buffers should be dropped. Or should the state change cycle
reset everything back to 0 after all?


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