GstMessageType

an undefined message

end-of-stream reached in a pipeline. The application will only receive this message in the PLAYING state and every time it sets a pipeline to PLAYING that is in the EOS state. The application can perform a flushing seek in the pipeline, which will undo the EOS state again.

an error occurred. When the application receives an error message it should stop playback of the pipeline and not assume that more data will be played.

a warning occurred.

an info message occurred

a tag was found.

the pipeline is buffering. When the application receives a buffering message in the PLAYING state for a non-live pipeline it must PAUSE the pipeline until the buffering completes, when the percentage field in the message is 100%. For live pipelines, no action must be performed and the buffering percentage can be used to inform the user about the progress.

a state change happened

an element changed state in a streaming thread. This message is deprecated.

a stepping operation finished.

an element notifies its capability of providing a clock. This message is used internally and never forwarded to the application.

The current clock as selected by the pipeline became unusable. The pipeline will select a new clock on the next PLAYING state change. The application should set the pipeline to PAUSED and back to PLAYING when this message is received.

a new clock was selected in the pipeline.

the structure of the pipeline changed. This message is used internally and never forwarded to the application.

status about a stream, emitted when it starts, stops, errors, etc..

message posted by the application, possibly via an application-specific element.

element-specific message, see the specific element's documentation

pipeline started playback of a segment. This message is used internally and never forwarded to the application.

pipeline completed playback of a segment. This message is forwarded to the application after all elements that posted @GST_MESSAGE_SEGMENT_START posted a GST_MESSAGE_SEGMENT_DONE message.

The duration of a pipeline changed. The application can get the new duration with a duration query.

Posted by elements when their latency changes. The application should recalculate and distribute a new latency.

Posted by elements when they start an ASYNC #GstStateChange. This message is not forwarded to the application but is used internally.

Posted by elements when they complete an ASYNC #GstStateChange. The application will only receive this message from the toplevel pipeline.

Posted by elements when they want the pipeline to change state. This message is a suggestion to the application which can decide to perform the state change on (part of) the pipeline.

A stepping operation was started.

A buffer was dropped or an element changed its processing strategy for Quality of Service reasons.

A progress message.

A new table of contents (TOC) was found or previously found TOC was updated.

Message to request resetting the pipeline's running time from the pipeline. This is an internal message which applications will likely never receive.

Message indicating start of a new stream. Useful e.g. when using playbin in gapless playback mode, to get notified when the next title actually starts playing (which will be some time after the URI for the next title has been set).

Message indicating that an element wants a specific context (Since 1.2)

Message indicating that an element created a context (Since 1.2)

Message is an extended message type (see below). These extended message IDs can't be used directly with mask-based API like gst_bus_poll() or gst_bus_timed_pop_filtered(), but you can still filter for GST_MESSAGE_EXTENDED and then check the result for the specific type. (Since 1.4)

Message indicating a #GstDevice was added to a #GstDeviceProvider (Since 1.4)

Message indicating a #GstDevice was removed from a #GstDeviceProvider (Since 1.4)

mask for all of the above messages.