Gstreamer net clock syncronization

[andeb91]

Hi everybody,

I have a central unit that manages all devices connected with. With the
instruction gst_net_time_provider_new (clock, ip, port) I create in the
central unit a global net clock where other devices can sync.
On devices I connect to this global net clock with the instruction clock =
gst_net_client_clock_new(NULL, ip, port, 0); and I sync with it with the
instruction gst_clock_wait_for_sync(clock, GST_CLOCK_TIME_NONE).

Everything seems going well, all devices are synced until I reboot the
central unit and then everything is not synced if I don't reboot the device
applications too. It seems that on devices there is a cache that avoid to
re-sync the clock if the ip and the port is the same.

Can someone confirm my hypothesis?
Can someone help me to clean this kind of cache to re-sync clock also if the
ip and the port are always the same? (if I change port or IP, clock is
syncing..)

Thanks in advance,
Andrea



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Nicolas Dufresne-5]

Le mardi 28 novembre 2017 à 01:45 -0700, andeb91 a écrit :

> I have a central unit that manages all devices connected with. With the
> instruction gst_net_time_provider_new (clock, ip, port) I create in the
> central unit a global net clock where other devices can sync.
> On devices I connect to this global net clock with the instruction clock =
> gst_net_client_clock_new(NULL, ip, port, 0); and I sync with it with the
> instruction gst_clock_wait_for_sync(clock, GST_CLOCK_TIME_NONE).
>
> Everything seems going well, all devices are synced until I reboot the
> central unit and then everything is not synced if I don't reboot the device
> applications too. It seems that on devices there is a cache that avoid to
> re-sync the clock if the ip and the port is the same.
>
> Can someone confirm my hypothesis?
> Can someone help me to clean this kind of cache to re-sync clock also if the
> ip and the port are always the same? (if I change port or IP, clock is
> syncing..)

Seems like a potential and plausible corner case that might have never
been tested. This could be simulated in a unit test, but killing the
clock server and then restarting it with an backward offset.

Nicolas
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel