[Bug 646397] rtpjitterbuffer base_time broken by commit f84b8a69

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=646397
  GStreamer | gst-plugins-good | git

Mark Nauwelaerts <mnauw> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.10.29

--- Comment #2 from Mark Nauwelaerts <mnauw at users.sourceforge.net> 2011-04-04 09:54:46 UTC ---
OK, so regression fixed by revert:

commit e5bcaa45e63a701be8f507efeb8cdcbd209ac54d
Author: Mark Nauwelaerts <mark.nauwelaerts at collabora.co.uk>
Date:   Mon Apr 4 11:35:59 2011 +0200

    Revert "jitterbuffer: reset element base_time upon flush"

    This reverts commit f84b8a69cba9c538f5546869cb4ef454ad5efb9d.

    Fixes bug #646397.

... and then solved the original problem (as described above) this way:

commit 226a7cb32e10cf057035348b616772bf539d2dc4
Author: Mark Nauwelaerts <mark.nauwelaerts at collabora.co.uk>
Date:   Mon Apr 4 11:27:29 2011 +0200

    rtspsrc: distribute new base_time to manager children following flush seek

    ... by forcing a state changed to PLAYING, which should otherwise be a
    no-op as elements should already be in that state.

    In particular, jitterbuffer needs new base_time as soon as possible to
perform
    proper timing (e.g. eos timeout handling) and can't wait for the new
base_time
    that will be distributed when the whole pipeline returns to PLAYING.

    See bug #646397.

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