[Bug 383102] [0.11] Rethink pad_blocking

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=383102
  GStreamer | gstreamer (core) | git

--- Comment #12 from Wim Taymans <wim.taymans at gmail.com> 2011-05-18 17:03:50 UTC ---
(In reply to comment #11)
> How is pad blocking in 0.11 different from probes? Apart from having a more
> annoying API ?

What do you mean? probes and pad block are completely different things now.

Probes lets you see the data and events that pass (both upstream and
downstream) by triggering a signal. There is limited support for modifying the
data. There is no support for blocking the dataflow in a way that works with
flushing events. All callbacks are called from the streaming thread. Multiple
probes can be installed on a pad.

Pad blocking is to block the dataflow, only works on downstream events. Has
support for blocking that works nicely with flushes. There is no support for
looking at the blocked item nor modifying it. Only one block can be installed
on a pad. The block can be handled from another thread.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.