Live video gateway

SDI to NDI encoder software

SDI to NDI encoding converts a Serial Digital Interface broadcast signal, the professional standard for studio, production, and transmission environments, into Network Device Interface format for distribution across an IP network.

SDI is the foundation of traditional broadcast infrastructure. Cameras, routers, monitors, production switchers, and playout systems have communicated via SDI for decades. NDI is the IP production standard that lets the same equipment and software communicate over a standard Ethernet network, without dedicated video cables, dedicated routing hardware, or point-to-point SDI connections.

Converting SDI to NDI is the fundamental step that integrates legacy SDI equipment into modern IP production workflows. A camera with SDI output becomes an NDI source accessible to any software or hardware on the network. A legacy SDI router output becomes available to NDI-compatible production systems, monitors, and recording tools. SDI infrastructure built years or decades ago participates in modern IP workflows without replacement.

BridgeWIZ performs SDI to NDI encoding in real time through a full GPU processing pipeline, with simultaneous additional outputs and live graphics, on standard server hardware.

Why SDI to NDI encoding matters

The broadcast industry is in transition. SDI remains the dominant physical signal standard in operational broadcast facilities, because routing infrastructure, transmission chains, and installed equipment represent significant capital investment that cannot be replaced overnight. NDI is the production standard for software-based workflows, supporting virtual production, remote collaboration, and IP-based signal distribution without the physical cabling constraints of SDI.

SDI to NDI encoding bridges this transition. It lets existing SDI infrastructure take part in NDI workflows without replacement, extending the operational life of SDI equipment while adding the flexibility of IP production.

Common SDI to NDI encoding scenarios:

Legacy camera integration

SDI cameras connected to an SDI to NDI encoder become NDI sources, available to any NDI-compatible software, production system, or monitor on the network. Each camera uses one encoder instance, and the instances run on a single GPU server.

SDI router output to IP production

SDI router outputs converted to NDI feed IP production systems, multiviewers, and software tools that accept NDI but not SDI directly.

Facility SDI to IP transition

Broadcast facilities moving from SDI to IP infrastructure use SDI to NDI encoding to bring existing SDI equipment into the new IP environment during the transition, without replacing working equipment early.

SDI monitoring to software multiviewers

SDI programme and preview outputs converted to NDI feed software multiviewers and monitoring tools on standard computers, without dedicated SDI monitoring hardware at every workstation.

OB SDI to production network

Outside broadcast vehicles with SDI internal routing convert programme and camera feeds to NDI for integration with IP-based production tools and remote collaboration workflows.

Supported SDI hardware for BridgeWIZ

BridgeWIZ receives SDI input through professional capture hardware installed in the server:

AJA

AJA Corvid, Kona, and Io capture cards with SD-SDI, HD-SDI, 3G-SDI, and HDMI inputs. AJA SDK updated to version 17.5.

Blackmagic Design DeckLink

The full range of DeckLink capture cards, from DeckLink Mini Recorder to DeckLink 8K Pro. Blackmagic SDK updated to version 15.3.

Bluefish444

Professional SDI capture with ancillary data support. Bluefish API updated to version 6.6.

Deltacast

SDI capture solutions supporting SD, HD, 3G, and 4K SDI with full ancillary data. Deltacast SDK updated to version 6.28.

Magewell

Pro Capture cards supporting SDI and HDMI inputs.

Yuan

SDI and HDMI capture hardware for broadcast and professional AV applications.

All supported hardware captures the complete SDI signal, including video, embedded audio, ancillary data, and timecode, and passes it to the BridgeWIZ GPU processing pipeline for encoding and output.

How SDI to NDI encoding works in BridgeWIZ

BridgeWIZ performs SDI to NDI encoding through a five-stage GPU processing pipeline:

  1. Stage 1: SDI capture

    The SDI signal is captured by the installed capture card from AJA, Blackmagic, Bluefish444, Deltacast, Magewell, or Yuan. The complete SDI signal is captured, including video, embedded audio, ancillary data, and timecode. SDI capture operates at the hardware interface level.

  2. Stage 2: GPU decoding

    The captured SDI signal passes into the GPU processing pipeline and is decoded on NVIDIA, Intel, or AMD GPU hardware. The GPU handles all later pipeline stages from this point.

  3. 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 GPU hardware.

  4. Stage 4: NDI encoding

    The processed video is encoded as full-bandwidth, broadcast-quality NDI output with minimal added latency from the encoding stage. NDI output is available immediately on the network for any NDI-compatible receiver.

  5. Stage 5: NDI network output

    The NDI stream is published to the local network, where any NDI-compatible device, software, or system can discover it. The NDI source name is configurable per instance.

