SRT Streaming

Use SRT ingest for more resilient streaming on unreliable networks.

Quick Navigation

Overview

SRT is a UDP-based protocol with built-in recovery, ideal for mobile or long-haul networks. Meshcast accepts SRT ingest on registered accounts and routes it to WHEP or HLS playback.

Requirements

Set up your SRT encoder

  1. Copy your Stream ID and Publish Key Find your public Stream ID (st_...), private Publish Key (pk_...), and assigned server in the Meshcast dashboard or studio.
  2. Build the SRT URL Use the credentialed SRT stream ID format below. The path is the public Stream ID, and the Publish Key is passed as the SRT password.
    srt://[server-ip]:8890?streamid=publish:[stream-id]:meshcast:[publish-key]&pkt_size=1316&latency=400000
  3. Configure your encoder Set SRT mode to Caller, paste the full URL above, leave OBS Stream Key empty, and use a stable bitrate for the network.
  4. Larix app note If Larix shows only NDI and WebRTC options, confirm you are using Larix Broadcaster (not Larix Player), and that you are adding a full destination URL that supports SRT Caller.
  5. Start streaming Publish and confirm the stream appears in your Meshcast dashboard or viewer link.
Stream ID format matters

SRT ingest should publish to st_... and authenticate with pk_...: streamid=publish:st_...:meshcast:pk_.... Using only pk_... can create a private media path that the normal viewer link does not watch.

Latency presets

OBS and FFmpeg use FFmpeg's SRT URL options. The latency value is measured in microseconds, not milliseconds.

Higher latency gives SRT more time to recover lost packets, but adds delay. If the stream still breaks up at 800 ms, lower the encoder bitrate before increasing latency further.

Playback options