From 1493f4a334f45446b3e81646b7db02c17afc2064 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Sebastian=20Dr=C3=B6ge?= Date: Wed, 28 Oct 2015 13:04:25 +0200 Subject: [PATCH] pad: Document the order in which pad probes are called https://bugzilla.gnome.org/show_bug.cgi?id=757197 --- gst/gstpad.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/gst/gstpad.c b/gst/gstpad.c index 8921213..f5630da 100644 --- a/gst/gstpad.c +++ b/gst/gstpad.c @@ -1324,6 +1324,13 @@ cleanup_hook (GstPad * pad, GHook * hook) * Be notified of different states of pads. The provided callback is called for * every state that matches @mask. * + * Probes are called in groups: First GST_PAD_PROBE_TYPE_BLOCK probes are + * called, then others, then finally GST_PAD_PROBE_TYPE_IDLE. The only + * exception here are GST_PAD_PROBE_TYPE_IDLE probes that are called + * immediately if the pad is already idle while calling gst_pad_add_probe(). + * In each of the groups, probes are called in the order in which they were + * added. + * * Returns: an id or 0 if no probe is pending. The id can be used to remove the * probe with gst_pad_remove_probe(). When using GST_PAD_PROBE_TYPE_IDLE it can * happen that the probe can be run immediately and if the probe returns -- 2.7.4