Network Device Interface

NDI is designed to run over existing Gigabit networks,[1] with the NDI codec[2] expected to deliver 1080i HD video at VBR data rates typically around 100 Mbit/s.[3]

By Default, NDI uses the mDNS (Bonjour / Zeroconf) discovery mechanism to advertise sources on a local area network, such that NDI receiving devices can automatically discover and offer those sources, although 2 other discovery modes (NDI Access, NDI Discovery Server) allow for operations across subnets, and without mDNS. Sources are created using an arbitrarily selected TCP port from a range of ports on the NDI send host. When a source is requested a TCP connection is established on the appropriate port with the NDI receiver connecting to the NDI sender. NDI 3.x has options to use UDP Multicast or Unicast with FEC(Forward error correction) instead of TCP, and can load balance streams across multiple Gigabit NICs without link aggregation, whilst NDI 4.0 introduces Multi-TCP connections.

NDI carries video, multichannel uncompressed audio and metadata. Metadata messages can be sent in both directions allowing the sender and receiver to message one another over the connection with arbitrary metadata in XML form.[4] This directional metadata system allows for functionality such as active tally information fed back to sources to understand that they are on-air (program / preview). NDI also allows senders to determine the number of connected receivers, so they can skip unnecessary processing and network bandwidth utilisation when there are no NDI receiver clients connected. NDI Receivers can opt to connect to various combinations of streams, to support things like audio-only or metadata-only connections where video is not required.

The SDK is available for Windows, Linux and macOS,[5] and has also been ported to iOS, tvOS,[6] Android, Raspberry Pi, and FPGA.[7][8] The SDK is available via a royalty-free proprietary license.[9]

Other IP video protocols emerging for use in professional video production (rather than IP video used for distribution to end users) include SMPTE 2022, SMPTE 2110, ASPEN (largely superseded by SMPTE 2110) and Sony NMI. There are clear differences in the technology used by these protocols.

*The TICO codec can be used to compress UHD by 4:1 so an encoded stream can be carried along a SMPTE 2022-6 channel at the same uncompressed bandwidth as HD.[17] SMPTE 2110 with TR-03 also offers the potential to use TICO.[18] This requires a proprietary encoder and decoder which are generally implemented as silicon on each end. * * NDI v1.0 was pure TCP. Later versions included options for UDP Unicast and Multicast as appropriate and FEC. NDI 4.0 adds 'Multi-TCP' transport. NDI|HX is generally UDP but uses TCP control commands. * * * Tally for SMPTE 2110 relies on external data sources, using proposed AMWA IS 07.

