GstEvent

Gst.Event

Gst.Event.prototype.new_buffer_size

function Gst.Event.prototype.new_buffer_size(format: Gst.Format, minsize: Number, maxsize: Number, async: Number): {
    // javascript wrapper for 'gst_event_new_buffer_size'
}

Create a new buffersize event. The event is sent downstream and notifies elements that they should provide a buffer of the specified dimensions.

When the async flag is set, a thread boundary is preferred.

Gst.Event.prototype.new_caps

function Gst.Event.prototype.new_caps(caps: Gst.Caps): {
    // javascript wrapper for 'gst_event_new_caps'
}

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.

Gst.Event.prototype.new_custom

function Gst.Event.prototype.new_custom(type: Gst.EventType, structure: Gst.Structure): {
    // javascript wrapper for 'gst_event_new_custom'
}

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.

Make sure to allocate an event type with the GST_EVENT_MAKE_TYPE (not introspectable) macro, assigning a free number and filling in the correct direction and serialization flags.

New custom events can also be created by subclassing the event type if needed.

Gst.Event.prototype.new_eos

function Gst.Event.prototype.new_eos(): {
    // javascript wrapper for 'gst_event_new_eos'
}

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 Gst.FlowReturn.EOS as a Gst.FlowReturn 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.MessageType.EOS on the bus after they have finished playing any buffered data.

When all sinks have posted an EOS message, an EOS message is forwarded to the application.

The EOS event itself will not cause any state transitions of the pipeline.

Gst.Event.prototype.new_flush_start

function Gst.Event.prototype.new_flush_start(): {
    // javascript wrapper for 'gst_event_new_flush_start'
}

Allocate a new flush start event. The flush start event can be sent upstream and downstream and travels out-of-bounds with the dataflow.

It marks pads as being flushing and will make them return Gst.FlowReturn.FLUSHING when used for data flow with Gst.Pad.prototype.push, Gst.Pad.prototype.chain, Gst.Pad.prototype.get_range and Gst.Pad.prototype.pull_range. Any event (except a Gst.EventType.FLUSH_STOP) received on a flushing pad will return false immediately.

Elements should unlock any blocking functions and exit their streaming functions as fast as possible when this event is received.

This event is typically generated after a seek to flush out all queued data in the pipeline so that the new media is played as soon as possible.

Gst.Event.prototype.new_flush_stop

function Gst.Event.prototype.new_flush_stop(reset_time: Number): {
    // javascript wrapper for 'gst_event_new_flush_stop'
}

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.

Elements can process this event synchronized with the dataflow since the preceding FLUSH_START event stopped the dataflow.

This event is typically generated to complete a seek and to resume dataflow.

Gst.Event.prototype.new_gap

function Gst.Event.prototype.new_gap(timestamp: Number, duration: Number): {
    // javascript wrapper for 'gst_event_new_gap'
}

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.

Gst.Event.prototype.new_instant_rate_change

function Gst.Event.prototype.new_instant_rate_change(rate_multiplier: Number, new_flags: Gst.SegmentFlags): {
    // javascript wrapper for 'gst_event_new_instant_rate_change'
}

Create a new instant-rate-change event. This event is sent by seek handlers (e.g. demuxers) when receiving a seek with the Gst.SeekFlags.INSTANT_RATE_CHANGE and signals to downstream elements that the playback rate in the existing segment should be immediately multiplied by the rate_multiplier factor.

The flags provided replace any flags in the existing segment, for the flags within the Gst.SEGMENT_INSTANT_FLAGS set. Other GstSegmentFlags are ignored and not transferred in the event.

Since : 1.18

Gst.Event.prototype.new_instant_rate_sync_time

function Gst.Event.prototype.new_instant_rate_sync_time(rate_multiplier: Number, running_time: Number, upstream_running_time: Number): {
    // javascript wrapper for 'gst_event_new_instant_rate_sync_time'
}

Create a new instant-rate-sync-time event. This event is sent by the pipeline to notify elements handling the instant-rate-change event about the running-time when the new rate should be applied. The running time may be in the past when elements handle this event, which can lead to switching artifacts. The magnitude of those depends on the exact timing of event delivery to each element and the magnitude of the change in playback rate being applied.

The running_time and upstream_running_time are the same if this is the first instant-rate adjustment, but will differ for later ones to compensate for the accumulated offset due to playing at a rate different to the one indicated in the playback segments.

Since : 1.18

Gst.Event.prototype.new_latency

