GNOME Bugzilla – Bug 640637
Camerabin has warning: Internal GStreamer error: clock problem.
Last modified: 2011-05-01 12:42:35 UTC
Created attachment 179370 [details] [review] Handle upstream events when select-all is set When used with clutter-gst sink or with ximagesink, camerabin posts the warning: "Internal GStreamer error: clock problem.". Aditional debug info: "gstbin.c(2375): gst_bin_do_latency_func (): /GstCameraBin:camerabin: Failed to configure latency of 0:00:00.000000000" This is because input-selector doesn't handle upstream events when select-all is set. The warning doesn't occur with xvimagesink because this sink doesn't forward the latency event upstream, so it never reaches input-selector. This patch forwards the event to all sink-pads when select-all is set. It succeeds if any of the pads does, because when select-all is set the pads that are connected to input-selector sink pads might not be active and not handle the event. This affects only the input-selector copy in camerabin.
Created attachment 179954 [details] [review] Handle upstream events when select-all is set Update handling GST_ITERATOR_RESYNC and GST_ITERATOR_ERROR.
I see no harm in this as it only targets the internal camerabin input-selector. How would this work for the core input-selector?
Since the core input-selector doesn't have a select-all property anymore, I think it doesn't have the problem I'm trying to solve here.
Looks good to me. I'll push it after some testing.
Pushed with small corrections (don't leak the element-ref, avoid cast check when unreffing the pad). commit 2522a672a9a841a44ff4e0b20c7372092fd61010 Author: Luciana Fujii Pontello <luciana@fujii.eti.br> Date: Wed Jan 26 11:49:48 2011 -0200 camerabin: Events with select-all in input-selector When select-all was set, input-selector wasn't handling upstream events. Now input-selector forwards the event to all of its sink pads. This changes the input-selector internal to camerabin until it is replaced with a better solution.
*** Bug 645280 has been marked as a duplicate of this bug. ***
*** Bug 649067 has been marked as a duplicate of this bug. ***