clock issue

[Olivier Crête]

Hi,

You want to use gst_pipeline_use_clock() with a common clock (it can be
the system clock). If you want the timestamps on packets from both
pipeline to match, you also need to do gst_pipeline_set_base_time()
with the same value (0 is a good value). Then they will both use the
same clock. You can just use the system clock on both (obtain using
gst_system_clock_option() ).

Also, you should know that the V4L2 API doesn't expose any hardware
clocks but instead converts (or timestamps) everything using the
monotonic clock.



On Mon, 2019-08-19 at 03:39 -0500, IgalKroyter wrote:
> Hi,
> I wonder in which way both following commands are different
> *gst_clock_set_master* and *gst_pipeline_use_clock*?
> Let say that *v4l2 *is utilizing a HW clock while *alsasrc *is utilizing a
> different HW clock, which of the functions shoould be used to synchronize
> the *v4l2 *and *alsasrc *if both reside in different pipelines?
> 
> 
> 
> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
-- 
Olivier Crête
olivier.crete at collabora.com