Sebastian Dröge 558c0b97fc 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		2015-06-09 10:03:49 +02:00
..
base	basetransform: Add Since markers for new vfuncs	2015-06-08 19:33:23 +10:00
check	check: optionally check env var for us to make sure test env is set up	2015-04-23 15:54:08 +01:00
controller	timedvaluecontrolsource: Check that the only iter is the end iter in the GSequence	2015-05-16 13:08:06 +02:00
helpers	ptp: Ensure that not too much is read from or written to struct ifreq.ifr_name	2015-06-08 12:03:30 +02:00
net	netclientclock: Make the clock a wrapper clock around an internal clock	2015-06-09 10:03:49 +02:00
Makefile.am	Remove obsolete Android build cruft	2015-04-26 17:49:44 +01:00