GstEventType lists the standard event types that can be sent in a pipeline.
The custom event types can be used for private messages between elements that can't be expressed using normal GStreamer buffer passing semantics. Custom events carry an arbitrary gstreamer.Structure
Specific custom events are distinguished by the name of the structure.
Start a flush operation. This event clears all data from the pipeline and unblock all streaming threads.
Stop a flush operation. This event resets the running-time of the pipeline.
Event to mark the start of a new stream. Sent before any other serialized event and only sent at the start of a new stream, not after flushing seeks.
gstreamer.Caps event. Notify the pad of a new media type.
A new media segment follows in the dataflow. The segment events contains information for clipping buffers and converting buffer timestamps to running-time and stream-time.
A new gstreamer.StreamCollection is available (Since 1.10)
A new set of metadata tags has been found in the stream.
Notification of buffering requirements. Currently not used yet.
An event that sinks turn into a message. Used to send messages that should be emitted in sync with rendering.
Indicates that there is no more data for the stream group ID in the message. Sent before EOS in some instances and should be handled mostly the same. (Since 1.10)
End-Of-Stream. No more data is to be expected to follow without either a STREAM_START event, or a FLUSH_STOP and a SEGMENT event.
An event which indicates that a new table of contents (TOC) was found or updated.
An event which indicates that new or updated encryption information has been found in the stream.
Marks the end of a segment playback.
Marks a gap in the datastream.
A quality message. Used to indicate to upstream elements that the downstream elements should adjust their processing rate.
A request for a new playback position and rate.
Navigation events are usually used for communicating user requests, such as mouse or keyboard movements, to upstream elements.
Notification of new latency adjustment. Sinks will use the latency information to adjust their synchronisation.
A request for stepping through the media. Sinks will usually execute the step operation.
A request for upstream renegotiating caps and reconfiguring.
A request for a new playback position based on TOC entry's UID.
A request to select one or more streams (Since 1.10)
Upstream custom event
Downstream custom event that travels in the data flow.
Custom out-of-band downstream event.
Custom sticky downstream event.
Custom upstream or downstream event. In-band when travelling downstream.
Custom upstream or downstream out-of-band event.