Live video gateway

NDI to SDI Decoder Software

NDI to SDI decoding converts a Network Device Interface (NDI) video signal, distributed across an IP network, into a Serial Digital Interface (SDI) signal for output to legacy broadcast hardware, routing infrastructure, and SDI-based equipment.

NDI supports modern IP production workflows, connecting software tools, IP cameras, and production systems across a standard Ethernet network. In most broadcast facilities, though, significant SDI infrastructure remains in active operation. Production switchers, routing matrices, transmission encoders, broadcast monitors, and playout systems built around SDI cannot accept NDI input directly. NDI to SDI decoding bridges this gap by converting NDI sources from the IP production environment back to SDI for SDI-based downstream equipment.

NDI to SDI decoding is the return path of SDI to NDI encoding. Together they form a complete bridge between IP production workflows and legacy SDI infrastructure, so both environments can coexist and exchange content during the industry's transition from SDI to IP.

BridgeWIZ performs NDI to SDI decoding in real time through a full GPU processing pipeline on standard server hardware, outputting physical SDI signals through Blackmagic Design hardware.

Why NDI to SDI decoding is needed

The broadcast industry's transition from SDI to IP infrastructure is gradual, and few facilities replace all SDI equipment at once. In practice, most run a mixed environment: NDI sources from software production tools, IP cameras, and remote contributors coexist with SDI routers, production switchers, monitors, and transmission infrastructure that cannot be replaced immediately.

NDI to SDI decoding lets NDI content from the IP production environment reach SDI-based downstream equipment, without replacing working hardware or running parallel signal paths.

Common NDI to SDI decoding scenarios:

NDI software sources to SDI router

Software production tools such as graphics systems, virtual production software, and playout applications output NDI. NDI to SDI decoding converts these outputs to SDI for routing through existing SDI matrix routers to downstream equipment.

Remote NDI contribution to SDI production

Remote contributors sending NDI over IP, from remote production hubs, OB locations, or remote production software, are converted to SDI for input to SDI-based production switchers and routing infrastructure.

IP production to SDI transmission

Programme feeds produced in NDI-based IP production environments are converted to SDI for delivery to SDI-based transmission encoders, uplink equipment, and distribution infrastructure.

NDI monitoring on SDI monitors

NDI sources from IP production systems are converted to SDI for display on professional SDI broadcast monitors, giving reference-quality monitoring without replacing existing SDI monitoring infrastructure.

Software playout to SDI infrastructure

Software-based playout systems outputting NDI are converted to SDI for delivery to SDI-based master control equipment, routing infrastructure, and transmission systems.

Supported SDI output hardware for BridgeWIZ

BridgeWIZ outputs SDI signals through Blackmagic Design DeckLink hardware installed in the server. Depending on the card model, DeckLink output cards support HD-SDI, 3G-SDI, and 4K SDI output, feeding downstream SDI equipment directly from the BridgeWIZ GPU processing pipeline.

The current BridgeWIZ platform uses Blackmagic SDK version 15.3 for compatibility with current DeckLink hardware generations.

How NDI to SDI decoding works in BridgeWIZ

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

  1. Stage 1: NDI ingest

    BridgeWIZ discovers and receives the NDI source from the local network. NDI-compatible devices and software on the network are available as inputs, including production systems, software tools, hardware NDI devices, and remote contributors.

  2. 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.

  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: SDI encoding

    The processed video is prepared for SDI output and converted to the SDI format the downstream hardware requires. Resolution, frame rate, and SDI standard are configurable per output.

  5. Stage 5: SDI physical output

    The SDI signal is output through the installed Blackmagic DeckLink hardware, delivering a physical SDI signal to downstream broadcast equipment exactly as a hardware SDI source would.

Simultaneous outputs from one NDI source

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

  • SDI: physical output to legacy broadcast infrastructure
  • NDI: re-output as NDI to another part of the network
  • SRT: for remote contribution or distribution
  • RTMP: for streaming to YouTube or Facebook
  • 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 SDI decoding

BridgeWIZ's built-in HTML graphics engine adds live broadcast graphics to the NDI signal during decoding, before the SDI output is generated. Graphics are rendered in the GPU pipeline and embedded in the physical SDI output:

  • 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 NDI sources during decoding to SDI, without a separate CG system.

Resolution scaling during NDI to SDI decoding

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

  • 4K NDI source decoded to HD SDI output
  • HD NDI source decoded to SD SDI for legacy SD infrastructure
  • Frame rate conversion where SDI downstream equipment requires a different frame rate
  • Colour space conversion where required

The SDI output format is fully independent of the NDI source format, so an NDI source at one resolution can feed SDI infrastructure running a different standard.

Multi-instance NDI to SDI decoding

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

For facilities that need multiple simultaneous NDI to SDI conversions, such as multi-channel production environments, broadcast facilities with large SDI router installations, and playout centres with multiple SDI outputs, multiple instances on one GPU server can take the place of several dedicated hardware decoder appliances.

HDR NDI to SDI

BridgeWIZ supports HDR metadata natively through the GPU processing pipeline. HDR content received as NDI with HLG or PQ metadata is preserved through decoding and SDI output without downconversion. Where the downstream SDI equipment supports it, HDR NDI sources reach SDI infrastructure with their HDR metadata intact.

How BridgeWIZ differs from hardware NDI to SDI decoders

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

BridgeWIZ performs NDI to SDI decoding 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 multiple simultaneous NDI to SDI decodings without additional decoder appliances.

FAQs

What is NDI to SDI decoding used for in broadcast?

NDI to SDI decoding converts NDI sources from IP production environments into physical SDI signals for legacy broadcast hardware, such as production switchers, routing matrices, transmission encoders, and broadcast monitors that accept SDI but not NDI. It lets NDI content reach SDI-based downstream infrastructure without replacing existing equipment.

What SDI output formats does BridgeWIZ support for NDI decoding?

BridgeWIZ outputs HD-SDI, 3G-SDI, and 4K SDI through Blackmagic Design DeckLink hardware. The available SDI output formats depend on the DeckLink card installed in the server. BridgeWIZ uses Blackmagic SDK version 15.3.

Does BridgeWIZ output simultaneous destinations alongside SDI during NDI decoding?

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

Can BridgeWIZ add graphics during NDI to SDI decoding?

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 decoding. Graphics are embedded in the physical SDI output without a separate CG system.

How many simultaneous NDI to SDI decodings can BridgeWIZ handle?

Multiple BridgeWIZ instances run independently on a single GPU server, each decoding a different NDI source to SDI at the same time. Channel count scales with GPU server specification, without buying additional hardware decoder 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.