The different message types that are available.
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 occured. Whe the application receives an error
message it should stop playback of the pipeline and not assume that more
data will be played.
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
an element changed state in a streaming thread. This message is deprecated
a framestep finished. This message is not yet implemented.
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.
A new clock was selected in the pipeline.
The structure of the pipeline changed. Not implemented yet.
STRUCTURE_CHANGE(1 << 12),
Status about a stream, emitted when it starts, stops, errors, etc.. Not implemented yet.
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
have posted a 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 pipeline will calculate
and distribute a new latency. Since: 0.10.12
Posted by elements when they start an ASYNC state
change. This message is not forwarded to the application but is used
internally. Since: 0.10.13.
Posted by elements when they complete an ASYNC state change. The application
will only receive this message from the toplevel pipeline. Since: 0.10.13
Gets the native integer value for this type.
- the native gstreamer value.
Gets the name of this message type.
- the name of the message type.
Gets a MessageType that corresponds to the native integer value.
type the native value of the type.
- a MessageType.
Gets a MessageType that corresponds to the name
name the gstreamer name of the type.
- a MessageType.
return type != null ? type : UNKNOWN;