> For the complete documentation index, see [llms.txt](https://docs.timeinpixels.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.timeinpixels.com/nobe-omniscope/outputs/srt-output.md).

# SRT Output

{% hint style="info" %}
This feature requires a **Pro** license.
{% endhint %}

SRT Output allows you to stream video from OmniScope using the Secure Reliable Transport (SRT) protocol. SRT is designed for low-latency, secure streaming over unpredictable networks, including the internet.

## Overview

SRT Output is ideal for:

* Remote monitoring over the internet
* Streaming to cloud-based services
* Secure transmission of video content
* Reliable delivery over unreliable networks

## Requirements

* OmniScope Pro license
* Network connection
* SRT-compatible receiver (software or hardware)

## Setup

### Enabling SRT Output

1. Go to **View** > **Output Settings** or click the output icon in the toolbar
2. Select **SRT** from the output type dropdown
3. Configure the connection settings
4. Click **Start streaming**

### Connection Modes

For a manual SRT destination, enter the complete **SRT URL** and select a connection mode. The mode selector and the `mode` value in the URL stay synchronized.

| Mode           | Description                              | Use Case                                                          |
| -------------- | ---------------------------------------- | ----------------------------------------------------------------- |
| **Caller**     | OmniScope connects to a remote listener  | Streaming to a server                                             |
| **Listener**   | OmniScope waits for incoming connections | Receiving pulls from clients                                      |
| **Rendezvous** | Both endpoints connect to each other     | Peer-to-peer connections where both endpoints use Rendezvous mode |

If the URL does not include a mode, OmniScope uses **Caller** mode.

In current beta builds, Listener and Rendezvous outputs keep waiting for a receiver until you stop the output. A missing receiver or ended connection does not stop the waiting output automatically.

### Connect an iPad by QR code

For the simplest setup in current beta builds, use **Add iPad** instead of **Add SRT**. Follow [Desktop to iPad](https://docs.timeinpixels.com/nobe-omniscope-for-ipad/desktop-to-ipad.md) for the illustrated walkthrough with automatic network selection. The controls below describe the alternative SRT output setup.

OmniScope 1.11.55 and later on macOS, or 1.11.58 and later on Windows, can connect the OmniScope iPad app without typing a pairing code:

1. In **SRT Output**, choose **Scan with iPad**.
2. Select the desktop's local network address and port.
3. Click **Start streaming**, then **Show pairing QR code**.
4. On the iPad, open **Sources** > **Connect to OmniScope Desktop** > **Scan desktop QR code**.
5. Scan the code shown by the desktop. Both devices must be on the same local network.

On Windows, allow OmniScope through Windows Firewall on the trusted local network if prompted.

The iPad remembers the scanned desktop in Keychain so you can reconnect later. Use **Reset QR pairing** on the desktop to revoke the previous code and generate a new pairing key.

{% hint style="warning" %}
The QR code grants access to the stream. Hide it before sharing screenshots or recordings.
{% endhint %}

If the iPad cannot use its camera, choose **Enter iPad code** on the desktop and use the pairing code shown by the iPad instead.

### Settings

| Setting         | Description                                                           | Default |
| --------------- | --------------------------------------------------------------------- | ------- |
| SRT URL         | Destination or local listener URL, including any advanced SRT options | -       |
| Connection mode | Caller, Listener, or Rendezvous                                       | Caller  |
| Latency         | Buffer latency in milliseconds                                        | 120ms   |
| Passphrase      | Optional encryption key supplied in the SRT URL                       | None    |
| Output Mode     | Source only or scope view                                             | Source  |

### Output Modes

| Mode   | Description                        |
| ------ | ---------------------------------- |
| Source | Sends only the input video signal  |
| Scopes | Sends the full OmniScope interface |

Video delivery does not wait for audio samples. A source without audio, or whose audio stops, continues to send video.

## Connection Examples

### Streaming to a Server (Caller Mode)

1. Enter the server's SRT URL
2. Select **Caller** mode
3. Optionally include a passphrase in the SRT URL for encryption
4. Click **Start streaming**

### Allowing Remote Connections (Listener Mode)

1. Enter a local SRT URL, such as `srt://0.0.0.0:9000?mode=listener`
2. Select **Listener** mode
3. Optionally include a passphrase in the SRT URL
4. Click **Start streaming**
5. Share your IP address and port with receivers

## Security

SRT supports AES encryption for secure transmission:

1. Add a `passphrase` option to the **SRT URL**
2. Share the same passphrase with receivers
3. All data will be encrypted in transit

{% hint style="warning" %}
Always use encryption when streaming over public networks or the internet.
{% endhint %}

## Performance Tuning

### Latency Setting

The latency buffer helps handle network jitter:

| Network Type           | Recommended Latency |
| ---------------------- | ------------------- |
| Local LAN              | 20-50ms             |
| Stable internet        | 120-200ms           |
| Unstable/long distance | 500-1000ms          |

Lower latency = less delay but more sensitive to network issues. Higher latency = more delay but more resilient.

### Bandwidth Requirements

SRT streams are encoded; bandwidth depends on encoder settings:

| Resolution | Typical Bandwidth |
| ---------- | ----------------- |
| 1080p30    | 5-15 Mbps         |
| 1080p60    | 10-25 Mbps        |
| 4K30       | 20-50 Mbps        |

## Troubleshooting

### Connection Failed

1. Verify the remote address and port are correct
2. Check firewall settings on both ends
3. Ensure the receiver is in the correct mode (Listener if you're Caller)
4. Try increasing the latency setting

{% hint style="info" %}
If the encoder fails to initialize repeatedly, OmniScope will back off and stop retrying every frame automatically. Click **Apply Settings** to clear this recovery block and attempt a fresh connection.
{% endhint %}

### Poor Quality or Artifacts

1. Increase the latency setting
2. Check network bandwidth availability
3. Reduce output resolution or frame rate

### High Latency

1. Reduce the latency setting (if network allows)
2. Use a closer server/receiver
3. Check for network congestion

## Tips

* Start with higher latency and reduce gradually to find the optimal setting
* Use Listener mode when you have a static IP and want others to connect to you
* Use Caller mode when connecting to a known server or service
* SRT works well over WiFi and cellular networks due to its error correction

## Related

* [SRT Input](https://docs.timeinpixels.com/nobe-omniscope/sources/srt-stream.md) - Receive SRT streams in OmniScope
* [NDI Output](https://docs.timeinpixels.com/nobe-omniscope/outputs/ndi-output.md) - LAN-based streaming alternative
* [SDI Out](https://docs.timeinpixels.com/nobe-omniscope/live-pack-add-on/sdi-out.md) - Hardware SDI output
