Value | Meaning |
---|---|
INVALID0 | invalid probe type |
IDLE1 | probe idle pads and block while the callback is called |
BLOCK2 | probe and block pads |
BUFFER16 | probe buffers |
BUFFER_LIST32 | probe buffer lists |
EVENT_DOWNSTREAM64 | probe downstream events |
EVENT_UPSTREAM128 | probe upstream events |
EVENT_FLUSH256 | probe flush events. This probe has to be explicitly enabled and is not included in the @@GST_PAD_PROBE_TYPE_EVENT_DOWNSTREAM or @@GST_PAD_PROBE_TYPE_EVENT_UPSTREAM probe types. |
QUERY_DOWNSTREAM512 | probe downstream queries |
QUERY_UPSTREAM1024 | probe upstream queries |
PUSH4096 | probe push |
PULL8192 | probe pull |
BLOCKING3 | probe and block at the next opportunity, at data flow or when idle |
DATA_DOWNSTREAM112 | probe downstream data (buffers, buffer lists, and events) |
DATA_UPSTREAM128 | probe upstream data (events) |
DATA_BOTH240 | probe upstream and downstream data (buffers, buffer lists, and events) |
BLOCK_DOWNSTREAM114 | probe and block downstream data (buffers, buffer lists, and events) |
BLOCK_UPSTREAM130 | probe and block upstream data (events) |
EVENT_BOTH192 | probe upstream and downstream events |
QUERY_BOTH1536 | probe upstream and downstream queries |
ALL_BOTH1776 | probe upstream events and queries and downstream buffers, buffer lists, events and queries |
SCHEDULING12288 | probe push and pull |
The different probing types that can occur. When either one of @GST_PAD_PROBE_TYPE_IDLE or @GST_PAD_PROBE_TYPE_BLOCK is used, the probe will be a blocking probe.