Terms and Definitions

• AES - Audio Engineering Society

• AIMS - Alliance for IP Media Solutions, an industry consortium led by broadcast and ProAV companies.

• AMWA - Advanced Media Workflow Association, Inc. began in January 2000 as the Advanced Authoring Format (AAF) Association, Inc. The organization's name was officially changed in May 2007 to better reflect the direction and scope of the association and its mission statement. AMWA currently focuses on the industry move to IP based architectures. To enable software based systems to recognize and exploit devices, the AMWA has developed the Networked Media Open Specifications (NMOS). These have been created in practical workshops by the Networked Media Incubator project. The AMWA continues its support for the Media Exchange Format (MXF), the Advanced Authoring Format (AAF) and the Framework for Interoperable Media Services (FIMS).

• Anagram - An anagram is a word or phrase formed by rearranging the letters of a different word or phrase, typically using all the original letters exactly once.

anagram
Algorithmic anagram test using multisets as canonical forms: The strings "madam curie" and "radium came" are given as C arrays. Each one is converted into a canonical form by sorting. Since both sorted strings literally agree, the original strings were anagrams of each other.

• CNAME - A Canonical Name (CNAME) record is a type of resource record in the Domain Name System (DNS) that maps one domain name (an alias) to another (the canonical name). This can prove convenient when running multiple services (like an FTP server and a web server, each running on different ports) from a single IP address. One can, for example, use CNAME records to point ftp.example.com and www.example.com to the DNS entry for example.com, which in turn has an A record which points to the IP address. Then, if the IP address ever changes, one only has to record the change in one place within the network: in the DNS A record for example.com. CNAME records must always point to another domain name, never directly to an IP address.

• JT-NM - Joint Taskforce on Network Media
The group coordinate helping broadcasters transition from circuit-switch SDI working to IP workflows suitable for delivering content to today's multi-platform, mixed-consumption, IP-savvy consumers. Group Members include the Advanced Media Workflow Association (AMWA), the European Broadcasting Union (EBU), the Society of Motion Picture and Television Engineers (SMPTE©), and the Video Services Forum (VSF).

• NDI - Network Device Interface
NDI is a royalty-free protocol developed by NewTek to enable video-compatible products to share video across a local area network (LAN). NDI allows multiple video systems to identify and communicate with one another over IP and to encode, transmit, and receive many streams of high-quality, low latency, frameaccurate video and audio in real time. NDI operates bi-directionally over a LAN with many video streams on a shared connection. Its encoding algorithm is resolution and frame-rate independent supporting 4K resolutions and beyond along with 16 channels and more of floating-point audio. The protocol also includes tools that implement video access rights, grouping, bi-directional metadata, and IP commands.

• NDI❘HX - NDI is available in some devices and applications using a different compression codec than high bandwidth NDI. This variation is known as NDI❘HX, which stands for NDI ‘High Efficiency’. Devices that using this version of NDI will be labeled with the HX moniker. HX offers for similar video quality at a much lower bit rate, which can be useful in situations where bandwidth is limited, like Fast Ethernet networks, WiFi or WAN connections.

There are two variations of NDI❘HX. NDI❘HX v1 which requires the use of an ‘HX Driver’ which is included with NDI Tools and NDI❘HX v2 which can directly connect with NDI applications. NDI❘HX v1 is no longer used for new product development, new NDI❘HX products released into the market will use NDI❘HX v2. NDI 5 remote connections use NDI❘HX for transmission of signals over the Internet.

• NMOS - Networked Media Open Specifications
This is an open-source set of protocols and associated software for discovery, registration, connection, and management of ST 2110 networks

• PTP (IEEE 1588) - Precision Time Protocol

• REST - is an acronym for REpresentational State Transfer and an architectural style for distributed hypermedia systems. Roy Fielding first presented it in 2000 in his famous dissertation. Since then it has become one of the most widely used approaches for building web-based APIs (Application Programming Interfaces). More info

• RIST - The Reliable Internet Stream Transport protocol is similar to SRT, containing a special packet loss algorithm that reduces error, providing high quality and highly reliable broadcast stream. RIST is unique when it comes to protection. RIST Safelink protects live video and audio over unsecured networks.

• RTMP, Dante, Others etc. - There is also RTMP streaming, which is arguably on its way out but is used heavily by FLASH and Mobile IOS and ANDROID streaming apps AND DANTE and AES67 for audio- and many more than we’re not listing here. And that’s the point – with all these IP “cars” driving ‘fast’ on the virtual highway, we need to create standards and best practices – to keep each video or audio stream in its lane.

• SDP - Session Description Protocol
Ensures that receivers know the nature of all flows arriving through the IP port.

• SRT - This is a transmission protocol based on the H.264 / H.265 compression scheme. The focus here is on delivering high-quality video. SRT’s anti-packet loss mechanism is an ARQ, which is an Automatic Repeat Request error correction mechanism, removing jitter or packet drops that can sometimes happen to video. Delay for point-to-point transmission is under 1s. SRT is made to transmit signals over the internet but it is important to note that SRT transmission applications require a fixed public IP address on either the sender or the receiver.

• TCP, Multipath - This protocol permits transport across multiple NICs and all network paths, it is ensigned to use hardware-accelerated network adapters with adaptive bandwidth sharing across NICs.

Multipath TCP helps to maximize throughput, resource usage, and increase redundancy across the network, and is not disrupted by adding or dropping pathways and works across multiple network types such as wireless and mobile.

• UDP with Forward Error Correction - This is an alternative protocol to TCP that is used when reliable delivery of data packets in not required. UDP is typically used for applications where timeliness is of higher priority than accuracy, such as streaming media, teleconferencing, and voice-over-IP (VoIP). Forward error correction (FEC) is a method of obtaining error control in data transmission in which the source (transmitter) sends redundant data and the destination (receiver).

• UDP, Reliable - high-performance approach to transferring video and audio on a network. Real world testing has shown that in many problematic network configurations that performed poorly with previous versions of NDI and other video protocols now work perfectly with this version.

This uses a highly optimized UDP sender that supports very high latency connections (e.g., WAN or WiFi networks), with state-of-the-art congestion control and loss recovery (far superior to other reliable transfer protocols used in the industry), full inter-stream bandwidth management and connection sharing, no front of line queue blocking, reduced number of open ports and fully asynchronous sending and receiving.

• VSF - Video Services Forum