[gstreamer-bugs] [Bug 597407] GstPipeline calculates base_time incorrectly when a new clock appears during PAUSED state

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Tue Oct 6 10:08:06 PDT 2009


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

Wim Taymans <wim.taymans> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO
                 CC|                            |wim.taymans at gmail.com

--- Comment #2 from Wim Taymans <wim.taymans at gmail.com> 2009-10-06 17:08:04 UTC ---
The running_time of the pipeline (time spent in PLAYING) is taken when going to
PAUSED. Then a new base_time is selected such that current clock time -
base_time gives the original running_time. If the current clock time is indeed
0, this will result in a big base_time.

I don't quite know how this would fail, the base time of an element is supposed
to be a signed int64, so the calculation should work. Maybe there is some
element that does some weird thing with the signed/unsigned value somewhere.

Can you give more info on the elements involved? or how to reproduce this
maybe.

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




More information about the Gstreamer-bugs mailing list