Live video gateway

NDI encoder software for broadcast IP production

An NDI encoder converts a video source into Network Device Interface (NDI) format, making it available as an NDI stream on an IP network for NDI-compatible devices, software, and systems to receive.

NDI has become a widely used protocol for IP-based production workflows. Production switchers, multiviewers, recording systems, graphics platforms, and software production tools commonly support NDI as a native input. Converting a video source to NDI makes it immediately accessible to the NDI production ecosystem, without dedicated video cables, physical routing infrastructure, or point-to-point SDI connections.

BridgeWIZ is Tricube's GPU-accelerated NDI encoder software. It accepts professional video sources including SDI, HDMI, ST2110, SRT, RTMP, HLS, YouTube Live, and screen capture, and encodes them to full-bandwidth NDI in real time through a full GPU processing pipeline. NDI is one of several simultaneous outputs: the same source can deliver to NDI, SRT, RTMP, SDI, UDP, and local ISO recording from one encoding pass.

What is NDI and why it matters for broadcast production

Network Device Interface is an IP video standard developed by NewTek, now part of Vizrt, for distributing broadcast-quality video over standard Ethernet networks. NDI lets video sources on a network be discovered and received by NDI-compatible devices and software on the same network, without dedicated video infrastructure.

NDI key characteristics:

No dedicated video hardware

NDI runs over standard Gigabit Ethernet, the same network infrastructure already present in most facilities. It needs no dedicated video cabling or routing hardware, and no network infrastructure beyond what already exists.

Broadcast quality

Full-bandwidth NDI delivers broadcast-quality video, typically at 100 to 200 Mbps for HD content, with minimal compression and latency suitable for live production workflows.

Automatic discovery

NDI sources are automatically discovered on the local network. In most network environments, an NDI-compatible receiver can see and connect to NDI sources without manual IP configuration.

Wide ecosystem support

NDI is supported by a large and growing ecosystem of professional broadcast hardware and software, including production switchers, graphics systems, multiviewers, recording platforms, monitoring tools, and software production environments.

Low latency

NDI delivers video with sub-frame latency on local networks, which suits live production workflows where timing between sources is critical.

Sources BridgeWIZ encodes to NDI

BridgeWIZ accepts the following sources for NDI encoding:

SDI and HDMI

From Blackmagic Design DeckLink, AJA, Magewell, Deltacast, and Bluefish444 professional capture hardware. Legacy SDI cameras, routers, and production equipment become NDI sources on the production network.

SMPTE ST2110

ST2110 IP media sources are encoded to NDI, making ST2110 infrastructure accessible to NDI production systems, multiviewers, and software tools without separate gateway hardware.

SRT

Incoming SRT contribution feeds are decoded and re-encoded to NDI, so remote production contributions become NDI sources on the local production network.

RTMP

Incoming RTMP streams are decoded and re-encoded to NDI, bringing streaming platform feeds into local NDI production workflows.

HLS and RTSP

Network stream sources decoded and re-encoded to NDI output.

YouTube Live

YouTube Live streams ingested and published as NDI sources on the local network.

Screen capture

Full screen, window, and custom region capture can be published as NDI, making computer display output available to any NDI-compatible system on the network.

How NDI encoding works in BridgeWIZ

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

  1. Stage 1: Source ingest

    BridgeWIZ receives the incoming source, such as SDI from capture hardware, NDI from the network, ST2110 from IP media infrastructure, SRT from a remote contribution, or screen capture from a computer display.

  2. Stage 2: GPU decoding

    The incoming source is decoded on NVIDIA, Intel, or AMD GPU hardware. GPU decoding reduces CPU load and increases the number of simultaneous NDI encodings 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: NDI encoding

    The processed video is encoded as full-bandwidth NDI at broadcast quality with minimal compression. The NDI source name is configurable per instance and appears automatically in NDI discovery on the local network.

  5. Stage 5: NDI network output

    The NDI stream is published to the local network, where NDI-compatible devices, software, and systems can discover and receive it immediately without manual IP configuration.

Simultaneous outputs from one source

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

  • NDI: full-bandwidth network output
  • SRT: for remote contribution or distribution
  • RTMP: for streaming to YouTube or Facebook
  • SDI: physical output to legacy broadcast infrastructure
  • UDP: multicast or unicast network delivery
  • Local ISO file: independent recorded file per source