function Gst.Event.prototype.new_latency(latency: Number): {
    // javascript wrapper for 'gst_event_new_latency'
}

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.

The latency is mostly used in live sinks and is always expressed in the time format.

Gst.Event.prototype.new_navigation

function Gst.Event.prototype.new_navigation(structure: Gst.Structure): {
    // javascript wrapper for 'gst_event_new_navigation'
}

Create a new navigation event from the given description.

Gst.Event.prototype.new_protection

function Gst.Event.prototype.new_protection(system_id: String, data: Gst.Buffer, origin: String): {
    // javascript wrapper for 'gst_event_new_protection'
}

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.

In order for a decryption element to decrypt media protected using a specific system, it first needs all the protection system specific information necessary to acquire the decryption key(s) for that stream. The functions defined here enable this information to be passed in events from elements that extract it (e.g., ISOBMFF demuxers, MPEG DASH demuxers) to protection decrypter elements that use it.

Events containing protection system specific information are created using Gst.Event.prototype.new_protection, and they can be parsed by downstream elements using Gst.Event.prototype.parse_protection.

In Common Encryption, protection system specific information may be located within ISOBMFF files, both in movie (moov) boxes and movie fragment (moof) boxes; it may also be contained in ContentProtection elements within MPEG DASH MPDs. The events created by Gst.Event.prototype.new_protection contain data identifying from which of these locations the encapsulated protection system specific information originated. This origin information is required as some protection systems use different encodings depending upon where the information originates.

The events returned by Gst.Event.prototype.new_protection are implemented in such a way as to ensure that the most recently-pushed protection info event of a particular origin and system_id will be stuck to the output pad of the sending element.

Since : 1.6

Gst.Event.prototype.new_qos

function Gst.Event.prototype.new_qos(type: Gst.QOSType, proportion: Number, diff: Number, timestamp: Number): {
    // javascript wrapper for 'gst_event_new_qos'
}

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.

type indicates the reason for the QoS event. Gst.QOSType.OVERFLOW is used when a buffer arrived in time or when the sink cannot keep up with the upstream datarate. Gst.QOSType.UNDERFLOW is when the sink is not receiving buffers fast enough and thus has to drop late buffers. Gst.QOSType.THROTTLE is used when the datarate is artificially limited by the application, for example to reduce power consumption.

proportion indicates the real-time performance of the streaming in the element that generated the QoS event (usually the sink). The value is generally computed based on more long term statistics about the streams timestamps compared to the clock. A value < 1.0 indicates that the upstream element is producing data faster than real-time. A value > 1.0 indicates that the upstream element is not producing data fast enough. 1.0 is the ideal proportion value. The proportion value can safely be used to lower or increase the quality of the element.

diff is the difference against the clock in running time of the last buffer that caused the element to generate the QOS event. A negative value means that the buffer with timestamp arrived in time. A positive value indicates how late the buffer with timestamp was. When throttling is enabled, diff will be set to the requested throttling interval.

timestamp is the timestamp of the last buffer that cause the element to generate the QOS event. It is expressed in running time and thus an ever increasing value.

The upstream element can use the diff and timestamp values to decide whether to process more buffers. For positive diff, all buffers with timestamp <= timestamp + diff will certainly arrive late in the sink as well. A (negative) diff value so that timestamp + diff would yield a result smaller than 0 is not allowed.

The application can use general event probes to intercept the QoS event and implement custom application specific QoS handling.

Gst.Event.prototype.new_reconfigure

function Gst.Event.prototype.new_reconfigure(): {
    // javascript wrapper for 'gst_event_new_reconfigure'
}

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.

Gst.Event.prototype.new_seek

function Gst.Event.prototype.new_seek(rate: Number, format: Gst.Format, flags: Gst.SeekFlags, start_type: Gst.SeekType, start: Number, stop_type: Gst.SeekType, stop: Number): {
    // javascript wrapper for 'gst_event_new_seek'
}

Allocate a new seek event with the given parameters.

The seek event configures playback of the pipeline between start to stop at the speed given in rate, also called a playback segment. The start and stop values are expressed in format.

A rate of 1.0 means normal playback rate, 2.0 means double speed. Negatives values means backwards playback. A value of 0.0 for the rate is not allowed and should be accomplished instead by PAUSING the pipeline.

A pipeline has a default playback segment configured with a start position of 0, a stop position of -1 and a rate of 1.0. The currently configured playback segment can be queried with Gst.QueryType.SEGMENT.

