Docs

Search documentation

Search across Strave documentation

RTMP & SRT Streaming

Ingest and restream match feeds for your broadcast.

Organisation streaming servers receive an observer or programme feed and can relay it to production or additional RTMP destinations.

SRT ingest is currently available to eligible organisations. RTMP server creation is temporarily disabled in the product; existing RTMP servers can still appear in an organisation. The create-server dialog always shows the current availability for your plan.

Create a server

You need the organisation's Manage servers permission.

  1. Open the organisation workspace.
  2. Go to Broadcast → Servers.
  3. Select New server.
  4. Enter a descriptive name such as Main observer EU.
  5. Choose SRT.
  6. Select Create Server.

Streaming access may require a plan upgrade. Members without management permission can view existing infrastructure but cannot create or change it.

Connect an SRT publisher

Open the server and stay on Connection info. Copy the generated:

  • SRT URL;
  • stream id;
  • passphrase.

The full URL shown by Strave already includes the required query parameters for compatible encoders. In OBS, select the custom output or FFmpeg-based SRT option supported by your version and paste the complete URL.

For another SRT application that asks for separate fields, use the displayed URL, stream id, and passphrase independently. Keep the mode and latency settings consistent with the encoder and production receiver.

Connect production playback

The same page provides a separate SRT playback URL, stream id, and passphrase. Give playback credentials only to the producer or system receiving the feed. Publisher and playback credentials are intentionally distinct.

When the observer starts sending video, the server status changes from Stopped to Running and the preview becomes ready.

Existing RTMP servers

For an existing RTMP server, Strave shows an RTMPS URL and key for ingest, plus separate RTMPS playback credentials. Configure the server URL and key as separate values in OBS or the sending encoder.

Do not create documentation or runbooks that assume new RTMP servers can be provisioned while the product marks the option unavailable.

Add restream outputs

The Outputs tab can relay the incoming feed to Twitch, YouTube, Facebook, Kick, or another RTMP endpoint.

  1. Select Add output.
  2. Enter the full rtmp:// or rtmps:// destination URL.
  3. Enter that destination's stream key.
  4. Save and verify the output at the destination.

Destination keys are secrets. Never paste them into chat, screenshots, issue trackers, or public documentation.

Operational checklist

Before going live:

  • run a sustained test using the expected resolution, frame rate, and bitrate;
  • verify audio channels and sync;
  • confirm the server reports Running;
  • inspect the Strave preview and the final destination;
  • keep an alternate communication path with the observer;
  • label servers and outputs so an operator cannot confuse rehearsals with the live show.

Troubleshooting

If the feed stays offline:

  1. copy the current credentials again instead of retyping them;
  2. confirm SRT stream id and passphrase are both present;
  3. check that the encoder is publishing rather than listening;
  4. verify the organisation still has streaming access;
  5. stop duplicate publishers using the same endpoint.

If Strave receives the feed but an output is dark, test the destination URL and key directly in an encoder. The issue is then between the restream output and the destination, not the ingest.

Streaming servers carry the video. Event graphics are separate browser sources; set those up with the Overlay overview.