NDI was publicly revealed by NewTek on 8 September 2015 and was demonstrated at the IBC broadcast exhibition in Amsterdam that week.[19] The first device shown using NDI was the NewTek TriCaster which delivered an NDI feed from each of its SDI inputs as well as 4 output feeds from its vision mixer. TriCaster could also receive up to 2 NDI sources from other devices (increased to 12 in later releases and up to 44 in NewTek's IP Series ).[20]

NDI devices from other vendors followed during 2016. The first third-party products came from Gallery Sienna and included an NDI signal generator for macOS, a desktop scan converter for macOS and the NDICam camera app for iPhone which delivers a native NDI stream from iOS devices.[21][22]

NewTek had previously created a predecessor of NDI called AirSend to get video from external devices into their TriCaster products. AirSend had been implemented by a number of CG manufacturers including VizRT and Chyron. In order to quickly bring these products into the NDI space, NewTek created a new driver to replace the existing AirSend driver, which could be installed on these existing AirSend compatible devices, instantly converting them to NDI compatible devices with no change required by the original CG vendors.[23]

Another early adopter of NDI was VMix, a Windows-based vision mixer which offers NDI inputs and outputs.[24] A significant increase in the NDI installed base came when live streaming application XSplit added support for NDI.[25]

Later in 2016, NewTek delivered NDI 2.0 which added features including support for service discovery across subnets. In the first half of 2017, BirdDog began demonstrating and shipping BirdDog Studio NDI - a PoE powered portable FPGA based NDI encoder with HDMI and SDI inputs with Tally, supporting up to 1080p60 video resolutions.[8] On 12 July 2017 NewTek announced NDI 3.0 which added multicast, NDI/HX and other new features, introducing support for specific PTZ Cameras with H.264 chipsets and updated firmware.[26]

In April 2018 at the NAB Show, Microsoft announced they had added NDI support to Skype for Content Creators.[27] Other announcements at NAB2018 included NDI 3.5, and new NDI support from vendors including EVS[28] and Avid.[29]

Version 3.4 of ffmpeg added input and output support for NDI when optionally compiled by the end-user to a non-opensource NewTek library.[30] However, NewTek was later found to be redistributing pre-compiled binaries of FFmpeg that incorporated their non-opensource library in violation of the GNU General Public License, causing the FFmpeg project to remove NDI support from their codebase in March 2019.[31][32]

In April 2019 ahead of NAB NewTek announced the addition of Multi-TCP mode to NDI 4.0 which is reported to leverage hardware TCP acceleration present in silicon, assisting lower spec processors with NDI transport.[33] NDI 4.0 shipped in September 2019 to coincide with the IBC exhibition.

NDI was designed to work on good quality gigabit local area networks using TCP and Bonjour (mDNS) technologies. In order to work across subnets which don't pass mDNS, NDI supports a mechanism known as NDI Access which allows manual entry of the IP address of machines on other subnet which may be running NDI sources.

Some NDI adopters have run the protocol across medium distance Fibre connections up to 15 km, although NDI's use of the TCP protocol make it less suitable for longer distance, high latency connections due to factors such as bandwidth-delay product and TCP packet loss recovery.[34] The NDI 3.5 libraries now default to a UDP transfer method with forward error correction that removes the latency requirements that are inherent with TCP connections. NDI|HX uses a lower data rate making it easier to use in bandwidth limited connections.[26]

To provide an extension of NDI to wide area networks, tools have been developed including the Sienna Cloud for NDI[35] protocol which uses node gateways in each LAN to bridge NDI sources across continents.[36] In July 2017, USSSA (United States Speciality Sports Association) successfully made the first truly wide area network NDI sports coverage using Cloud for NDI with 5 cameras backhauled across the public internet from a stadium, to 200 miles away into an NDI based production gallery.[37]

NDI is also used within cloud-based production systems[38], with its compressed video and non-reliance on multicast making it a perfect fit for cloud-based data centres like AWS and Azure. in 2019 Sienna demonstrated a complete cloud-based production workflow using NDI, including remote contribution using Sienna. Cloud or SRT, cloud-based processing, including VisionMixing, graphics and audio manipulation, leading to final publishing via CDNs like YouTube Live.

NDI, when running on x86 architectures, requires CPUs that include the SSSE3 (Supplemental Streaming SIMD Extensions 3) instruction set. Most Intel CPU designs starting in 2006 have this instruction set, AMD added support starting in 2011.

While not a requirement, NDI will take advantage of AVX (Advanced Vector Extensions) and AVX2 instructions sets for additional performance. While NDI itself doesn't require these instructions, applications might.

NDI can run on 32-bit or 64-bit CPU architectures, although performance is increased when using 64-bit, and 32-bit support may not be available in future versions of the macOS and iOS NDI libraries.

NDI is available for ARM-based systems with encode support, but generally not video decode. Exceptions to this are Sienna NDI Monitor[39] for iOS which does provide NDI decoding on ARM, and Sienna NDI Monitor TV for AppleTV 4k[40].

NDI|HX devices are typically transmit-only and based on proprietary platforms with hardware H.264 encoder chips. Examples are NDI|HX devices are PTZ cameras, and the NDI Connect Spark SDI to NDI|HX converter box. The NDI stream itself is formed at the stream consumption end via the platform specific NDI|HX driver, presenting the same uncompressed data to the application software consuming the NDI source regardless of original HX source hardware and compression. NDI|HX2 is a purer implementation of H.264 in NDI packets, and will allow software and hardware systems to embed H.264 essence into NDI streams using the NDI Embedded SDK.

NewTek, Birddog and Magewell have all developed FPGA encoding implementations of NDI. In April 2018 NewTek announced the Connect Spark Pro which will be their first FPGA based NDI product. Birddog and Magewell also offer FPGA-based decode of full NDI streams (not NDI|HX). Newtek offers a licensable FPGA reference design for third-party NDI encoders as part of their NDI Embedded SDK.

With NDI 4.0 NewTek announced the addition of a 'Multi-TCP' transport mode. This takes advantage of the hardware TCP acceleration in silicon which helps lower spec processors handle heavy network load, in contrast to UDP which does not benefit from the hardware acceleration.[41]

NDI supports arbitrary metadata as XML blocks, embedded in video and audio frames, as well as stand-alone metadata frames. The content of these metadata blocks form 3 families.

• Internal Metadata used by NDI invisibly. These messages are used for connectivity and some other fundamental tasks like Tally. They are typically invisible to NDI clients.
• Defined Public Metadata. These messages include things like the NDI PTZ Protocol. They are defined by NewTek as part of the NDI SDK.
• Third-party Metadata schemes. These messages are implemented in the same way as Defined NDI Metadata but the content is based on 3rd party designs. Over time these third-party metadata schemes may become widely used and perhaps adopted as officially supported.

There are 8 published examples of third-party NDI metadata schemes:

• In August 2018, Gallery Sienna published a proposal[42] for the carriage of C708 Closed Caption metadata via NDI. It involves capture of the appropriate line of SDI VANC data, and text based encoding to be compatible with XML. This is carried as video frame-based attached metadata. It can be passed to an equivalently compatible decoder for reconversion to SDI along with intact C708 captions. Gallery Sienna implemented this standard into their Sienna NDI SourceMulti product[43], and the proposal is also being adopted by other NDI product developers. A companion proposal for a universal caption format[44] for NDI has since been published, providing a human readable, rather than binary container for closed captions in NDI Metadata streams.

• In February 2019, Gallery Sienna published a proposal[45] for the carriage of MIDI messages via NDI. This uses real time stand alone NDI Metadata frames to carry any sort of Midi message including Midi Machine Control, and controller data. NDI Midi is used within Sienna's NDI Processing Engine[46] as a generic control protocol between modules and the outside world.

• In April 2019, Gallery Sienna published a proposal[47] for the use of the industry standard iXML Metadata protocol within NDI. iXML allows for unambiguous description of stream contents, and linkage between streams.

• In April 2019, Gallery Sienna published a proposal[48] for the carriage of PTPv2 timing and GMID within NDI. Sienna also implemented this as a Precision_Time_Protocol converter which captures this data and feeds it as NDI into multiple NDI systems wanting to share this information, such as software to interact with AES67 devices.

• In September 2019, Gallery Sienna published a proposal[49] for the definition and carriage of sub-region stream definition within NDI. This can be used for definition of video wall subcuts of a stream, or for applications like AI analysis of video where a system is following a face in a stream, or following a football - with a pan scan subcut of the stream. This is also used to deliver sub-stream definitions for social media publishing with non standard aspect ratios - for example, portrait or square video for phones.

• In November 2019, Gallery Sienna published a proposal[50] for the definition of the HDR Metadata description profile for HDR NDI Streams

• In December 2019, Gallery Sienna published a proposal[51] for the communication of GPI State via NDI connections. This mechanism is implemented in Sienna's GPI Interface module in the NDI Processing Engine[52] which interfaces with the JLCooper Ebox[53] GPI interface, supporting 24 GPI Inputs and Outputs.

• In December 2019, Gallery Sienna published a proposal[54] for the communication of DMX data via NDI connections. This mechanism is implemented in Sienna's ArtNet-DMX Interface module in the NDI Processing Engine[55] which interfaces with the LTECH Artnet-DMX-1 DMX interface, supporting 512 DMX Channels in or out.

Other non-published NDI metadata schemes are also in use, for things like triggering CG animations.