Content deleted Content added
review: also VSF. wrap control. ws. |
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5 |
||
| (9 intermediate revisions by 4 users not shown) | |||
Line 10:
==Technology==
NDI is designed to run over [[gigabit Ethernet]]<ref>{{cite web|url=https://www.provideocoalition.com/newtek-announces-ndi-an-open-protocol-for-ip-production-workflow/|title=NewTek announces NDI, an open protocol for IP production workflow by Allan Tépper|first=ProVideo|last=Coalition|date=8 September 2015}}</ref> with the NDI codec.<ref>{{cite web|url=http://support.newtek.com/hc/en-us/articles/218109667-NDI-Encoding-Decoding|title=NDI Encoding/Decoding|website=NewTek Knowledge Base}}</ref> It delivers [[1080i]] [[high-definition video]] at [[variable bitrate|variable data rate]]s typically around {{nowrap|100 Mbit/s}}.<ref>{{cite web|url=https://support.newtek.com/hc/en-us/articles/217662708-NDI-Network-Bandwidth|title=NDI Network Bandwidth|website=NewTek Knowledge Base|access-date=2017-03-09|archive-date=2021-04-11|archive-url=https://web.archive.org/web/20210411005049/https://support.newtek.com/hc/en-us/articles/217662708-NDI-Network-Bandwidth|url-status=dead}}</ref>
By default, NDI uses [[multicast DNS]] to advertise sources on a [[local area network]], such that NDI receivers can automatically discover and offer those sources. It also supports two other discovery modes (NDI Access, NDI Discovery Server) that allow for operations across [[subnet]]s and without multicast DNS. Sources are created using an arbitrarily selected [[TCP port]] from a range of ports on the NDI senders. 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 [[User Datagram Protocol|UDP]] [[multicast]] or [[unicast]] with [[forward error correction]] (FEC) instead of TCP, and can [[Load balancing (computing)|load balance]] streams across multiple [[network interface controller]]s (NICs) without using [[link aggregation]]. NDI version 4.0 introduces the ''Multi-TCP'' transport.
NDI carries video, [[Surround sound|multichannel]] [[uncompressed audio]],{{Citation needed|date=September 2020|reason=Please link to an official source verifying this claim}} and [[metadata]].
The NDI [[software development kit]] (SDK) is available for [[Windows]], [[Linux]], and [[MacOS]],<ref>{{cite web|url=https://www.newtek.com/ndi/sdk/|title=NewTek NDI SDK|website=Newtek.com}}</ref> and has also been ported to [[iOS]], [[tvOS]], [[Android (operating system)|Android]], [[Raspberry Pi]], and [[FPGA]].{{cn|date=January 2025}} The Standard NDI SDK is available via a royalty-free [[Proprietary_software|proprietary]] license.<ref>{{cite web |title=NDI® license agreement |url=http://new.tk/ndisdk_license/ |website=new.tk |accessdate=3 June 2020}}</ref> The NDI Advanced SDK offers OEMs direct access to and from compressed data and other features, with a commercial license.
Line 178:
{{efn-ua|name=TCP|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 5.0 adds 'Reliable-UDP' transport . NDI|HX is generally UDP but uses TCP control commands.}}
{{efn-ua|name=Tally|Tally for SMPTE 2110 relies on external data sources, using proposed AMWA IS 07.}}
}}<!--[[User:Kvng/RTH]]-->▼
==History==
NDI was publicly revealed by NewTek on 8 September 2015 and was demonstrated at the
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 [[character generator]] (CG) vendors including [[Vizrt]] and [[ChyronHego|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.<ref>{{cite web|url=http://pages.newtek.com/NDI-Upgrader-Download.html|title=NDI AirSend Updater-NewTek|website=pages.newtek.com}}</ref>
BirdDog was an early adopter and in 2018
Another early adopter of NDI was [[VMix]], a Windows-based vision mixer
Later in 2016, NewTek delivered NDI 2.0, which added features including support for service discovery across subnets. In April, Magewell announced
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]] [[chipset]]s and updated [[firmware]].<ref name="newtek.com">{{cite web|url=https://www.newtek.com/press-releases/ndi-v3/|title=NewTek NDI® Version 3 Offers the Only End-to-End IP Video Solution for Product Manufacturers|website=NewTek}}</ref>
In April 2018 at the [[NAB Show]], Microsoft announced they had added NDI support to [[Skype|Skype for Content Creators]].<ref name="blogs.skype.com">{{cite web|url=https://blogs.skype.com/news/2018/04/06/make-collaboration-the-heart-of-your-live-streams-podcasts-and-videos-with-skype-for-content-creators/|title=Make collaboration the heart of your live streams, podcasts, and videos with Skype for Content Creators|date=6 April 2018|website=Skype Blogs}}</ref> Other announcements at
Version 3.4 of [[FFmpeg]] added input and output support for NDI when optionally compiled by the end-user to a non-open-source NewTek library.<ref>{{cite web|url=https://www.newtek.com/blog/ffmpeg-3-4-adds-ndi-io/|title=FFmpeg 3.4 Adds NDI I/O|first=Chuck|last=Baker|publisher=NewTek|date=December 6, 2017}}</ref> However, NewTek was later found to be redistributing pre-compiled binaries of FFmpeg that incorporated their non-
In April 2019, ahead of NAB, NewTek announced the addition of Multi-TCP mode to NDI 4.0 which
In July 2021, NDI 5 was released adding
{| class="wikitable"
|-
! Version !! Released !! Features
|-
| 1.0|| April 2016 || Initial Release
Line 209:
| 2.0|| Sept 2016 || Cross subnet support via Access Manager, ARM encoding support, iOS SDK
|-
| 3.0|| July 2017 || NDI-HX support, Option for multicast transport with FEC, PTZ support
|-
| 3.5|| June 2018 || Defaults to Unicast UDP transport method with FEC
|-
| 3.6|| July 2018 || Packet level bonding improvements
|-
| 3.7|| Sept 2018 || Discovery improvements
|-
| 3.8|| Nov 2018 || Performance Enhancements, NDI Embedded SDK for FPGA development
|-
| 4.0|| Sept 2019 || Multi-TCP Transport mode, HDR 16-bit support, Native synchronized recording, Discovery Server, NDI HX2<ref name="nab2019plans"/>
|-
| 4.1|| Nov 2019 || Performance improvements
|-
| 4.5|| March 2020 || New Multi-TCP implementation, Lower latency with NDI-HX, Predictable port numbers for firewall rules, Improvements to codec quality
|-
| 4.6|| Nov 2020 || Can support NDI-HX2 encoding on PC's using NVENC
|-
| 5.0|| July 2021 || Reliable UDP transmission, Redundant discovery server support, NDI 5 Tools (Bridge, Remote, Audio Direct, FCP-X output)
|-
| 5.1|| Feb 2022 || NDI Bridge enhancements, DNS name support for Discovery Server, SDK improvements
|-
| 5.5|| Aug 2022 || NDI Router, Quad Inputs on NDI Webcam Input with 4K video support, NDI Remote adds Talkback and desktop sharing features, Auto start applications on system boot, NDI FreeAudio command line tool (found with SDK)
|-
| 6.0|| Apr 2024 || Added specification for NDI HDR metadata, Improved support for 16-bit colour formats, NDI Bridge Utility for Linux, NDI-KVM support for Video Monitor on macOS, NDI Router for macOS, NDI Studio Monitor on Windows enhanced with HDR support for display and recording
|-
|6.1
|Dec 2024
|NDI Bridge improvements, NDI Bridge service, 16-bit
▲|}
==Use in Wi-Fi and wide area networks==
Line 255:
NDI 4.x and earlier had limited support for [[ARM architecture family|ARM]], generally offering encode-only support. The release of NDI 5 brings full support for encode and decode on ARM-based processors that include [[Neon (instruction set)|Neon instructions]]. This includes [[Apple silicon]] processors.
NDI|HX devices are typically transmit-only and based on proprietary platforms with hardware H.264 encoder chips. Examples of NDI|HX devices are [[Pan–tilt–zoom camera|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, supporting either H.264 or HEVC compression, and allows for additional NDI features.
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]].<ref>{{Cite web | url=https://www.tvtechnology.com/news/newteks-andrew-cross-talks-about-the-acquisition-discusses-nab-show-plans |title = NewTek's Andrew Cross Discusses Acquisition, NAB Show Plans| date=3 April 2019 }}</ref>
==Metadata and extensions to the NDI specification==
| |||