Product guide
SRT Redundancy Proxy
Forward one SRT input to two destinations with the free edition or run multiple relay instances with MULTI.
Editions
Compare editions
Paid editions include all features of the Free edition, plus the capabilities listed below.
| Function | SRT Redundancy Proxy | SRT Redundancy Proxy MULTI |
|---|---|---|
| One SRT Listener input per relay instance | ○ | ○ |
| Up to two SRT Caller outputs per relay instance | ○ | ○ |
| Independent output enable controls | ○ | ○ |
| Automatic startup with saved settings | ○ | ○ |
| Live connection and forwarding statistics | ○ | ○ |
| Local application logs | ○ | ○ |
| Multiple independent relay instances | × | ○ |
○ Included · × Not included
Current version: Version not verified for either edition.
Overview
Use this guide to relay one SRT input to as many as two destinations while viewing the forwarding state. The free edition runs one relay instance. The paid MULTI edition runs multiple independent relay instances.
Key features
- Receive one SRT stream on a configurable listener port.
- Forward the input to two independently enabled SRT destinations.
- Start automatically with saved settings when required.
- Display input and output connection state, bitrate, RTT, packet and byte counts, drops, and errors.
- Open the local application log folder for troubleshooting.
- Run one free-edition instance as
ID=1.
Installation
- Install the application from the Microsoft Store link below.
- Document the input mode and port and the settings for both destinations.
- Confirm that every required UDP path is allowed by the applicable firewalls.
Basic configuration
- Configure and start the input side first.
- Configure each Caller output with its receiver address and port.
- Leave an unused output disabled instead of entering an unverified destination.
- Check the displayed state for the input and each enabled output.
Settings
| Setting | Purpose | Available values |
|---|---|---|
| Input port | Set the listener port for the incoming SRT stream. | 1–65535 |
| Output 1 address | Set the first SRT receiver address. | Host or IP address |
| Output 1 port | Set the first SRT receiver port. | 1–65535 |
| Output 1 | Enable or disable forwarding to the first destination. | On or Off |
| Output 2 address | Set the second SRT receiver address. | Host or IP address |
| Output 2 port | Set the second SRT receiver port. | 1–65535; leave blank to use one output only |
| Output 2 | Enable or disable forwarding to the second destination. | On or Off |
Main operations
Verify that input packets are arriving before troubleshooting an output. Test destinations one at a time, then confirm both together.
Local test
Start one or two listeners:
ffplay "srt://0.0.0.0:9100?mode=listener"
ffplay "srt://0.0.0.0:9200?mode=listener"
With the proxy listening on port 9000, send an MPEG-TS stream to its input:
ffmpeg -re -i input.ts -c copy -f mpegts "srt://127.0.0.1:9000?mode=caller"
The default local destinations are 127.0.0.1:9100 and 127.0.0.1:9200.
MULTI workflow
- Create the required relay instances.
- Give every listener on the same network interface a unique input port.
- Configure each input and its associated outputs independently.
- Start and verify one relay path before enabling the next.
- Maintain a written mapping between each instance, source, and destinations.
- Confirm aggregate network and system capacity as instances are added.
Network roles
- Input: SRT Listener
- Output 1 and Output 2: SRT Caller
- Processing: payload relay without video or audio transcoding
System requirements
- Windows 10 or Windows 11
- SRT-compatible sender and receiver applications
- Network access between the sender, proxy, and receivers
Checks before use
- A second output provides another destination; it does not repair a failed source or shared network path.
- Confirm the capacity of the outgoing network for both copies.
- Configure receiver addresses, UDP ports, firewall rules, and stream handling for every path.
- In MULTI, check for listener-port conflicts before troubleshooting stream content.
- Do not expose listening ports directly to untrusted networks.
Troubleshooting
Use the status display to identify whether the input or one output is affected. See the relay FAQ.