RIST¶

media.push.rist

Sapsan initiates an outgoing publication over RIST. A stream can have several named pushes.

Configuration¶

Apply the stream configuration through central.

A stream's pushes are a mapping of push name to setting, not a list. The name is unique within the stream and serves as the key: it is how a push is found in the configuration, in the statistics, and in the metrics. A push has exactly one protocol.

streams:
  - name: tv1
    inputs:
    - udp: {host: 239.0.0.1, port: 5000}
    pushes:
      delivery:
        rist:
          host: 203.0.113.10
          port: 9000

The name is the push's identity. Renaming carries over neither the setting nor the accumulated counters: the old push disappears and the new one starts from zero.

A push over UDP, SRT, or RIST can carry its own mpegts section — its own program number, track PIDs, and SDT for that push only.

Monitoring¶

Every push has statistics of its own — target, status, failure reason, rate, bytes, errors, reconnects. The field reference, the Prometheus series, and alerting recipes are on the Statistics page.

Transport¶

MPEG-TS over RIST/UDP with retransmission of lost packets.

Supported codecs¶

• H.264
• HEVC
• AV1
• JPEG 2000
• MPEG-2 Video
• AAC
• AC-3
• E-AC-3
• MPEG Audio
• SMPTE 302M

These codecs can be remuxed from already encoded tracks into MPEG-TS; the push itself does not transcode them. AAC is carried with ADTS. Codec support in fMP4 or HLS does not imply the same support in this output.

AV1 is announced as a private stream with the AV01 registration; the receiver must support this specific packaging. Opus is not included in the verified codec set for this output: its presence in the input path does not establish complete output signaling and packaging of Opus in MPEG-TS.