RTMP & SRT Streaming

Ingest and restream match feeds for your broadcast.

An organisation streaming server receives an observer feed or a programme feed. It can relay that feed to your production team or to other RTMP destinations.

SRT ingest is available to eligible organisations. You can't create new RTMP servers at the moment, but existing RTMP servers still work. The New server dialog always shows what your plan can use.

Create a server

To create a server, you need the organisation's Manage servers permission. Members without this permission can view existing servers but can't create or change them. Streaming access can also require a plan upgrade.

To create an SRT server, follow these steps:

  1. Open the organisation workspace.
  2. In the Manage section of the sidebar, select Streaming Server.
  3. Select New server.
  4. Enter a descriptive name, such as Main observer EU.
  5. Choose SRT.
  6. Select Create Server.

Connect an SRT publisher

The publisher is the encoder that sends the feed to Strave, for example the observer's OBS. Open the server and stay on Connection info. Copy these values:

  • SRT URL.
  • Stream ID.
  • Passphrase.

The full URL already includes the query parameters that compatible encoders need. In OBS, select the custom output or the FFmpeg-based SRT option that your version supports, and paste the complete URL.

If your SRT application asks for separate fields, enter the URL, stream ID, and passphrase separately. Use the same mode and latency settings on the encoder and the production receiver.

Connect production playback

The same page shows a separate SRT playback URL, stream ID, and passphrase. Publisher and playback credentials are different on purpose. Give the playback credentials only to the producer or system that receives the feed.

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

Existing RTMP servers

For an existing RTMP server, Strave shows an RTMPS URL and a stream key for ingest. It also shows separate RTMPS playback credentials. In OBS or your encoder, enter the server URL and the key as separate values.

Add restream outputs

The Outputs tab can relay the incoming feed to Twitch, YouTube, Facebook, Kick, or any other RTMP endpoint. To add an output, follow these steps:

  1. Select Add output.
  2. Enter the full rtmp:// or rtmps:// destination URL.
  3. Enter the stream key for that destination.
  4. Save the output.
  5. Check that the stream appears at the destination.

Stream keys are secrets. Never paste them into chat, screenshots, issue trackers, or public documents.

Checklist before you go live

Before you go live, complete these checks:

  • Run a long test with the expected resolution, frame rate, and bitrate.
  • Check the audio channels and audio sync.
  • Confirm that the server shows Running.
  • Check the Strave preview and the final destination.
  • Keep a second way to contact the observer.
  • Name servers and outputs clearly, so that no operator confuses a rehearsal with the live show.

Troubleshooting

If the feed stays offline, do these steps in order:

  1. Copy the current credentials again instead of typing them.
  2. Confirm that both the SRT stream ID and the passphrase are present.
  3. Check that the encoder publishes the stream and doesn't only listen.
  4. Check that the organisation still has streaming access.
  5. Stop any other publishers that use the same endpoint.

If Strave receives the feed but an output stays dark, the problem is between the restream output and the destination, not with the ingest. To find it, test the destination URL and key directly in an encoder.

Next steps

Streaming servers carry only the video. Event graphics are separate browser sources. To set them up, see the Overlay overview.