• Need for Public IP Addresses: Each RTSP camera operates as a server, necessitating a public IP address for external access. If multiple cameras are involved, this requires port forwarding configuration.
• Low Efficiency Over Long Distances: The RTSP protocol is not optimized for data transmission over long distances and unreliable communication channels, falling short compared to modern protocols like SRT.

• The configuration file specifies the RTSP camera addresses.
• SRT Streamer PRO connects to the cameras and retrieves the video streams.
• The acquired streams are encapsulated in the SRT protocol without transcoding, reducing the load on the system.
• The SRT streams are transmitted to the designated remote server in the Studio or Control Center.

• Ease of Setup: No complicated network configuration or port forwarding is required.
• Efficiency: The absence of transcoding allows for the use of low-powered computers (our performance test is detailed below).
• Stability and Transmission Distance: The SRT protocol offers reliable data transmission over long distances through unstable communication channels, such as the Starlink satellite internet.

*** Special Offer ***

To launch the new version of SRT Mini Server, we are pleased to announce special offers

for Annual and Permanent licenses!

Send us a request with your

use-case to Office@GaraninApps.com and we will be happy to send you a special offer.

**************************************

• Added UDP multicast with transcoding.

• Changed delay functionality - now it can be used to smooth out breaks in the clip.

• It does not depend on the video codec. It can be used with any video codec while transmitting timecode via SEI is only provided for h264 and HEVC (SEI method)
• It can be easily added to encoders that do NOT support timecode generation. For example you can add it to GoPro and LiveU encoders. All you need to do is to apply the appropriate signal to the audio input.

• We deployed more than 6 cameras on the mountain, all capturing 1080/50p video.
• Tentacle Sync devices were connected to the audio channel 1 of each camera signal to generate LTC timecode.

• All SDI camera signals were routed into Teradek Prism Backpacks equipped with 6 LTE modems for bonded transmission.
• The bonded signals were sent to Teradek Core Cloud, where we accessed individual camera feeds via SRT streams.

• The SRT Mini Server was used to receive and synchronize the SRT streams from the Core Cloud.
• While synchronization was effective, we encountered delays of around 10 seconds, which was manageable during the week but became a challenge during the finals.
• For the finals, we opted for direct SDI or wireless links for critical camera signals while using SRT for Red cameras dedicated to slow-motion shots, where sync precision was less critical.

• Signals from the SRT Mini Server were output via SDI/NDI to our TriCaster Vizion system, where they were combined into the program output (PGM).

1. Operation Without a White IP Address: The ability to work in proxy mode allows direct connection to the set without the need for cloud servers.
2. Cross-Line Functionality: This feature enables the incoming SRT signal to be transmitted to multiple viewers. In the latest release, we removed the limit on the number of viewers, making this feature virtually unlimited.
3. Viewer Grouping: You can configure different streams for different groups of viewers, providing flexibility in managing the viewing experience.
4. Multichannel Audio: SRT supports multichannel audio
5. Low Latency: SRT technology ensures minimal latency, allowing directors to provide feedback in real time.

• Receive two return channels via SRT (e.g., for live interviews or studio intercom).
• Output them to SDI devices (cameras, monitors).

• SDI camera → SRTStreamerPRO → remote proxy-server + SRTMiniServer (simulating distance between location and studio) → SDI monitor (echo)

• For a lagging stream: If a frame from one source arrives with a delay that exceeds a set threshold compared to other streams, it is dropped. This pulls the lagging stream back into sync with the others.
• For a leading stream: If a frame arrives too early, its playback is briefly paused to maintain the overall timing.

• Magewell
• Haivision Makito
• Kiloview

• Improved Synchronization Algorithm: The enhanced sync algorithm for multi-camera streams ensures even more precise and seamless switching between sources.(more >>>)
• Increased RIST-addon Stability: The RIST module is now significantly more resilient to network instability and connection drops, minimizing potential data loss.

• We have implemented support for the promising OMT protocol—an open-source alternative to NDI, developed with support from the creators of vMix. This integration future-proofs your workflow and offers greater flexibility for software integration (more >>>)

• Link Generator: Added a convenient tool for automatically generating streaming URLs for live broadcasts through OBS.

• Advanced Settings: New parameters have been added for granular control:
• tbmauto – For auto start TalkBackManager
• record_format – To select the recording format.
• omt – To configure OMT protocol settings.
• sync_auto_control – To control auto-sync method.

1. Six incoming SRT streams are converted exclusively to NDI, and system metrics are recorded.
2. The same six streams are then converted exclusively to OMT (high), and identical measurements are taken again.

• CPU utilization during NDI and OMT encoding;
• Network bandwidth consumption when 6 clients are simultaneously connected to output streams.