Simultaneous outputs from one SDI source

BridgeWIZ encodes SDI to NDI as one output among several simultaneous destinations. The same SDI source delivers simultaneously to:

  • NDI: full-bandwidth network output
  • SRT: for remote contribution or distribution
  • RTMP: for streaming to YouTube or Facebook
  • SDI: re-output as SDI to downstream hardware
  • UDP: multicast or unicast network delivery
  • Local ISO file: independent recorded file per source

One SDI source feeds multiple simultaneous outputs from one GPU processing pass, with no additional hardware.

Live graphics on SDI to NDI encoding

BridgeWIZ's built-in HTML graphics engine adds live broadcast graphics to the SDI signal during encoding, before the NDI output is published. Graphics are rendered in the GPU pipeline and embedded in the NDI 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 identification overlays to SDI sources during encoding to NDI, without a separate CG system.

Resolution scaling during SDI to NDI encoding

BridgeWIZ performs resolution scaling and format conversion during SDI to NDI encoding, independently of the SDI source parameters:

  • 4K SDI source encoded to HD NDI output
  • HD SDI source encoded to SD NDI for bandwidth-constrained network segments
  • Frame rate conversion where the NDI destination requires a different frame rate
  • Colour space conversion where required

The NDI output format is fully independent of the SDI source format.

Multi-instance SDI to NDI encoding

Run multiple independent BridgeWIZ instances on a single GPU server, each encoding a different SDI source to NDI at the same time. Each instance has its own SDI input hardware, its own NDI output configuration, and its own graphics setup.

Multi-camera OB vehicles, multi-channel playout centres, and broadcast facilities with large SDI router installations often need several SDI to NDI conversions at once. Multiple instances on one GPU server can take the place of several dedicated hardware encoder appliances.

HDR SDI to NDI

BridgeWIZ supports HDR metadata from SDI sources, both HLG and PQ, natively through the GPU processing pipeline. HDR metadata is preserved in the NDI output stream without downconversion, so the HDR signal stays technically accurate through the SDI to NDI encoding process.

How BridgeWIZ differs from hardware SDI to NDI encoders

Dedicated hardware SDI to NDI encoder boxes perform one fixed conversion: one SDI input to one NDI output. Each box handles one channel, so expanding to multiple channels means buying more boxes, with more rack space, power, maintenance, and licences.

BridgeWIZ performs SDI to NDI encoding in software on GPU-accelerated server hardware, with simultaneous additional outputs, live graphics, resolution scaling, HDR support, and ISO recording included. Multiple instances on one server handle several SDI to NDI encodings at once without additional encoder hardware.

FAQs

What is SDI to NDI encoding used for in broadcast?

SDI to NDI encoding brings legacy SDI equipment into modern IP production workflows by making SDI cameras, routers, and playout systems available as NDI sources on an IP network. It is the basic step that connects traditional SDI infrastructure to NDI-based production environments during facility transitions.

What SDI formats does BridgeWIZ support for NDI encoding?

BridgeWIZ supports SD-SDI, HD-SDI, and 3G-SDI inputs through AJA, Blackmagic Decklink, Bluefish, Deltacast, Magewell, and Yuan capture hardware. The specific SDI formats supported depend on the capture card installed in the server.

Does BridgeWIZ output simultaneous destinations alongside NDI during SDI encoding?

Yes. BridgeWIZ encodes SDI to NDI as one output among several simultaneous destinations, including SRT, RTMP, SDI re-output, UDP, and local ISO file recording. All of them come from the same SDI source in one GPU processing pass.

Can BridgeWIZ add graphics during SDI to NDI encoding?

Yes. BridgeWIZ's built-in HTML graphics engine adds live broadcast graphics, such as tickers, lower thirds, logos, and custom HTML templates, to the SDI signal during encoding. Graphics are embedded in the NDI output stream without a separate CG system.

How many simultaneous SDI to NDI encodings can BridgeWIZ handle?

Multiple BridgeWIZ instances run independently on a single GPU server, each encoding a different SDI source to NDI. The number of channels depends on the GPU server specification, and adding instances does not require additional hardware encoder appliances.

Get started

See BridgeWIZ working with your sources

Book a demo and our broadcast engineers will demonstrate BridgeWIZ using your sources, destinations, and channel requirements.