One source feeds multiple simultaneous outputs from one GPU processing pass, without separate encoder appliances.

Live graphics on NDI encoding

BridgeWIZ's built-in HTML graphics engine adds live broadcast graphics to the source during NDI encoding. Graphics are rendered in the GPU pipeline and embedded in the NDI output stream published to the network:

  • Scrolling tickers and news banners
  • Lower thirds and name straps
  • Logo overlays and watermarks
  • Date and time displays
  • Live time counter and elapsed time
  • Custom HTML templates

Add channel branding, live news graphics, or identification overlays to a source during NDI encoding, without a separate CG system. Every NDI receiver on the network receives the complete signal, including graphics.

NDI encoding use cases in broadcast

SDI camera to NDI production network

SDI cameras connected to capture hardware in a BridgeWIZ server become NDI sources, available to NDI-compatible production switchers, multiviewers, recording systems, and software tools on the network. Each camera uses one BridgeWIZ instance, with multiple instances running on a single GPU server.

ST2110 to NDI production tools

ST2110 sources from IP media infrastructure are encoded to NDI, making professional ST2110 signals accessible to software production tools, multiviewers, and monitoring systems that support NDI but not ST2110 natively.

Remote contribution to NDI production

Incoming SRT contribution feeds from remote locations are decoded and published as NDI sources on the local production network, so production switchers and software tools can use remote contributors exactly as if they were local NDI sources.

Screen capture to NDI

Presentation slides, graphics software, and computer display content are captured and published as NDI, feeding production switchers, multiviewers, and recording systems without dedicated scan converter hardware.

YouTube Live to NDI monitoring

YouTube Live streams are ingested and published as NDI sources on the local network, so streaming platform output can be monitored through NDI-compatible multiviewers and monitoring tools.

Resolution scaling during NDI encoding

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

  • 4K SDI or ST2110 source encoded to HD NDI for bandwidth-efficient distribution on the production network
  • HD source encoded to SD NDI where required
  • Frame rate conversion where NDI receivers require a different frame rate

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

Multi-instance NDI encoding

Run multiple independent BridgeWIZ instances on a single GPU server, each encoding a different source to NDI at the same time. Each instance publishes its own named NDI source to the network, which NDI receivers discover separately.

For facilities that need multiple simultaneous NDI encodings, such as multi-camera productions, multi-channel facilities, and broadcast operations moving from SDI to NDI, multiple instances on one GPU server can take the place of several dedicated hardware NDI encoder appliances.

How BridgeWIZ differs from hardware NDI encoders

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

BridgeWIZ performs NDI encoding in software on GPU-accelerated server hardware. It accepts ST2110 and SRT alongside SDI and HDMI, and includes simultaneous additional outputs, live graphics, resolution scaling, and ISO recording. Multiple instances on one server handle multiple simultaneous NDI encodings without additional hardware.

FAQs

What is NDI encoder software used for in broadcast?

NDI encoder software converts video sources into Network Device Interface streams and publishes them on an IP network for NDI-compatible devices, software, and production systems to receive. It brings legacy SDI equipment, ST2110 infrastructure, remote SRT contributions, and screen capture into NDI-based IP production workflows without dedicated hardware per source.

What video sources can BridgeWIZ encode to NDI?

BridgeWIZ encodes SDI, HDMI, ST2110, SRT, RTMP, HLS, RTSP, YouTube Live, and screen capture to full-bandwidth NDI. Any professional video source accepted by BridgeWIZ can be published as an NDI source on the local network.

Does BridgeWIZ output full-bandwidth NDI?

Yes. BridgeWIZ outputs full-bandwidth NDI at broadcast quality for professional facility workflows. Full-bandwidth NDI is the appropriate standard for studio and facility use where network bandwidth is not a constraint.

Can BridgeWIZ encode ST2110 sources to NDI?

Yes. BridgeWIZ accepts ST2110 as a native input and encodes it to NDI, making ST2110 infrastructure accessible to NDI production systems, multiviewers, and software tools without separate ST2110 to NDI gateway hardware.

How many simultaneous NDI encodings can BridgeWIZ handle?

Multiple BridgeWIZ instances run independently on a single GPU server, each encoding a different source to NDI and publishing its own named NDI source to the network. Channel count scales with GPU server specification, without buying additional hardware NDI 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.