GNOME Bugzilla – Bug 134227
[api] gst_clock_id_wait_async, wrong return code for default clock
Last modified: 2005-07-20 17:28:24 UTC
if one uses clock = gst_bin_get_clock (GST_BIN (thread)); clockId = gst_clock_new_periodic_id(clock, 0, GST_SECOND*1 ); gst_clock_id_wait_async(clockId, &clockFunc, NULL); then gst_clock_id_wait_async() returns GST_CLOCK_EARLY instead of GST_CLOCK_UNSUPPORTED when checking the flags of the clock via GST_CLOCK_FLAGS(clock) it reports 0 when setting a different clock e.g. gst_bin_use_clock(GST_BIN (thread), gst_system_clock_obtain()); then gst_clock_id_wait_async() returns GST_CLOCK_UNSUPPORTED
The behavior of the system clock is normal, it does not support async notifications. The behaviour of the other clock (most likely some audio clock) is not correct. It does support async notifications but it does not set the flags correctly. It returns _EARLY because there is no return value that says something like _ASYNC.
Wim, is this still a valid bug in 0.9?
There is a check for all possible clock wait functions that does not reproduce this problem anymore.
Reporting fixed.