Choose the next receiver before you build the route
Start with the source, the receiver and the media change the receiver actually needs. An SRT Route is for a transparent SRT-to-SRT relay: it forwards the contribution, so the receiver must already accept its container, codecs, tracks and timestamps. It relays the source media; it does not create a browser output.
If the next job is RTMP publishing, configure a Restream output and enable processing only when that destination needs it. If the next job is an NDI production handoff, configure the NDI output path and validate it on the designed production network. Use an SRT Server for controlled ingress and an SRT Stream for a named connection on an existing server. A connected source is not proof that any downstream receiver accepted the feed.
| Incoming SRT job | Choose | Verify at the far end |
|---|
| SRT → SRT receiver | SRT Route, when both endpoints already accept the source media. | Receiver connection, decoded picture and programme audio. |
|---|
| SRT → RTMP publisher | Restreaming with the required RTMP destination and only the media processing that output needs. | The RTMP receiver or publishing platform accepts the intended programme. |
|---|
| SRT → NDI production handoff | The NDI output workflow for the selected deployment and production network. | The intended NDI receiver sees picture and programme audio. |
|---|
Transcoding, resizing, audio changes and overlays add processing work beyond a relay. Test the planned source, output profile, host capacity and destination together; do not infer the final output from a green ingress connection.
When the publisher connects but the receiver is empty
| What you see | Check next |
|---|
| Publisher is connected; receiver has no bitrate | Confirm the route selects the intended input and output, then compare receiver host, port, Caller/Listener role, Stream ID and passphrase. |
|---|
| Receiver has bitrate; no picture or programme audio | Check the container, codecs, tracks and timestamps at the receiver. SRT transport does not make an unsupported payload decodable. |
|---|
| Picture breaks on the event network | Compare RTT, loss, retransmissions and effective latency on the actual path. Test the source, route and receiver together. |
|---|
Connection
Record the source and destination host, port, roles and access state. Use endpoint logs when the session is denied or reaches the wrong stream.
Transport health
Watch bitrate, RTT, packet loss, connection events and peer details while the source is running. A saved route or running process does not show whether a destination accepted it.
Decoded output
Verify picture and programme audio at the selected receiver, player or Multiview tile. Multiview is the observation handoff; it does not turn a relay into a production switcher.
Keep the route demo separate from a failover test
The temporary gateway demo tests one publisher and one receiver connection, then a Multiview preview after the publisher connects. It does not convert a stream and does not demonstrate protocol conversion or failover.
For a main/backup contribution, select SRT main/backup failover under SRT Routing, choose Pull, and enter the source hosts and routing ports for both contributions. Write the trigger and expected destination behavior into the event plan, then test actual feeds, buffers and destination behaviour before the event. A transport switch can preserve connected receiver and puller sessions, but the picture transition depends on the prepared feeds, buffers, network conditions and destination.
Use a route choice before browsing device guides
Choose ingress, transparent relay, RTMP publishing or NDI production handoff first. Then use the device directory as a configuration starting point for the selected encoder or camera. Confirm the installed firmware, SRT mode, port, Stream ID, encryption and payload settings against manufacturer documentation before using a device on an event route.
For a small starting configuration, review the SRT relay preset. It starts with one stream and one Restream job; the actual source, destination and receiver test remain yours to configure.