the default accept-caps handler will check it the caps intersect the query-caps result instead of checking for a subset. This is interesting for parsers that can accept incompletely specified caps.
the default accept-caps handler will use the template pad caps instead of query caps to compare with the accept caps. Use this in combination with Gst.PadFlags.ACCEPT_INTERSECT. (Since: 1.6)
is dataflow on a pad blocked
is pad currently blocking on a buffer or event
is pad in EOS state
the pad is using fixed caps. This means that once the caps are set on the pad, the default caps query function will only return those caps.
is pad flushing
offset to define more flags
ensure that there is a parent object before calling into the pad callbacks.
the pad should be reconfigured/renegotiated. The flag has to be unset manually after reconfiguration happened.
the pad has pending events
the default query handler will forward allocation queries to the internally linked pads instead of discarding them.
the default event and query handler will forward all events and queries to the internally linked pads instead of discarding them.
the default query handler will forward scheduling queries to the internally linked pads instead of discarding them.
Pad state flags