NetTimeProvider/NetClientClock issue

[danny.smith]

Thanks for replying!

I put the pipeline to NULL state and the unref the pipeline and
netclientclock. Thereafter I create a new pipeline and netclientclock. This
new pipeline does not start if the sender which provides the time-provider
has rebooted and has started a new time-provider (on the same address and
port). I only get the 'synced'-signal on the first netclientclock I created.
All netclientclocks created thereafter are already in "synced" state, and I
cannot get them to resync to the new time-provider.

Regards,
Danny



--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/NetTimeProvider-NetClientClock-issue-tp4682456p4682458.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.