[gstreamer-bugs] [Bug 574408] New: Adder element disregards timestamp of incoming 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=574408

  GStreamer | gst-plugins-base | Ver: 0.10.22
           Summary: Adder element disregards timestamp of incoming buffers.
           Product: GStreamer
           Version: 0.10.22
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: balachandran_c at rediffmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: 2.25/2.26
   GNOME milestone: Unspecified


Please describe the problem:
Adder resets the timestamp of buffers to zero on state change from ready to
pause. It disregards the timestamp of the incoming buffers. This causes
synchronisation problems when downstream elements (eg. alsasink) sync on the
clock. It results in having no audio.

Steps to reproduce:
1. Place an adder in a sink bin:=  queue2 ! adder ! alsasink.
2. Add this sink bin to a playing pipeline.
3. Link a playing source to this sink bin.

Actual results:
There is no audio written out to the soundcard, unless the "sync" property of
alsasink is set to false. If false, audio is output with a substantial latency.


Expected results:
Adder should be able to produce a stream that is playable by syncing elements
downstream. Audio is output when the adder is removed from the sink bin, the
same behavior is expected when the adder element is a part of the bin.

Does this happen every time?
Yes.

Other information:
This is because the timestamp of the input buffers are not considered in
computing the timestamp of the output buffer. Timestamp is set to zero
everytime the element changes state from READY to PAUSED.


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