Package ch.bailu.gtk.gst
Schnittstelle PadProbeReturn
public interface PadProbeReturn
-
Feldübersicht
FelderModifizierer und TypFeldBeschreibungstatic final int
drop data in data probes.static final int
Data has been handled in the probe and will not be
forwarded further.static final int
normal probe return value.static final int
pass the data item in the block probe and block on the
next item.static final int
remove this probe, passing the data.
-
Felddetails
-
DROP
static final int DROPdrop data in data probes. For push mode this means that
the data item is not sent downstream. For pull mode, it means that
the data item is not passed upstream. In both cases, no other probes
are called for this item and %GST_FLOW_OK or %TRUE is returned to the
caller.- Siehe auch:
-
OK
static final int OKnormal probe return value. This leaves the probe in
place, and defers decisions about dropping or passing data to other
probes, if any. If there are no other probes, the default behaviour
for the probe type applies ('block' for blocking probes,
and 'pass' for non-blocking probes).- Siehe auch:
-
REMOVE
static final int REMOVEremove this probe, passing the data. For blocking probes
this will cause data flow to unblock, unless there are also other
blocking probes installed.- Siehe auch:
-
PASS
static final int PASSpass the data item in the block probe and block on the
next item. Note, that if there are multiple pad probes installed and
any probe returns PASS, the data will be passed.- Siehe auch:
-
HANDLED
static final int HANDLEDData has been handled in the probe and will not be
forwarded further. For events and buffers this is the same behaviour as
%GST_PAD_PROBE_DROP (except that in this case you need to unref the buffer
or event yourself). For queries it will also return %TRUE to the caller.
The probe can also modify the #GstFlowReturn value by using the
#GST_PAD_PROBE_INFO_FLOW_RETURN() accessor.
Note that the resulting query must contain valid entries.
Since: 1.6- Siehe auch:
-