GNOME Bugzilla – Bug 711269
systemclock: Add method to set the default system clock
Last modified: 2013-11-11 15:15:05 UTC
Created attachment 258776 [details] [review] systemclock: Add gst_system_clock_set_default This patch adds a new method: gst_system_clock_set_default It is used for setting the default system clock that is obtained through gst_system_clock_obtain() which is sometimes needed for unit testing, specifically for some RTP retransmission tests. This patch also includes a unit test for the new method.
In which use cases is the system clock used unconditionally instead of the pipeline clock? I mean, in which test can't you just force a specific clock on the pipeline to get the behaviour you want?
For bug #711270 which tests rtpsession, the rtpsession element has a call to gst_system_clock_obtain to handle RTP timeouts in a separate thread. It doesn't use the pipeline clock for that. A number of other RTP elements also have calls to gst_system_clock_obtain.
commit 02b64ee03bfcdcd75c8d405f99dd4a2f0f7df164 Author: Wim Taymans <wim.taymans@gmail.com> Date: Mon Nov 11 12:25:14 2013 +0100 systemclock: Add gst_system_clock_set_default Used for setting the default system clock that is obtained through gst_system_clock_obtain(), which is sometimes needed for unit testing. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=711269