[Bug 649369] basesrc: do not set first buffer timestamp to 0 for live sources

[GStreamer (bugzilla.gnome.org)]

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

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |t.i.m at zen.co.uk
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.10.34

--- Comment #4 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2011-05-12 17:16:43 UTC ---
I've pushed this now for the quick-fix 0.10.34 release (since we're doing one
anyway, we may just as well put this in):

 commit 03050fd71ddede6980440ec205678b068f84a738
 Author: Vincent Penquerc'h <vincent.penquerch at collabora.co.uk>
 Date:   Wed May 4 15:31:56 2011 +0300

    basesrc: do not set first buffer timestamp to 0 for live sources

    Doing so avoids a large timestamp gap between first and second buffer
    for live sources which take time to start up.
    The first buffer now has a "live" timestamp based on the running time,
    as other buffers do.

    https://bugzilla.gnome.org/show_bug.cgi?id=649369

Some more context:

<tpm> that basesrc is-live timestamp patch, what exactly does it actually fix?
(what elements?)
<v> my particular case was a shmsrc. It would emit its first buffer a while
after being started.
<v> The first buffer would get retimstamped to 0, and the second would have its
23 seconds timestamp left.

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