start_type and stop_type specify how to adjust the currently configured start and stop fields in playback segment. Adjustments can be made relative or absolute to the last configured values. A type of Gst.SeekType.NONE means that the position should not be updated.

When the rate is positive and start has been updated, playback will start from the newly configured start position.

For negative rates, playback will start from the newly configured stop position (if any). If the stop position is updated, it must be different from -1 (#GST_CLOCK_TIME_NONE) for negative rates.

It is not possible to seek relative to the current playback position, to do this, PAUSE the pipeline, query the current playback position with Gst.QueryType.POSITION and update the playback segment current position with a Gst.SeekType.SET to the desired position.

Gst.Event.prototype.new_segment

function Gst.Event.prototype.new_segment(segment: Gst.Segment): {
    // javascript wrapper for 'gst_event_new_segment'
}

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.

The segment event marks the range of buffers to be processed. All data not within the segment range is not to be processed. This can be used intelligently by plugins to apply more efficient methods of skipping unneeded data. The valid range is expressed with the start and stop values.

The time value of the segment is used in conjunction with the start value to convert the buffer timestamps into the stream time. This is usually done in sinks to report the current stream_time. time represents the stream_time of a buffer carrying a timestamp of start. time cannot be -1.

start cannot be -1, stop can be -1. If there is a valid stop given, it must be greater or equal the start, including when the indicated playback rate is < 0.

The applied_rate value provides information about any rate adjustment that has already been made to the timestamps and content on the buffers of the stream. (@rate * applied_rate) should always equal the rate that has been requested for playback. For example, if an element has an input segment with intended playback rate of 2.0 and applied_rate of 1.0, it can adjust incoming timestamps and buffer content by half and output a segment event with rate of 1.0 and applied_rate of 2.0

After a segment event, the buffer stream time is calculated with:

time + (TIMESTAMP(buf) - start) * ABS (rate * applied_rate)

Gst.Event.prototype.new_segment_done

function Gst.Event.prototype.new_segment_done(format: Gst.Format, position: Number): {
    // javascript wrapper for 'gst_event_new_segment_done'
}

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.

Gst.Event.prototype.new_select_streams

function Gst.Event.prototype.new_select_streams(streams: [ String ]): {
    // javascript wrapper for 'gst_event_new_select_streams'
}

Allocate a new select-streams event.

The select-streams event requests the specified streams to be activated.

The list of streams corresponds to the "Stream ID" of each stream to be activated. Those ID can be obtained via the Gst.Stream objects present in Gst.EventType.STREAM_START, Gst.EventType.STREAM_COLLECTION or Gst.MessageType.STREAM_COLLECTION.

Note: The list of streams can not be empty.

Since : 1.10

Gst.Event.prototype.new_sink_message

function Gst.Event.prototype.new_sink_message(name: String, msg: Gst.Message): {
    // javascript wrapper for 'gst_event_new_sink_message'
}

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.

name is used to store multiple sticky events on one pad.

Gst.Event.prototype.new_step

function Gst.Event.prototype.new_step(format: Gst.Format, amount: Number, rate: Number, flush: Number, intermediate: Number): {
    // javascript wrapper for 'gst_event_new_step'
}

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.

A rate of <= 0.0 is not allowed. Pause the pipeline, for the effect of rate = 0.0 or first reverse the direction of playback using a seek event to get the same effect as rate < 0.0.

The flush flag will clear any pending data in the pipeline before starting the step operation.

The intermediate flag instructs the pipeline that this step operation is part of a larger step operation.

Gst.Event.prototype.new_stream_collection

function Gst.Event.prototype.new_stream_collection(collection: Gst.StreamCollection): {
    // javascript wrapper for 'gst_event_new_stream_collection'
}

Create a new STREAM_COLLECTION event. The stream collection event can only travel downstream synchronized with the buffer flow.

Source elements, demuxers and other elements that manage collections of streams and post Gst.StreamCollection messages on the bus also send this event downstream on each pad involved in the collection, so that activation of a new collection can be tracked through the downstream data flow.

Since : 1.10

Gst.Event.prototype.new_stream_group_done

function Gst.Event.prototype.new_stream_group_done(group_id: Number): {
    // javascript wrapper for 'gst_event_new_stream_group_done'
}

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.

This event is followed by EOS at some point in the future, and is generally used when switching pads - to unblock downstream so that new pads can be exposed before sending EOS on the existing pads.

Since : 1.10

Gst.Event.prototype.new_stream_start

function Gst.Event.prototype.new_stream_start(stream_id: String): {
    // javascript wrapper for 'gst_event_new_stream_start'
}

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.

Source elements, demuxers and other elements that create new streams are supposed to send this event as the first event of a new stream. It should not be sent after a flushing seek or in similar situations and is used to mark the beginning of a new logical stream. Elements combining multiple streams must ensure that this event is only forwarded downstream once and not for every single input stream.

The stream_id should be a unique string that consists of the upstream stream-id, / as separator and a unique stream-id for this specific stream. A new stream-id should only be created for a stream if the upstream stream is split into (potentially) multiple new streams, e.g. in a demuxer, but not for every single element in the pipeline. Gst.Pad.prototype.create_stream_id or gst_pad_create_stream_id_printf (not introspectable) can be used to create a stream-id. There are no particular semantics for the stream-id, though it should be deterministic (to support stream matching) and it might be used to order streams (besides any information conveyed by stream flags).

Gst.Event.prototype.new_tag

function Gst.Event.prototype.new_tag(taglist: Gst.TagList): {
    // javascript wrapper for 'gst_event_new_tag'
}

Generates a metadata tag event from the given taglist.

The scope of the taglist specifies if the taglist applies to the complete medium or only to this specific stream. As the tag event is a sticky event, elements should merge tags received from upstream with a given scope with their own tags with the same scope and create a new tag event from it.

Gst.Event.prototype.new_toc

function Gst.Event.prototype.new_toc(toc: Gst.Toc, updated: Number): {
    // javascript wrapper for 'gst_event_new_toc'
}

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.

Gst.Event.prototype.new_toc_select

function Gst.Event.prototype.new_toc_select(uid: String): {
    // javascript wrapper for 'gst_event_new_toc_select'
}

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.

Gst.Event.prototype.copy_segment

function Gst.Event.prototype.copy_segment(segment: Gst.Segment): {
    // javascript wrapper for 'gst_event_copy_segment'
}

Parses a segment event and copies the Gst.Segment into the location given by segment.

Gst.Event.prototype.get_running_time_offset

function Gst.Event.prototype.get_running_time_offset(): {
    // javascript wrapper for 'gst_event_get_running_time_offset'
}

Retrieve the accumulated running time offset of the event.

Events passing through Gst.Pad that have a running time offset set via Gst.Pad.prototype.set_offset will get their offset adjusted according to the pad's offset.

If the event contains any information that related to the running time, this information will need to be updated before usage with this offset.

Since : 1.4

Gst.Event.prototype.get_seqnum

function Gst.Event.prototype.get_seqnum(): {
    // javascript wrapper for 'gst_event_get_seqnum'
}

Retrieve the sequence number of a event.

Events have ever-incrementing sequence numbers, which may also be set explicitly via Gst.Event.prototype.set_seqnum. Sequence numbers are typically used to indicate that a event corresponds to some other set of events or messages, for example an EOS event corresponding to a SEEK event. It is considered good practice to make this correspondence when possible, though it is not required.

Note that events and messages share the same sequence number incrementor; two events or messages will never have the same sequence number unless that correspondence was made explicitly.

Gst.Event.prototype.get_structure

function Gst.Event.prototype.get_structure(): {
    // javascript wrapper for 'gst_event_get_structure'
}

Access the structure of the event.

Gst.Event.prototype.has_name

function Gst.Event.prototype.has_name(name: String): {
    // javascript wrapper for 'gst_event_has_name'
}

Checks if event has the given name. This function is usually used to check the name of a custom event.

Gst.Event.prototype.has_name_id

function Gst.Event.prototype.has_name_id(name: GLib.Quark): {
    // javascript wrapper for 'gst_event_has_name_id'
}

Checks if event has the given name. This function is usually used to check the name of a custom event.

Since : 1.18

deprecated : 1.26: Use gst_event_has_name().

Gst.Event.prototype.parse_buffer_size

function Gst.Event.prototype.parse_buffer_size(): {
    // javascript wrapper for 'gst_event_parse_buffer_size'
}

Get the format, minsize, maxsize and async-flag in the buffersize event.

Gst.Event.prototype.parse_caps

function Gst.Event.prototype.parse_caps(): {
    // javascript wrapper for 'gst_event_parse_caps'
}

Get the caps from event. The caps remains valid as long as event remains valid.

Gst.Event.prototype.parse_flush_stop

function Gst.Event.prototype.parse_flush_stop(): {
    // javascript wrapper for 'gst_event_parse_flush_stop'
}

Parse the FLUSH_STOP event and retrieve the reset_time member.

Gst.Event.prototype.parse_gap

function Gst.Event.prototype.parse_gap(): {
    // javascript wrapper for 'gst_event_parse_gap'
}

Extract timestamp and duration from a new GAP event.

Gst.Event.prototype.parse_gap_flags

function Gst.Event.prototype.parse_gap_flags(): {
    // javascript wrapper for 'gst_event_parse_gap_flags'
}

Retrieve the gap flags that may have been set on a gap event with Gst.Event.prototype.set_gap_flags.

Since : 1.20

Gst.Event.prototype.parse_group_id

function Gst.Event.prototype.parse_group_id(): {
    // javascript wrapper for 'gst_event_parse_group_id'
}

Since : 1.2

Gst.Event.prototype.parse_instant_rate_change

function Gst.Event.prototype.parse_instant_rate_change(): {
    // javascript wrapper for 'gst_event_parse_instant_rate_change'
}

Extract rate and flags from an instant-rate-change event.

Since : 1.18

Gst.Event.prototype.parse_instant_rate_sync_time

function Gst.Event.prototype.parse_instant_rate_sync_time(): {
    // javascript wrapper for 'gst_event_parse_instant_rate_sync_time'
}

Extract the rate multiplier and running times from an instant-rate-sync-time event.

Since : 1.18

Gst.Event.prototype.parse_latency

function Gst.Event.prototype.parse_latency(): {
    // javascript wrapper for 'gst_event_parse_latency'
}

Get the latency in the latency event.

Gst.Event.prototype.parse_protection

function Gst.Event.prototype.parse_protection(): {
    // javascript wrapper for 'gst_event_parse_protection'
}

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.

Since : 1.6

Gst.Event.prototype.parse_qos

function Gst.Event.prototype.parse_qos(): {
    // javascript wrapper for 'gst_event_parse_qos'
}

Get the type, proportion, diff and timestamp in the qos event. See Gst.Event.prototype.new_qos for more information about the different QoS values.

timestamp will be adjusted for any pad offsets of pads it was passing through.

Gst.Event.prototype.parse_seek

function Gst.Event.prototype.parse_seek(): {
    // javascript wrapper for 'gst_event_parse_seek'
}

Parses a seek event and stores the results in the given result locations.

Gst.Event.prototype.parse_seek_trickmode_interval

function Gst.Event.prototype.parse_seek_trickmode_interval(): {
    // javascript wrapper for 'gst_event_parse_seek_trickmode_interval'
}

Retrieve the trickmode interval that may have been set on a seek event with Gst.Event.prototype.set_seek_trickmode_interval.

Since : 1.16

Gst.Event.prototype.parse_segment

function Gst.Event.prototype.parse_segment(): {
    // javascript wrapper for 'gst_event_parse_segment'
}

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.

Gst.Event.prototype.parse_segment_done

function Gst.Event.prototype.parse_segment_done(): {
    // javascript wrapper for 'gst_event_parse_segment_done'
}

Extracts the position and format from the segment done message.

Gst.Event.prototype.parse_select_streams

function Gst.Event.prototype.parse_select_streams(): {
    // javascript wrapper for 'gst_event_parse_select_streams'
}

Parse the SELECT_STREAMS event and retrieve the contained streams.

Since : 1.10

Gst.Event.prototype.parse_sink_message

function Gst.Event.prototype.parse_sink_message(): {
    // javascript wrapper for 'gst_event_parse_sink_message'
}

Parse the sink-message event. Unref msg after usage.

Gst.Event.prototype.parse_step

function Gst.Event.prototype.parse_step(): {
    // javascript wrapper for 'gst_event_parse_step'
}

Parse the step event.

Gst.Event.prototype.parse_stream

function Gst.Event.prototype.parse_stream(): {
    // javascript wrapper for 'gst_event_parse_stream'
}

Parse a stream-start event and extract the Gst.Stream from it.

Since : 1.10

Gst.Event.prototype.parse_stream_collection

function Gst.Event.prototype.parse_stream_collection(): {
    // javascript wrapper for 'gst_event_parse_stream_collection'
}

Retrieve new Gst.StreamCollection from STREAM_COLLECTION event event.

Since : 1.10

Gst.Event.prototype.parse_stream_flags

function Gst.Event.prototype.parse_stream_flags(): {
    // javascript wrapper for 'gst_event_parse_stream_flags'
}

Since : 1.2

Gst.Event.prototype.parse_stream_group_done

function Gst.Event.prototype.parse_stream_group_done(): {
    // javascript wrapper for 'gst_event_parse_stream_group_done'
}

Parse a stream-group-done event and store the result in the given group_id location.

Since : 1.10

Gst.Event.prototype.parse_stream_start

function Gst.Event.prototype.parse_stream_start(): {
    // javascript wrapper for 'gst_event_parse_stream_start'
}

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.

Gst.Event.prototype.parse_tag

function Gst.Event.prototype.parse_tag(): {
    // javascript wrapper for 'gst_event_parse_tag'
}

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.

Gst.Event.prototype.parse_toc

function Gst.Event.prototype.parse_toc(): {
    // javascript wrapper for 'gst_event_parse_toc'
}

Parse a TOC event and store the results in the given toc and updated locations.

Gst.Event.prototype.parse_toc_select

function Gst.Event.prototype.parse_toc_select(): {
    // javascript wrapper for 'gst_event_parse_toc_select'
}

Parse a TOC select event and store the results in the given uid location.

Gst.Event.prototype.set_gap_flags

function Gst.Event.prototype.set_gap_flags(flags: Gst.GapFlags): {
    // javascript wrapper for 'gst_event_set_gap_flags'
}

Sets flags on event to give additional information about the reason for the Gst.EventType.GAP.

Since : 1.20

Gst.Event.prototype.set_group_id

function Gst.Event.prototype.set_group_id(group_id: Number): {
    // javascript wrapper for 'gst_event_set_group_id'
}

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.

Use Gst.prototype.util_group_id_next to get a new group id.

Since : 1.2

Gst.Event.prototype.set_running_time_offset

function Gst.Event.prototype.set_running_time_offset(offset: Number): {
    // javascript wrapper for 'gst_event_set_running_time_offset'
}

Set the running time offset of a event. See Gst.Event.prototype.get_running_time_offset for more information.

MT safe.

Since : 1.4

Gst.Event.prototype.set_seek_trickmode_interval

function Gst.Event.prototype.set_seek_trickmode_interval(interval: Number): {
    // javascript wrapper for 'gst_event_set_seek_trickmode_interval'
}

Sets a trickmode interval on a (writable) seek event. Elements that support TRICKMODE_KEY_UNITS seeks SHOULD use this as the minimal interval between each frame they may output.

Since : 1.16

Gst.Event.prototype.set_seqnum

function Gst.Event.prototype.set_seqnum(seqnum: Number): {
    // javascript wrapper for 'gst_event_set_seqnum'
}

Set the sequence number of a event.

This function might be called by the creator of a event to indicate that the event relates to other events or messages. See Gst.Event.prototype.get_seqnum for more information.

MT safe.

Gst.Event.prototype.set_stream

function Gst.Event.prototype.set_stream(stream: Gst.Stream): {
    // javascript wrapper for 'gst_event_set_stream'
}

Set the stream on the stream-start event

Since : 1.10

Gst.Event.prototype.set_stream_flags

function Gst.Event.prototype.set_stream_flags(flags: Gst.StreamFlags): {
    // javascript wrapper for 'gst_event_set_stream_flags'
}

Since : 1.2

Gst.Event.prototype.writable_structure

function Gst.Event.prototype.writable_structure(): {
    // javascript wrapper for 'gst_event_writable_structure'
}

Get a writable version of the structure.

Gst.prototype.event_type_get_flags

function Gst.prototype.event_type_get_flags(type: Gst.EventType): {
    // javascript wrapper for 'gst_event_type_get_flags'
}

Gets the Gst.EventTypeFlags associated with type.

Gst.prototype.event_type_get_name

function Gst.prototype.event_type_get_name(type: Gst.EventType): {
    // javascript wrapper for 'gst_event_type_get_name'
}

Get a printable name for the given event type. Do not modify or free.

Gst.prototype.event_type_to_quark

function Gst.prototype.event_type_to_quark(type: Gst.EventType): {
    // javascript wrapper for 'gst_event_type_to_quark'
}

Get the unique quark for the given event type.

Gst.prototype.event_type_to_sticky_ordering

function Gst.prototype.event_type_to_sticky_ordering(type: Gst.EventType): {
    // javascript wrapper for 'gst_event_type_to_sticky_ordering'
}

Converts the Gst.EventType to an unsigned integer that represents the ordering of sticky events when re-sending them. A lower value represents a higher-priority event.

Since : 1.22