rtph263ppay2

Payloads an H.263+ (H.263-1998) or H.263++ (H.263-2000) video stream into RTP packets as per RFC 4629.

Each input buffer must contain exactly one complete picture. Frames that don't fit into the configured MTU are fragmented either with follow-on packets or at segment boundaries, depending on the fragmentation-mode property. Segment boundaries are picture, GOB, slice, EOS and EOSBS start codes; encoders should be configured to emit GOB or slice start codes for this to be useful.

The SDP annex parameters (f, i, j, t, k, n) are derived from annex-* fields of the input caps; without them receivers must assume Baseline H.263 (RFC 4629 section 8.1.1). Placing a parser such as h263parse before this element provides those fields.

Example pipeline

 gst-launch-1.0 videotestsrc ! video/x-raw,format=I420,width=176,height=144 ! avenc_h263p ! rtph263ppay2 ! udpsink2 host=127.0.0.1 port=5004

This will encode a test pattern as H.263+ and payload it as RTP to localhost port 5004.

Hierarchy

GObject
    ╰──GInitiallyUnowned
        ╰──GstObject
            ╰──GstElement
                ╰──GstRtpBasePay2
                    ╰──rtph263ppay2

Factory details

Authors: – Edward Hervey

Classification: – Codec/Payloader/Network/RTP

Rank – primary

Plugin – rsrtp

Package – gst-plugin-rtp

Pad Templates

sink

video/x-h263:
        variant: itu
         parsed: true

Presence – always

Direction – sink

Object type – GstPad


src

application/x-rtp:
          media: video
  encoding-name: H263-1998
     clock-rate: 90000
application/x-rtp:
          media: video
  encoding-name: H263-2000
     clock-rate: 90000

Presence – always

Direction – src

Object type – GstPad


Properties

fragmentation-mode

“fragmentation-mode” Rtp-h263ppay2fragmentation-mode *

How to fragment frames larger than the MTU: follow-on packets ('normal') or packets that start at segment boundaries ('sync')

Flags : Read / Write

Default value : normal (0)


Named constants

Rtp-h263ppay2fragmentation-mode

Members

normal (0) – Follow-on packets
sync (1) – Fragment at segment boundaries

The results of the search are