Sets our main struct and passes it to the parent class
Create a new application-typed message. GStreamer will never create these messages; they are a gift from us to you. Enjoy.
Create a clock provide message. This message is posted whenever an element is ready to provide a clock or lost its ability to provide a clock (maybe because it paused or became EOS). This message is mainly used internally to manage the clock selection.
Create a clock lost message. This message is posted whenever the clock is not valid anymore. If this message is posted by the pipeline, the pipeline will select a new clock again when it goes to PLAYING. It might therefore be needed to set the pipeline to PAUSED and PLAYING again.
Create a new custom-typed message. This can be used for anything not handled by other message-specific functions to pass a message to the app. The structure field can be NULL.
Create a state change message. This message is posted whenever an element changed its state.
Create a new tag message. The message will take ownership of the tag list. The message is posted by elements that discovered a new taglist.
Create a new buffering message. This message can be posted by an element that needs to buffer data before it can continue processing. percent should be a value between 0 and 100. A value of 100 means that the buffering completed. When percent is < 100 the application should PAUSE a PLAYING pipeline. When percent is 100, the application can set the pipeline (back) to PLAYING. The application must be prepared to receive BUFFERING messages in the PREROLLING state and may only set the pipeline to PLAYING after receiving a message with percent set to 100, which can happen after the pipeline completed prerolling.
Create a new duration message. This message is posted by elements that know the duration of a stream in a specific format. This message is received by bins and is used to calculate the total duration of a pipeline. Elements may post a duration message with a duration of GST_CLOCK_TIME_NONE to indicate that the duration has changed and the cached duration should be discarded. The new duration can then be retrieved via a query.
The message is posted when elements completed an ASYNC state change.
Convenience macro to increase the reference count of the message.
the main Gtk struct as a void*
Access the structure of the message.
Extract the new_base_time from the async_start message. MT safe.
Extracts the buffering percent from the GstMessage. see also gst_message_new_buffering().
Extracts the lost clock from the GstMessage. The clock object returned remains valid until the message is freed. MT safe.
Extracts the clock and ready flag from the GstMessage. The clock object returned remains valid until the message is freed. MT safe.
Extracts the duration and format from the duration message. The duration might be GST_CLOCK_TIME_NONE, which indicates that the duration has changed. Applications should always use a query to retrieve the duration of a pipeline. MT safe.
Extracts the GError and debug string from the GstMessage. The values returned in the output arguments are copies; the caller must free them when done. MT safe.
Extracts the GError and debug string from the GstMessage. The values returned in the output arguments are copies; the caller must free them when done. MT safe.
Extracts the new clock from the GstMessage. The clock object returned remains valid until the message is freed. MT safe.
Extracts the position and format from the segment start message. MT safe.
Extracts the position and format from the segment start message. MT safe.
Extracts the old and new states from the GstMessage. MT safe.
Extracts the tag list from the GstMessage. The tag list returned in the output argument is a copy; the caller must free it when done. MT safe.
Extracts the GError and debug string from the GstMessage. The values returned in the output arguments are copies; the caller must free them when done. MT safe.
Get the src (the element that originated the message) of the message.
Get the structure.
Get the type of the message.
This message is posted by elements when they start an ASYNC state change. new_base_time is set to TRUE when the element lost its state when it was PLAYING.
Create a new eos message. This message is generated and posted in the sink elements of a GstBin. The bin will only forward the EOS message to the application if all sinks have posted an EOS message. MT safe.
Create a new element-specific message. This is meant as a generic way of allowing one-way communication from an element to an application, for example "the firewire cable was unplugged". The format of the message should be documented in the element's documentation. The structure field can be NULL. MT safe.
Create a new error message. The message will copy error and debug. This message is posted by element when a fatal event occured. The pipeline will probably (partially) stop. The application receiving this message should stop the pipeline. MT safe.
Create a new info message. The message will make copies of error and debug. MT safe. Since 0.10.12
This message can be posted by elements when their latency requirements have changed.
Create a new clock message. This message is posted whenever the pipeline selectes a new clock for the pipeline. MT safe.
Create a new segment done message. This message is posted by elements that finish playback of a segment as a result of a segment seek. This message is received by the application after all elements that posted a segment_start have posted the segment_done. MT safe.
Create a new segment message. This message is posted by elements that start playback of a segment as a result of a segment seek. This message is not received by the application but is used for maintenance reasons in container elements. MT safe.
Create a state dirty message. This message is posted whenever an element changed its state asynchronously and is used internally to update the states of container objects. MT safe.
Create a new warning message. The message will make copies of error and debug. MT safe.
Get a printable name for the given message type. Do not modify or free.
Get the unique quark for the given message type.
the main Gtk struct
Description Messages are implemented as a subclass of GstMiniObject with a generic GstStructure as the content. This allows for writing custom messages without requiring an API change while allowing a wide range of different types of messages. Messages are posted by objects in the pipeline and are passed to the application using the GstBus. The basic use pattern of posting a message on a GstBus is as follows: A GstElement usually posts messages on the bus provided by the parent container using gst_element_post_message(). Last reviewed on 2005-11-09 (0.9.4)