## Overview The **Configuration** page is the central place to set up the **SRT Overlord**. It allows operators to: - Enable optional features such as **Test Stream** and the built-in **RTSP Server**. - Configure the **SRT output destination** where all streams are sent to an **ORBNET Streaming Engine**. - Add and manage **manual input sources** (RTSP streams or MPEG-TS over UDP). After ONVIF inputs or manual input source have been configured, a restart of the SRT Overlord app is recommended to apply the changes. Once restarted, all inputs will automatically be transmitted over SRT protocol to the destination and the the streams will restart automatically if disconnected. Besides adding cameras via the **ONVIF Devices** page, operators can also add input sources from here. It is available at the route: **/config**. ![[Config page - Overview.png|800]] <div style="page-break-after: always;"></div> ## Page Sections ### Test Stream ![[Config page - Test Stream.png|400]] The **Test Stream** option enables a built-in test source (NTP-synced / absolute time) that helps verify connectivity and end-to-end delivery to **ORBNET Streaming Engine**. When enabled: - Overlord generates an **additional stream** that will be also listed in the **Streams table** from **Status** page. - The same stream should be visible/received on the **ORBNET Streaming Engine** side, confirming the SRT path is working. > [!warning] > **Important considerations** > > - **High CPU usage:** the test stream can consume significant CPU resources. > > - **Restart required:** enabling this option requires a **restart of SRT Overlord** to take effect. > > > This option is intended for **connection testing**, not continuous operation on low-resource devices. ![[Config page - Test Stream Visual.png|500]] - The test stream show an old-school broadcast color palate with a white vertical bar scanning along the horizontal axis and a black square moving diagonally --- ### RTSP Server ![[Config page - RTSP Server.png|400]] The **RTSP Server** option enables Overlord’s built-in RTSP server. When enabled: - Overlord starts an **RTSP server** that clients like VLC or ORBNET Low-Latency Player can connect to. - The server listens for new connections on the port specified in **RTSP Server Port**. This is useful for: - **Verifying** streams are working _inside Overlord_ (independent of SRT output). - **Restreaming** Overlord-managed streams to other endpoints via RTSP. > [!tip] > If a stream is healthy via the built-in **RTSP server** but fails over SRT, the issue is likely in the **Output (SRT) configuration**, routing, firewall, or Streaming Engine receiver side. --- ### Input Sources ![[Config page - Input Sources.png|500]] The **Input Sources** section defines additional streams that Overlord should collect manually (besides **ONVIF Devices** page). It shows both manual inputs configured here and the connected ONVIF devices listed under **Connected Devices** on the **ONVIF Devices** page (`/onvif-devices`). Supported input types: - **MPEG-TS over UDP** – Overlord listens on a UDP port for an incoming transport stream. - **RTSP Stream** – Overlord pulls a stream from an RTSP URL (camera/encoder/source). Typical actions: - **Add** – Create a new input definition. - **Edit** – Modify the selected input (input type, RTSP URL, RTSP Mode, TS Port, Stream Key). - **Remove selected** – Remove the currently selected input. --- ### Output ![[Config page - Output.png|500]] The **Output** section defines the single SRT destination where **all streams** are sent (the **ORBNET Streaming Engine** receiver). Fields: - **SRT URL** – Base SRT destination address of the Streaming Engine receiver. - **Passphrase** – SRT encryption passphrase. Must match the receiver configuration. The maximum number of allowed characters is 79, which is recommended for maximum AES-256 security. - **Max Latency (ms)** – Maximum one-way latency buffer in milliseconds. ORBNET's custom SRT implementation will aim to keep the latency as low as possible, even if the latency is set to high values. The maximum latency value will influence how much video data each stream will keep in RAM locally to ensure retransmission in case of latency spikes. > [!note] > **Latency** here is an SRT buffering setting for transport stability. It is not the same as “glass-to-glass” viewing delay. > Setting a high latency will not be sufficient to ensure a high quality stream if the average available total bandwidth is too low. --- ### Save Configuration ![[Config page - save button.png|200]] Click **Save Configuration** to apply changes. After saving: - Input changes should reflect on the **Status** page stream list. - Some changes (for example **Test Stream**) may require a **service restart** as noted. --- | BACK | FORWARD | | ------------------------------------------------------------------------- | ------------------------------- | | [[ORB SRT Overlord/1.0.0/Website/ONVIF Devices page\|ONVIF Devices page]] | [[ORB SRT Overlord/1.0.0/Website/Open API Documentation page]] | <div class="page-break" style="page-break-before: always;"> </div>