no NDI, no OMT, only decode 6x1080@50p and convert to 422

6 x NDI encoding (no connected clients, so no bandwidth )

now we connect 6 clients (NDI Studio Monitor, macOS)

6 x NDI encoding, 6 x clients

6 x OMT(high) encoding (no connected clients, so no bandwidth )

now we connect 6 clients (OMT Video Monitor, macOS)

6 x OMT(high) encoding, 6 x clients

6 x OMT(low) encoding, 6 x clients

• NDI is optimized for today’s reality: it handles 4:2:0 natively and efficiently, minimizing network load and system resources—making it an excellent choice for established, performance-sensitive production environments.
• OMT, by contrast, is designed with the future in mind. As specified in its documentation, it automatically upgrades incoming 4:2:0 content to 4:2:2:4, delivering superior color fidelity and compatibility with professional workflows where color accuracy is critical—such as studio production, virtual sets, or graphics-intensive applications like chroma keying.

• Caller Mode ("Initiator"): SRTStreamerPRO actively "calls" the specified address and port of the recipient to establish a connection. This is the classic and most direct method.
• Listener Mode ("Waiting"): Now SRTStreamerPRO can act as a "server": it opens a port and waits for the recipient to connect to it. This is especially useful when the recipient is behind complex network infrastructure (e.g., behind a NAT), making it easier for them to initiate the connection.

• Remote Control of Film Production and Events
• UDP Multicast

• DEMO_NDI_PACK — starts the server in NDI/OMT Pack mode.
• DEMO_ROUTING_PACK — starts the server in Routing Pack mode.

• ease of use — how quickly a person without a deep technical background can get a working SDI → SRT setup;
• SDI card support — we'll look at support for SDI cards from various manufacturers (BlackMagic, AJA, Magewell, etc.);
• multi-channel audio — the ability to transmit multiple audio channels, not just stereo;
• NDI support — the ability to capture an NDI source is as important as SDI;
• recovery after connection loss — what happens when the connection is lost.

• Ease of use: Low; the syntax of pipelines and debugging "which element failed to negotiate caps" requires time.
• SDI card support: Maximum support for DeckLink cards. For cards from other manufacturers, you'll need to find plugins from the hardware manufacturers.
• Multi-channel audio: Extremely flexible: splitting tracks, mixing, separate branches for encoding — if the pipeline is built consciously.
• NDI support: Supported via a special plugin. Due to the plugin architecture, unlike FFmpeg, adding the protocol requires installing only this plugin.
• Recovery after connection loss: In the event of an SRT connection break, it will try to reconnect by default without stopping the command.

• Ease of use: The interface might seem somewhat confusing for a beginner, considering that OBS is a powerful tool for a wide range of tasks. While AI can assist by writing commands for FFmpeg and GStreamer, with OBS's interface, you'll need to click around yourself.
• SDI card support: Maximum support for DeckLink cards. For cards from other manufacturers, it works via DirectShow filters, but there may be nuances.
• Multi-channel audio: Capable of sending 6 audio pairs.
• NDI support: so-so.
• Recovery after connection loss: Automatically handles reconnections by default.

• Ease of use: The interface is designed for a single purpose and leaves no room for "getting lost."
• SDI card support: Supports DeckLink, AJA, DekTec, Deltacast, Bluefish444, SoftLab, Magewell.
• Multi-channel audio: Flexible configuration using notation like "1,2,3,4" with the ability to remap and mix channels using notation like "3+4, 1+2".
• NDI support: Excellent.
• Recovery after connection loss: Reconnects a specified number of times.

• guarantee smoother and uninterrupted proxy operation for regular clients;
• reduce the risk of technical issues;
• promptly respond to possible situations involving an increase in the number of simultaneously connected users.

• displays it in multiview alongside SRT and other sources;
• decodes and outputs to NDI for further routing within the studio;
• distributes via SRT to one or more recipients;
• can participate in CrossLine — redirecting the stream to the return channel of another line.

1. An SRT-streaming camera streamed directly to the proxy in Amsterdam.
2. The proxy forwarded the stream to SRTMiniServer.
3. From SRTMiniServer, the signal was output via SDI through a Decklink SDI card to an SDI monitor.

example of SRTMiniServer: read Timecode and Sync

• encoded separately
• transmitted separately over the network
• and can arrive at the receiving end with different delays.

• select up to 4 sources (Quadrants)
• select encoding options
• setup SRT destination
• press Start

• double click START.bat
• open browser http://127.0.0.1:3000

• select up to 4 sources (Quadrants)
• select encoding options
• setup SRT destination
• press Start

We would appreciate your feedback at Support@GaraninApps.com