Sets our main struct and passes it to the parent class.
Create a new buffersize event. The event is sent downstream and notifies elements that they should provide a buffer of the specified dimensions.
Create a new CAPS event for @caps. The caps event can only travel downstream synchronized with the buffer flow and contains the format of the buffers that will follow after the event.
Create a new custom-typed event. This can be used for anything not handled by other event-specific functions to pass an event to another element.
Allocate a new flush stop event. The flush stop event can be sent upstream and downstream and travels serialized with the dataflow. It is typically sent after sending a FLUSH_START event to make the pads accept data again.
Create a new GAP event. A gap event can be thought of as conceptually equivalent to a buffer to signal that there is no data for a certain amount of time. This is useful to signal a gap to downstream elements which may wait for data, such as muxers or mixers or overlays, especially for sparse streams such as subtitle streams.
Create a new latency event. The event is sent upstream from the sinks and notifies elements that they should add an additional @latency to the running time before synchronising against the clock.
Create a new navigation event from the given description.
Creates a new event containing information specific to a particular protection system (uniquely identified by @system_id), by which that protection system can acquire key(s) to decrypt a protected stream.
Allocate a new qos event with the given values. The QOS event is generated in an element that wants an upstream element to either reduce or increase its rate because of high/low CPU load or other resource usage such as network performance or throttling. Typically sinks generate these events for each buffer they receive.
Create a new reconfigure event. The purpose of the reconfigure event is to travel upstream and make elements renegotiate their caps or reconfigure their buffer pools. This is useful when changing properties on elements or changing the topology of the pipeline.
Allocate a new seek event with the given parameters.
Create a new SEGMENT event for @segment. The segment event can only travel downstream synchronized with the buffer flow and contains timing information and playback properties for the buffers that will follow.
Create a new segment-done event. This event is sent by elements that finish playback of a segment as a result of a segment seek.
Allocate a new select-streams event.
Create a new sink-message event. The purpose of the sink-message event is to instruct a sink to post the message contained in the event synchronized with the stream.
Create a new step event. The purpose of the step event is to instruct a sink to skip @amount (expressed in @format) of media. It can be used to implement stepping through the video frame by frame or for doing fast trick modes.
Create a new STREAM_COLLECTION event. The stream collection event can only travel downstream synchronized with the buffer flow.
Create a new Stream Group Done event. The stream-group-done event can only travel downstream synchronized with the buffer flow. Elements that receive the event on a pad should handle it mostly like EOS, and emit any data or pending buffers that would depend on more data arriving and unblock, since there won't be any more data.
Create a new STREAM_START event. The stream start event can only travel downstream synchronized with the buffer flow. It is expected to be the first event that is sent for a new stream.
Generates a metadata tag event from the given @taglist.
Generate a TOC event from the given @toc. The purpose of the TOC event is to inform elements that some kind of the TOC was found.
Parses a segment @event and copies the #GstSegment into the location given by @segment.
Get the main Gtk struct
Retrieve the accumulated running time offset of the event.
Retrieve the sequence number of a event.
the main Gtk struct as a void*
Access the structure of the event.
Checks if @event has the given @name. This function is usually used to check the name of a custom event.
Get the format, minsize, maxsize and async-flag in the buffersize event.
Get the caps from @event. The caps remains valid as long as @event remains valid.
Parse the FLUSH_STOP event and retrieve the @reset_time member.
Extract timestamp and duration from a new GAP event.
Get the latency in the latency event.
Parses an event containing protection system specific information and stores the results in @system_id, @data and @origin. The data stored in @system_id, @origin and @data are valid until @event is released.
Get the type, proportion, diff and timestamp in the qos event. See gst_event_new_qos() for more information about the different QoS values.
Parses a seek @event and stores the results in the given result locations.
Parses a segment @event and stores the result in the given @segment location. @segment remains valid only until the @event is freed. Don't modify the segment and make a copy if you want to modify it or store it for later use.
Extracts the position and format from the segment done message.
Parse the SELECT_STREAMS event and retrieve the contained streams.
Parse the sink-message event. Unref @msg after usage.
Parse the step event.
Parse a stream-start @event and extract the #GstStream from it.
Retrieve new #GstStreamCollection from STREAM_COLLECTION event @event.
Parse a stream-group-done @event and store the result in the given @group_id location.
Parse a stream-id @event and store the result in the given @stream_id location. The string stored in @stream_id must not be modified and will remain valid only until @event gets freed. Make a copy if you want to modify it or store it for later use.
Parses a tag @event and stores the results in the given @taglist location. No reference to the taglist will be returned, it remains valid only until the @event is freed. Don't modify or free the taglist, make a copy if you want to modify it or store it for later use.
Parse a TOC @event and store the results in the given @toc and @updated locations.
Parse a TOC select @event and store the results in the given @uid location.
All streams that have the same group id are supposed to be played together, i.e. all streams inside a container file should have the same group id but different stream ids. The group id should change each time the stream is started, resulting in different group ids each time a file is played for example.
Set the running time offset of a event. See gst_event_get_running_time_offset() for more information.
Set the sequence number of a event.
Set the @stream on the stream-start @event
Get a writable version of the structure.
Create a new EOS event. The eos event can only travel downstream synchronized with the buffer flow. Elements that receive the EOS event on a pad can return UNEXPECTED as a GstFlowReturn when data after the EOS event arrives. The EOS event will travel down to the sink elements in the pipeline which will then post the GST_MESSAGE_EOS on the bus after they have finished playing any buffered data. When all sinks have posted an EOS message, the EOS message is forwarded to the application.
Allocate a new flush start event. The flush start event can be send upstream and downstream and travels out-of-bounds with the dataflow. It marks pads as being in a WRONG_STATE to process more data. Elements unlock and blocking functions and exit their streaming functions as fast as possible. This event is typically generated after a seek to minimize the latency after the seek.
Generate a TOC select event with the given uid. The purpose of the TOC select event is to start playback based on the TOC's entry with the given uid.
Gets the #GstEventTypeFlags associated with @type.
Get a printable name for the given event type. Do not modify or free.
Get the unique quark for the given event type.
The event class provides factory methods to construct events for sending and functions to query (parse) received events.
Events are usually created with gst_event_new_*() which takes event-type specific parameters as arguments. To send an event application will usually use gst_element_send_event() and elements will use gst_pad_send_event() or gst_pad_push_event(). The event should be unreffed with gst_event_unref() if it has not been sent.
Events that have been received can be parsed with their respective gst_event_parse_*() functions. It is valid to pass %NULL for unwanted details.
Events are passed between elements in parallel to the data stream. Some events are serialized with buffers, others are not. Some events only travel downstream, others only upstream. Some events can travel both upstream and downstream.
The events are used to signal special conditions in the datastream such as EOS (end of stream) or the start of a new stream-segment. Events are also used to flush the pipeline of any pending data.
Most of the event API is used inside plugins. Applications usually only construct and use seek events. To do that gst_event_new_seek() is used to create a seek event. It takes the needed parameters to specify seeking time and mode. |[<!-- language="C" --> GstEvent *event; gboolean result; ... // construct a seek event to play the media from second 2 to 5, flush // the pipeline to decrease latency. event = gst_event_new_seek (1.0, GST_FORMAT_TIME, GST_SEEK_FLAG_FLUSH, GST_SEEK_TYPE_SET, 2 * GST_SECOND, GST_SEEK_TYPE_SET, 5 * GST_SECOND); ... result = gst_element_send_event (pipeline, event); if (!result) g_warning ("seek failed"); ... ]|