rtponviftimestamp

Hierarchy

GObject
    ╰──GInitiallyUnowned
        ╰──GstObject
            ╰──GstElement
                ╰──rtponviftimestamp

Factory details

sink

application/x-rtp:

src

application/x-rtp:

cseq

“cseq” guint

The RTSP CSeq which initiated the playback

Flags : Read / Write

Default value : 0

drop-out-of-segment

“drop-out-of-segment” gboolean

Whether the element should drop buffers that fall outside the segment, not part of the specification but allows full reverse playback.

Flags : Read / Write

Default value : true

ntp-offset

“ntp-offset” guint64

Offset between the pipeline running time and the absolute UTC time, in nano-seconds since 1900 (-1 for automatic computation)

Flags : Read / Write

Default value : 18446744073709551615

set-e-bit

“set-e-bit” gboolean

If the element should set the 'E' bit as defined in the ONVIF RTP extension. This increases latency by one packet

Flags : Read / Write

Default value : false

set-t-bit

“set-t-bit” gboolean

If the element should set the 'T' bit as defined in the ONVIF RTP extension. This increases latency by one packet

Flags : Read / Write

Default value : false

use-reference-timestamps

“use-reference-timestamps” gboolean

Whether to obtain timestamps from reference timestamp meta instead of using the ntp-offset method. If enabled then timestamps are expected to be attached to the buffers, and in that case ntp-offset should not be configured.

Default value is FALSE, meaning that the ntp-offset property is used. If neither is set then the element calculates an ntp-offset.

Flags : Read / Write

Default value : false

Since : 1.22