Ir al contenido
Feature · SRT relay

SRT gateway for RTMP platforms and SRT receivers

Send one SRT feed out of the venue and StreamRove turns it into what each destination takes: RTMP or RTMPS for YouTube, Twitch, Kick and Facebook, and SRT again for a broadcaster's receiver or your own server. With Broadcast delivery, the relay forwards your encoder's own signal without touching it, so a 1080i50 contribution feed arrives as 1080i50.

Encoders call StreamRove on port 8890 in Caller mode. RTMP and RTMPS work as inputs too, and they can feed an SRT destination just the same.

8890
SRT input port
1080i50
Kept on Broadcast delivery
H.265 → H.264
Converted on the standard route
60 s
Before a signal alert

Why run SRT through StreamRove

Contribution and distribution from one feed

One stream leaves the venue. The copies are made on our side: one for the broadcaster's SRT receiver and one for each public platform, at the same time.

Interlaced stays interlaced

On the standard route, platforms re-make your picture, and a 1080i50 feed comes out as 25p with the fields still woven into each frame. Broadcast delivery sends the encoder's own packets instead. We measured it: a 1080i50 feed sent over SRT reached the receiver top field first on every frame we checked, 40 ms apart.

Codecs fixed on the way

On the standard route, H.265, AV1 and other pictures the platforms won't take are converted to H.264, up to 1080p, and Opus or MP3 sound to AAC. On Broadcast delivery the picture stays exactly as sent, H.265 included, and only the sound is converted when it has to be.

You hear about a drop first

Turn on signal alerts and StreamRove emails you when the signal stops reaching its destinations for more than a minute, and again when it's back. Webhook and Telegram alerts are a workspace setting.

What the gateway does

An SRT input on every encoder stream

Each encoder stream has its own SRT address on live.streamrove.com, port 8890, mode Caller. Start with 500 ms latency and raise it for long or mobile routes. The input takes no passphrase; use RTMPS when the route needs encryption.

SRT out to any receiver

A Custom SRT destination calls the receiver's srt:// address, with its stream ID and passphrase in the URL if it uses them. The receiver listens; StreamRove calls it. Listener and rendezvous addresses are refused.

Standard or Broadcast, per destination

Each destination has a switch under its name. Standard suits the public platforms. Broadcast sends the encoder's own signal for receivers that need it as it left the truck. Broadcast is on the Relay plan and up.

RTMP and RTMPS out

YouTube, Twitch and Kick connect in one click. Facebook, LinkedIn, a client's CDN or your own RTMP server take a pasted address and key, with a username and password if the server asks for one.

A status line per destination

Each destination says whether it is reaching its platform. When a Broadcast push fails, the page gives the reason in a word (refused, timeout, key rejected) and switches it back to Standard in one click if you choose.

A holding screen when the line gives out

On the Control plan and up, the Backup stream card keeps every destination on air with a holding screen, a countdown or a looping video until the encoder reconnects. It covers the gap; it isn't a second feed.

StreamRove as your SRT gateway, or a gateway server you run?

SRT gateway software on your own machine does the routing too. The difference is who keeps it running.

StreamRoveA self-hosted SRT gateway
Server or appliance to keep up✓ None: it runs in the cloudYours to install, patch and watch
SRT to YouTube, Twitch, Kick and Facebook✓ One click for the first three, a pasted key for the rest✓ One output to configure per platform
1080i50 untouched to an SRT receiver✓ With Broadcast delivery✓ Usually, as a pass-through
H.265 or AV1 in, H.264 out✓ On the standard route, up to 1080pDepends on the server's CPU and set-up
Alerts when the feed drops✓ Email per stream; webhook or TelegramMonitoring you add yourself
Encryption on the input— No passphrase on the SRT input; RTMPS is encrypted✓ AES passphrase, if you set one
CostBroadcast delivery from the Relay planServer, bandwidth and your time

How to route an SRT feed to a receiver and the platforms

Do it the day before, from the venue's connection if you can.

  1. Create an encoder stream

    Click New Stream and choose Encoder | RTMP. On the stream page, open the SRT tab next to RTMPS.

  2. Add the receiver and the platforms

    Under Your Channels, add a Custom SRT destination with the receiver's srt:// address, then YouTube, Twitch, Kick or any RTMP destination. Ask the receiving end to start its listener first.

  3. Point the encoder at StreamRove

    Set Caller mode, host live.streamrove.com, port 8890 and latency 500 ms, and paste the Stream ID whole. Software that takes one URL, OBS included, takes the Single URL instead.

  4. Switch the receiver to Broadcast

    Click Standard under the SRT destination's name and choose Broadcast. Leave the public platforms on Standard: they re-make the picture anyway.

  5. Turn on signal alerts

    Click Signal alerts off on the stream page to turn them on. Add a webhook or Telegram in your workspace's alert settings if email isn't enough.

  6. Start and check every line

    Start the encoder. The SRT tab should read Encoder connected over SRT, and each destination should show Reaching before you tell the receiving end you're up.

Preguntas frecuentes

Can StreamRove convert SRT to RTMP?

Yes. Send SRT to your stream's SRT address and every RTMP or RTMPS destination receives the stream the way it takes it: YouTube, Twitch, Kick, Facebook, LinkedIn or a server of your own. It works the other way too: an encoder sending RTMP can feed a Custom SRT destination.

Does StreamRove keep 1080i50 interlaced video?

On Broadcast delivery, yes: the relay forwards your encoder's own packets to that destination, interlacing included. MBAFF interlacing, what x264, OBS and vMix produce, passes untouched. PAFF with B-frames is the exception: the timestamps don't survive the relay's input, so send MBAFF or switch B-frames off. On the standard route, 1080i50 comes out as 25p.

What does an SRT receiver need to accept StreamRove's stream?

A listener that's running before you start, on an address StreamRove can reach from the internet. StreamRove calls it in Caller mode with the srt:// address you gave, stream ID and passphrase included. A private or local address is refused.

Which plan do I need for Broadcast delivery?

Relay and every plan above it. The SRT input, Custom SRT destinations and the standard route are on every plan, within its limits on destinations and output hours.

Is the SRT input encrypted?

No. StreamRove's SRT input takes no passphrase, so the feed travels unencrypted, as over plain RTMP. Treat the Stream ID like a password. When the route needs encryption, send RTMPS instead: it travels inside TLS, and the relay delivers it to SRT destinations the same way.

What happens if the venue's line drops?

Destinations stop receiving until the encoder reconnects to the same address; then delivery resumes. On the Control plan and up, the Backup stream card holds every destination with a holding screen in the meantime, and signal alerts email you if the gap lasts more than a minute.

Does Broadcast delivery work from StreamRove Studio?

No. Broadcast delivery forwards an encoder's own signal, so it needs an encoder sending to the StreamRove ingest. Studio broadcasts reach SRT destinations on the standard route.

Sigue leyendo

Del blog

One SRT feed, every receiver and platform

Create an encoder stream, add your receiver as a Custom SRT destination and test it from the venue.

Regístrate gratis