Content deleted Content added
m I fixed small grammar mistake. |
m unpiped links using script |
||
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 is expected to deliver [[1080i]] [[
By default, NDI uses the [[mDNS]] ([[Bonjour (software)|Bonjour]] / [[Zeroconf]]) discovery mechanism to advertise sources on a [[local area network]], such that NDI receiving devices can automatically discover and offer those sources. It also supports 2 other discovery modes (NDI Access, NDI Discovery Server) that allow for operations across [[subnet]]s and without mDNS. Sources are created using an arbitrarily selected [[Transmission Control Protocol|TCP]] [[Port (computer networking)|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 [[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]]. The release of NDI version 4.0 introduces the 'Multi-TCP' transport.
Line 16:
NDI carries video, multichannel [[uncompressed audio]],{{Citation needed|date=September 2020|reason=Please link to an official source verifying this claim}} 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.<ref>{{cite web|url=http://www.content-technology.com/standards/?p=578|title=NewTek Announces NDI – Open Protocol for IP Production Workflow - Technical Standards|website=Content-technology.com}}</ref> This directional metadata system allows for functionality such as active [[Tally light|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 NDI [[software development kit]] (SDK) is available for [[
==Comparison of common IP video protocols==
Line 190:
Another early adopter of NDI was [[VMix]], a Windows-based vision mixer which offers NDI inputs and outputs.<ref>{{cite web|url=https://www.thebroadcastbridge.com/content/entry/5589/studiocoast-vmix-adopts-newtek-ndi-standard|title=StudioCoast vMix Adopts NewTek NDI Standard - The Broadcast Bridge - Connecting IT to Broadcast|first=The Broadcast|last=Bridge|website=Thebroadcastbridge.com| date=18 April 2016 }}</ref> A significant increase in the NDI installed base came when live-streaming application [[XSplit]] added support for NDI.<ref>{{cite web|url=http://www.marketwired.com/press-release/xsplit-broadcaster-adopts-newtek-ndi-for-ip-production-workflow-2114230.htm |title=XSplit Broadcaster Adopts NewTek NDI for IP Production Workflow |website=Marketwired.com |date=2016-04-12 |accessdate=2017-05-23}}</ref>
Later in 2016, NewTek delivered NDI 2.0 which added features including support for service discovery across subnets. In April, Magewell announced seamless integration of their [[
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]] [[
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 NAB2018 included NDI 3.5, and new NDI support from vendors including EVS<ref name="sportsvideo.org">{{cite web|url=https://www.sportsvideo.org/2017/09/05/evs-x-one-production-system-takes-software-based-tech-to-new-level/|title=EVS X-One Production System Takes Software-Based Tech to New Level|first=Ken Kerschbaumer, Editorial|last=Director|website=Sports Video Group| date=5 September 2017 }}</ref> and Avid.<ref name="https://www.newtek.com/blog/avid">{{Cite web | url=https://www.newtek.com/blog/avid/ | title=Avid Media Composer Integrates NewTek NDI®}}</ref>
Line 238:
==Use in Wi-Fi and wide area networks==
NDI was designed to work on good quality [[Gigabit Ethernet|gigabit local area networks]] using TCP and Bonjour ([[
Some NDI adopters have run the protocol across [[Fiber-optic communication|fibre]] connections up to 15 km, although NDI's use of the TCP protocol makes it less suitable for long-distance, [[Network latency|high-latency]] connections due to factors such as [[bandwidth-delay product]] and [[Transmission Control Protocol|TCP packet loss recovery]].<ref>{{cite web|url=http://westreamu.se/2016/05/09/documentary-stockholm-kista-cross-production-using-ndi-over-fiber/|title=Documentary: Stockholm Kista cross production using NDI over fiber|first=Richard|last=Gatarski|date=9 May 2016|website=Weststreamu.se}}</ref> Later versions of NDI introduced different transport protocols including UDP, MultiTCP and reliable UDP ([[QUIC]]) which offer different network characteristics. NDI|HX uses a lower data rate making it easier to use in bandwidth-limited connections.
==Use in cloud-based infrastructure==
NDI is also used within [[
==CPU architecture support==
NDI, when running on [[x86]] or [[x86-64]] [[CPU Architecture|architectures]], requires CPUs that include the [[SSSE3]] 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 [[Advanced Vector Extensions]] (AVX) and [[AVX2]] instruction sets for additional performance.
NDI can run on [[
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
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 [[
==Metadata and extensions to the NDI specification==
| |||