[Bug 754528] decklinkvideosink: Properly handle pipelines where the running time does not start around 0
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Wed Sep 9 07:01:36 PDT 2015
https://bugzilla.gnome.org/show_bug.cgi?id=754528
Sebastian Dröge (slomo) <slomo at coaxion.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|git master |1.5.91
--- Comment #6 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
commit b6498c32f3971bffbc4424353264932e7c47a7fc
Author: Sebastian Dröge <sebastian at centricular.com>
Date: Thu Sep 3 16:36:57 2015 +0300
decklinkvideosink: Handle pipelines where the running time does not start
around 0 properly
We were converting all times to our internal running times, that is the
time
the sink itself spent in PLAYING already. But forgot to do that for the
running time calculated from the buffer timestamps. As such, all buffers
were
scheduled much later if the pipeline's running time did not start at 0.
This happens for example if a base time is explicitly set on the pipeline.
https://bugzilla.gnome.org/show_bug.cgi?id=754528
--
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