Specs
SPECIFICATIONS
The AMWA develops specifications and technologies to facilitate the deployment and operation of efficient media workflows. There are three types of specifications - Application Specifications, Data Model Specifications, and Interface Specifications. The AMWA also publishes Best Current Practices. More information on each of these document types is provided at the foot of this page.
To make sure that projects are clearly defined, adequately resourced and successful, we have a process to carefully manage proposals from start to finish. We welcome all new ideas to advance workflows. The AMWA Specification Process document provides information on how AMWA projects are started, the different types of AMWA Specifications, and the different levels of AMWA Specifications. Although first designed to meet a known requirement, a specification can be updated, either because the original user has refined their needs or because a new member wishes to capitalise on the previous work and slightly extend the capabilities of the specification.
View AMWA Specification Process
All Specifications
Edit metadata interchange using AAF. Includes base set of effects.
Project Owner: Phil Tudor, phil.tudor@bbc.co.uk
Published & STABLE
AAF Edit Protocol
Storage of MXF program components to enable versions & inventories, for use in a multi-version, multi-lingual, multi-delivery media environment.
Enquiries please to info@AMWA.tv
Published
MXF Versioning (was MXF Mastering Format)
MXF optimized for program delivery intended for direct playout via a video server for example. This is based on a PBS profile for MXF program delivery.
Enquiries please to info@AMWA.tv
Published
MXF Program Delivery
Extends AS-01 with color, text & opacity effects.
Project Owner: Phil Tudor, phil.tudor@bbc.co.uk
Published
AAF Effects Protocol
A vendor-neutral subset of the MXF file format to use for long-term archiving and preservation of moving image content and associated materials including audio, captions, multiple legacy timecodes, and other metadata.
Enquiries please to info@AMWA.tv
Published
MXF Archive & Preservation
The AMWA AS-11 family of Specifications define constrained media file formats for the delivery of finished media assets to a broadcaster or publisher. Includes Specifications used by broadcasters in the UK (DPP), Nordic countries, Australia and New Zealand.
Please see specifications below for details of individual implementations.
Project Owner: Phil Tudor, phil.tudor@bbc.co.uk
MXF Media Contribution File Formats
Delivery of finished SD programs to Digital Production Partnership (DPP) broadcasters.
Business Requirements Owner:
Andrew Dunne, Andrew.Dunne@bbc.co.uk
Published & STABLE
MXF Program Contribution – UK DPP SD
Delivery of finished HD programs to Digital Production Partnership (DPP) broadcasters.
Business Requirements Owner:
Andrew Dunne, Andrew.Dunne@bbc.co.uk
Published & STABLE
MXF Program Contribution – UK DPP HD
Delivery of finished UHD programs to Digital Production Partnership (DPP) broadcasters.
Business Requirements Owner:
Phil Tudor, Phil.Tudor@bbc.co.uk
Published
MXF Program Contribution – DPP UHD
Delivery of finished HD AVC Intra programs to a broadcaster or publisher.
Enquiries please to info@AMWA.tv
Published
MXF Program Contribution – HD Intra
Delivery of finished HD AVC Long GOP programs to a broadcaster or publisher.
Enquiries please to info@AMWA.tv
Archived
MXF Program Contribution – HD Long GOP
(25p, 50p)
Delivery of finished HD AVC Long GOP programs to a broadcaster or publisher.
Enquiries please to info@AMWA.tv
Archived
MXF Program Contribution - HD Long GOP (23.98p (24/1.001p), 59.94p (60/1.001p))
Delivery of finished commercials and promos based heavily on AS-11 X1.
Business Requirements Owner:
Bill Brown, bill.brown@itv.com
Work in Progress
MXF Program Contribution - DPP UHD Commercials & Promotions
Delivery of finished commercials and promos based heavily on AS-11 X2.
Business Requirements Owner:
Bill Brown, bill.brown@itv.com
Published
MXF Program Contribution - DPP HD Commercials & Promotions
Delivery of finished SD D10 programs to a broadcaster or publisher.
Enquiries please to info@AMWA.tv
Published
MXF Program Contribution – SD
Delivery of finished HD (MPEG-2) programs to North American Broadcasters Association (NABA) broadcasters.
Business Requirements Owner:
Douglas Pelenberg for NABA, depelenberg@pbs.org
Archived
MXF Program Contribution - NABA DPP HD (MPEG-2)
Delivery of finished HD (AVC) programs to North American Broadcasters Association (NABA) broadcasters.
Business Requirements Owner:
Douglas Pelenberg for NABA, depelenberg@pbs.org
Published
MXF Program Contribution - NABA DPP HD (AVC)
Delivery of finished High Dynamic Range (HDR) UHD and HD TV Programmes (AVC) to North American Broadcasters Association (NABA) broadcasters.
Business Requirements Owner:
Douglas Pelenberg for NABA, depelenberg@pbs.org
Work in Progress
MXF Program Contribution - NABA DPP HDR UHD and HD (AVC)
MXF format optimized for the delivery of finished commercials to broadcast stations. AS-12 adds advertising identification metadata to an advertisement contained in an AMWA MXF Application Specification compliant MXF file.
Enquiries please to info@AMWA.tv
Published
MXF Commercial Delivery
This Best Current Practice (BCP) describes the AMWA’s Specification development process, including how work is initiated, levels of AMWA documents, and types of AMWA Specifications. The goals of the AMWA Specification process are 1) interoperability, 2) satisfying business needs, 3) technical robustness, 4) reusability and composability, and 5) timeliness.
This Best Current Practice (BCP) describes the AMWA's specification development process. This document is, itself, a Best Current Practice.
Project Owner: Brad Gilmer, Brad.Gilmer@AMWA.tv
Published
AMWA Specification Process
How to group related Resources in NMOS specifications
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published
Natural Grouping of NMOS Resources
Documents best practice for using secure transport for NMOS API communications
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published
Secure Communication in NMOS Systems
Documents best practice for an API server to accept or reject requests depending on what a client is authorized to do
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published
Authorization in NMOS Systems
Documents best practice for automated provisioning of TLS Server Certificates to NMOS APIs
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published
Certificate provisioning in NMOS Systems
Allows an IS-04 Receiver to express parametric constraints on the types of streams that it is capable of consuming.
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published
NMOS Receiver Capabilities
Defines how express Extended Display Identification Data (EDID) information as NMOS Receiver Capabilities (BCP-004-01).
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Work in Progress
EDID to NMOS Receiver Capabilities Mapping
Enables Registration, Discovery and Connection Management of JPEG XS Endpoints using the AMWA IS-04 and IS-05 NMOS Specifications.
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Work in Progress
Use of NMOS with JPEG XS
AAF format for intelligence, surveillance and reconnaissance.
Project Owner: AMWA Board of Directors,
Published
AAF for ISR
AAF C++ SDK reference implementation.
Project Owner: Phil Tudor, phil.tudor@bbc.co.uk
Published
AAF toolkit
AAF Java API.
Project Owner: Phil Tudor, phil.tudor@bbc.co.uk
Published
Media Authoring with Java (MAJ) API
Published & STABLE
NMOS Discovery & Registration API
Device Connection Management
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published & STABLE
NMOS Device Connection Management API
NMOS Network Control Specification
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Deprecated
NMOS Network Control
Published
NMOS Event & Tally API
How to set channel mapping/selecting/shuffling settings for use with NMOS APIs.
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published & STABLE
NMOS Audio Channel Mapping
Supports interaction behaviours that allow NMOS Nodes to obtain global configuration parameters that are common across a system.
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published
NMOS System Parameters
Enables an API server to accept or reject requests depending on what a client is authorized to do.
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published
NMOS Authorization
Provides information about Sinks – the logical consumers of media associated with – Receivers, to support configuration of Senders.
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Work in Progress
NMOS Sink Metadata Processing
Mapping from AAF objects to Structured Storage.
Project Owner: Phil Tudor, phil.tudor@bbc.co.uk
Published
A model for identity and timing in AMWA NMOS specifications.
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published
Defines a system for modelling various types of devices which interrelates with existing NMOS Specifications and the JT-NM Reference Architecture.
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Work in Progress
Informative documentS
AMWA Informative Documents (documents with the prefix INFO) are not AMWA Specifications but contain information that is thought to be helpful to the media industry. For example, INFO-004 provides practical information on implementation of DNS-SD in NMOS systems and INFO-005 provides a guide for those implementing NMOS Controllers.
The information they contain is not required in order to successfully create an interoperable implementation of an AMWA Specification. That said, Informative documents are likely to be useful to implementers and end users who are working to create NMOS-based systems by identifying and addressing common questions and expanding on the normative language of the relevant Specifications.
Because Information Documents provide general information that may be helpful, but do not contain any normative provisions which would be required to ensure the implementation and interoperability of an AMWA Specification, the AMWA IPR Policy and procedures do not apply to them.
At the request of the AMWA board, a team of volunteers, including end-users, network equipment providers, processing equipment providers, and related software subsystem developers was charged with the task of adding a layer of detail to the JT-NM reference architecture in the area of control, monitoring and management interfaces.
Project Owner: John Mailhot
Published
Control / Monitoring / Management Architectural Sprint
Guide for implementers who want to add security to their NMOS Nodes and/or NMOS Controllers, according to the IS-10, BCP-003-01, BCP-003-02 and BCP-003-03 specifications.
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published
NMOS Security Implementation Guide
Outlines an architecture for use of Sink Metadata (see IS-11) in ProAV applications including use of EDID (see BCP-005-01).
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Work in Progress
NMOS Sink Metadata Processing Architecture
Explains the use of DNS-SD in NMOS environments, provides a practical “how-to” example of how to set up a BIND9 DNS server for NMOS use and gives example configurations for other DNS servers.
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published
NMOS use of DNS-SD
Is a guide for implementers of Controllers who want to support the NMOS suite of specifications.
It defines the role of an NMOS Controller and describes the requirements of an NMOS Controller with respect to each of the NMOS specifications, together with implementation guidance where appropriate.
Business Requirements Owner:
NMOS Steering group, NMOS-Steering@AMWA.tv
Published
Implementation Guide for NMOS Controllers
Application Specifications
Applications Specifications define a set of rules that constrain a standard—like MXF—to suit a specific application. Each has been created to satisfy the clearly defined operational need of a member company.
-
Program Mastering when there are multiple versions of the content (AS-02)
-
Program Delivery to multiple broadcast stations (AS-03)
-
Archive and Preservation of a wide range of material (AS-07)
-
Workflows suited to fast turnaround end-to-end production (AS-10)
-
Media Contribution for the delivery of finished media assets to a broadcaster or publisher (AS-11)
-
The use of metadata for the management of content, including a unique identifier (AS-12)
Data Model Specifications
The data models lie at the heart of the media workflow technologies.
Interface Specifications
The interface specifications are used to create interoperation between equipment and applications in the media workflow.
Best Current Practices
Best current practices are intended to define and ratify the community's best current thinking on statements of principle or the best ways to perform certain operations or process functions.