rtpbin/session: Add new ntp-time-source property and deprecate use-pipeline-clock...
authorSebastian Dröge <sebastian@centricular.com>
Fri, 12 Jun 2015 21:29:19 +0000 (23:29 +0200)
committerSebastian Dröge <sebastian@centricular.com>
Fri, 12 Jun 2015 21:35:42 +0000 (23:35 +0200)
commitdc513eb9498a7d3d482ccafa874486fc88419654
tree772f6b5dde7c962e13777feb6d2a40644b05ad46
parent74dcd85de4a553c32d46d1786f572514a4ab1b8d
rtpbin/session: Add new ntp-time-source property and deprecate use-pipeline-clock property

The new property allows to select the time source that should be used for the
NTP time in RTCP packets. By default it will continue to calculate the NTP
timestamp (1900 epoch) based on the realtime clock. Alternatively it can use
the UNIX timestamp (1970 epoch), the pipeline's running time or the pipeline's
clock time. The latter is especially useful for synchronizing multiple
receivers if all of them share the same clock.

If use-pipeline-clock is set to TRUE, it will override the ntp-time-source
setting and continue to use the running time plus 70 years. This is only kept
for backwards compatibility.
gst/rtpmanager/gstrtpbin.c
gst/rtpmanager/gstrtpbin.h
gst/rtpmanager/gstrtpsession.c
gst/rtpmanager/gstrtpsession.h