[Bug 750574] netclientclock: Make the clock a wrapper clock around an internal clock
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Tue Jun 9 01:04:11 PDT 2015
https://bugzilla.gnome.org/show_bug.cgi?id=750574
Sebastian Dröge (slomo) <slomo at coaxion.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|git master |1.5.1
--- Comment #5 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
commit 59d916a071e445ece94b7971263f272d69da43e4
Author: Sebastian Dröge <sebastian at centricular.com>
Date: Mon Jun 8 17:10:56 2015 +0200
netclientclock: Use the new GST_CLOCK_FLAG_NEEDS_STARTUP_SYNC flag
https://bugzilla.gnome.org/show_bug.cgi?id=750574
commit 558c0b97fc8b9ffe5a39563da72d9e29a511aa14
Author: Sebastian Dröge <sebastian at centricular.com>
Date: Mon Jun 8 17:04:55 2015 +0200
netclientclock: Make the clock a wrapper clock around an internal clock
The internal clock is only used for slaving against the remote clock, while
the user-facing GstClock can be additionally slaved to another clock if
desired. By default, if no master clock is set, this has exactly the same
behaviour as before. If a master clock is set (which was not allowed
before),
the user-facing clock is reporting the remote clock as internal time and
slaves this to the master clock.
This also removes the weirdness that the internal time of the
netclientclock
was always the system clock time, and not the remote clock time.
https://bugzilla.gnome.org/show_bug.cgi?id=750574
--
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