NDI and SRT serve different purposes in a broadcast workflow. NDI is designed for high-quality, low-latency video distribution within a local area network, between production systems, software tools, and network-connected devices in the same facility or campus. SRT is designed for reliable video transport over unpredictable networks such as the public internet, cellular connections, and long-distance IP links, where packet loss, jitter, and bandwidth variation are real operational factors.
Converting NDI to SRT connects these two environments. Content produced and distributed internally on NDI, from software production tools, NDI cameras, and IP production systems, is converted to SRT for delivery to remote locations, streaming platforms, contribution destinations, and distribution networks outside the local facility.
BridgeWIZ performs this conversion in real time through a full GPU processing pipeline, with no dedicated hardware converter required.
Why NDI to SRT conversion is needed
NDI assumes a reliable, high-bandwidth local network. A typical NDI stream carries 100 to 200 Mbps of video data. That is practical on a gigabit LAN but impractical over the public internet or a WAN connection.
SRT compresses video to a fraction of the NDI bandwidth, typically 5 to 20 Mbps for HD content, and adds error correction, retransmission, and encryption that make it reliable over unpredictable networks.
NDI to SRT conversion is therefore the standard workflow step that takes content from the production environment, where NDI is the native protocol, to the distribution environment, where SRT handles reliable delivery over IP infrastructure.
Common NDI to SRT conversion scenarios:
Remote production contribution
A production facility using NDI internally needs to send a programme feed to a remote location, such as a satellite uplink facility, a remote production hub, or a broadcast partner. NDI carries the signal within the facility, and SRT carries it to the remote destination.
Streaming platform delivery
NDI sources from production systems are converted to SRT for delivery to a streaming platform or CDN that accepts SRT input. This gives a reliable, low-latency path from production to distribution.
Multi-site broadcast operations
Broadcasters operating across multiple sites use NDI locally at each site and SRT for signal transport between sites, connecting production facilities, playout centres, and transmission sites over IP infrastructure.
OB contribution to base
Outside broadcast operations produce content locally on NDI, feeding cameras, graphics systems, and production tools. SRT carries the programme feed from the OB location back to the base facility over a cellular or satellite IP connection.
How NDI to SRT conversion works in BridgeWIZ
BridgeWIZ performs NDI to SRT conversion through a five-stage GPU processing pipeline:
Stage 1: NDI ingest
BridgeWIZ discovers and receives the NDI source from the local network. Any NDI-compatible device or software source on the network is available as an input, including cameras, production systems, software encoders, and hardware NDI devices.
Stage 2: GPU decoding
The incoming NDI signal is decoded on NVIDIA, Intel, or AMD GPU hardware. GPU decoding reduces CPU load and increases the number of simultaneous conversions possible on a single server.
Stage 3: GPU processing
The decoded video passes through the GPU processing pipeline for format conversion, resolution scaling, and frame rate conversion where required, and graphics overlay if configured. All processing runs on the GPU.
Stage 4: SRT encoding
The processed video is encoded to H.264 or H.265/HEVC using NVIDIA NVENC, Intel Quick Sync, or AMD hardware acceleration, at the bitrate and quality settings configured for the SRT destination.
Stage 5: SRT output delivery
The encoded stream is delivered as SRT output in caller, listener, or rendezvous mode to the configured destination. SRT encryption is available for secure delivery over public networks.
Simultaneous outputs from one NDI source
BridgeWIZ converts NDI to SRT as one output among several simultaneous destinations. The same NDI source can deliver simultaneously to:
- SRT: for remote contribution or distribution
- RTMP: for streaming to YouTube or Facebook
- NDI: re-output as NDI to another part of the network
- SDI: physical output to legacy broadcast infrastructure
- UDP: multicast or unicast network delivery
- Local ISO file: independent recorded file per source
One NDI source feeds multiple simultaneous outputs from one GPU processing pass, without separate decoder appliances.
Live graphics on NDI to SRT conversion
BridgeWIZ's built-in HTML graphics engine adds live broadcast graphics to the NDI signal during conversion, before the SRT output is encoded. Graphics are rendered in the GPU pipeline and embedded in the converted SRT stream:
- Scrolling tickers and news banners
- Lower thirds and name straps
- Logo overlays and watermarks
- Date and time displays
- Custom HTML templates
Add channel branding, live news graphics, or compliance overlays to NDI sources during conversion to SRT, without a separate CG system.
Resolution scaling and format conversion
BridgeWIZ performs resolution scaling and frame rate conversion during NDI to SRT conversion, independently of the source parameters:
- 4K NDI source converted to HD SRT output
- HD NDI source converted to SD SRT for bandwidth-constrained destinations
- Frame rate conversion, such as 50p to 25p or 60p to 30p, where the destination requires a different frame rate
- H.264 or H.265/HEVC output, configurable per SRT destination
The output format is fully independent of the NDI source format.
Multi-instance NDI to SRT conversion
Run multiple independent BridgeWIZ instances on a single GPU server, each converting a different NDI source to SRT at the same time. Each instance has its own NDI input, its own SRT output configuration, and its own graphics setup.
Multi-channel contribution facilities, teleports, and multi-site broadcast operations often need several NDI to SRT conversions at once. Multiple instances on one GPU server can take the place of several dedicated hardware converter appliances.
How BridgeWIZ differs from hardware NDI to SRT converters
Dedicated hardware NDI to SRT converter boxes perform one fixed conversion: one NDI input to one SRT output. Each box handles one channel, so expanding to multiple channels means buying more boxes.
BridgeWIZ performs NDI to SRT conversion in software on GPU-accelerated server hardware, with simultaneous additional outputs, live graphics, resolution scaling, and ISO recording included. Multiple instances on one server handle several NDI to SRT conversions at once without additional converter hardware.
FAQs
What is NDI to SRT conversion used for in broadcast?
NDI to SRT conversion takes content distributed on a local network via NDI and converts it to SRT for reliable delivery over the public internet, remote contribution, or distribution to destinations outside the local network. It is the standard workflow step connecting internal NDI production environments to external SRT distribution and contribution paths.
What is the difference between NDI and SRT?
NDI is designed for high-quality, low-latency video distribution within a local area network, typically at 100 to 200 Mbps per stream. SRT is designed for reliable video transport over unpredictable networks such as the public internet and WAN connections, at much lower bandwidth, with error correction and encryption. NDI to SRT conversion connects internal production to external distribution.
Does BridgeWIZ support simultaneous NDI to SRT conversion and other outputs?
Yes. BridgeWIZ converts NDI to SRT as one output among several simultaneous destinations, including RTMP, NDI re-output, SDI, UDP, and local ISO file recording. All of them come from the same NDI source in one GPU processing pass.
Can BridgeWIZ add graphics during NDI to SRT conversion?
Yes. BridgeWIZ's built-in HTML graphics engine adds live broadcast graphics, such as tickers, lower thirds, logos, and custom HTML templates, to the NDI signal during conversion. Graphics are embedded in the SRT output stream without a separate CG system.
How many simultaneous NDI to SRT conversions can BridgeWIZ handle?
Multiple BridgeWIZ instances run independently on a single GPU server, each converting a different NDI source to SRT. The number of channels depends on the GPU server specification, and adding instances does not require additional hardware appliances.