disable netclientclock

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

disable netclientclock

Johannes Bauer-2
Hi!

I am using a netclock for mp3 server-client synchronisation.
It works good so far, the only problem is I want to disable the clock without destroying the pipeline.
So, at my client, after the stream I change the pipeline clock to the standard clock and try to unref the clock, but it still is referenced.

GstClock *net_clock = gst_pipeline_get_clock(GST_PIPELINE(call.pipeline));
gst_element_set_state(call.pipeline, GST_STATE_NULL);
gst_pipeline_auto_clock(GST_PIPELINE(call.pipeline));
gst_object_unref(net_clock);
g_print("clock name: %s refcounf: %d\n",net_clock->object.name,net_clock->object.object.ref_count);

I still get the output:

clock name: netclientclock0 refcount: 14

I checked the pipeline clock, but it really is the standard clock.

Finally, after unrefing the whole pipeline the refcount is 0, but I still see the syncing messages to the server and in wireshark.

So how can I disable the netclock synchronisation?

Kind regards
JB

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: disable netclientclock

Sebastian Dröge-3
On Di, 2016-07-26 at 09:02 +0200, Johannes Bauer wrote:
> [...]
> I checked the pipeline clock, but it really is the standard clock.
>
> Finally, after unrefing the whole pipeline the refcount is 0, but I
> still see the syncing messages to the server and in wireshark.
>
> So how can I disable the netclock synchronisation?

The code you showed should work. Can you file a bug with a testcase
that reproduces the problem? Also which GStreamer version are you
using?

--
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

signature.asc (968 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: disable netclientclock

Johannes Bauer-2
I will hopefully get to do that in the next weeks.

However wouldnt it be possible to set the netclientclock at the sender side to wallclocktime (utc), so it would not matter that the client clocks keep synchronizing even after the stream ended, because the clock always keeps going.
If a new stream is started the clocks should still be more or less in sync if I always set them to wallclocktime before the stream starts at the sender.

However I am not sure how to set the clock time.
There seems to be external and internal time of the gst system clock.

How can I make sure to set it to the wallclocktime and how can I tell the clients to use exactly that clock?
should the "ntp-time-source" on both rtpbins be set to 3?

Kind regards
JB


2016-07-27 8:24 GMT+02:00 Sebastian Dröge <[hidden email]>:
On Di, 2016-07-26 at 09:02 +0200, Johannes Bauer wrote:
> [...]
> I checked the pipeline clock, but it really is the standard clock.
>
> Finally, after unrefing the whole pipeline the refcount is 0, but I
> still see the syncing messages to the server and in wireshark.
>
> So how can I disable the netclock synchronisation?

The code you showed should work. Can you file a bug with a testcase
that reproduces the problem? Also which GStreamer version are you
using?

--
Sebastian Dröge, Centricular Ltd · http://www.centricular.com


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