Join AMWA - Individual Membership Online Application for AMWA Individual Membership Please complete and submit the online application below for membership to the Advanced Media Workflow Association (AMWA). Membership rights and privileges will commence when AMWA has received full payment of membership fees. ​ Please note that Individual membership is only offered to an individual without any company affiliation in the media industry, an individual in academia as a student, researcher, or in some other way actively associated with an institution of higher learning, or a sole proprietor or the only employee of a corporation. ​ If you prefer, download the membership form (PDF) and send a scanned file to info@AMWA.tv (For future marketing purposes, provide the name of the person and/or company who referred you for membership.) ​ PAYMENT OF FEES Invoice Amount: $185 Payment Method: You will be invoiced on a 30-day billing cycle for membership dues, which may be paid by credit card or check. ​ Acknowledgement * I agree to the payment of fees for AMWA Individual membership. APPLICANT AUTHORIZATION By clicking the "Submit" button below, the applicant acknowledges and agrees that, when accepted by AMWA, this application represents a binding contract between the parties. More specifically, by clicking the "Submit" button, the Applicant: Certifies that it meets the conditions of Membership specified in the By-laws. Commits to (i) payment of annual membership dues and fees as determined from time to time by the Board of Directors and (ii) comply with all the terms and conditions of AMWA Certificate of Incorporation, By-laws, Intellectual Property Rights Policy (the applicant hereby acknowledging its review of these documents which can be found on the Bylaws, Policy Documents & Licenses page) and such other rules and policies as the Board of Directors and/or committees may from time to time adopt. Acknowledges that the AMWA has elected to avail itself of certain protections offered by the National Cooperative Research and Production Act of 1993, as amended, which requires disclosure of the names of all members of AMWA, and hereby appoints such person who shall be the Executive Director or acting Executive Director of AMWA as the undersigned's true and lawful attorney-in-fact and authorizes him or her to: ​ Notify government agencies of the undersigned's membership in AMWA, make, approve the form of, execute and deliver filings with government agencies on behalf of AMWA and on behalf of the undersigned as a member of AMWA, receive notifications, including without limitation, notifications pursuant to the National Cooperative Research and Production Act on behalf of AMWA and on behalf of the undersigned as a member of AMWA, and authorize and direct other officers of, and/or counsel to AMWA, to do any of the foregoing acts. * I have read and accept the applicant authorization terms Submit Your Application

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 AS-01 Edit metadata interchange using AAF. Includes base set of effects. Project Owner: Phil Tudor, phil.tudor@bbc.co.uk Published & STABLE AAF Edit Protocol AS-02 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) AS-03 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 AS-05 Extends AS-01 with color, text & opacity effects. Project Owner: Phil Tudor, phil.tudor@bbc.co.uk Published AAF Effects Protocol AS-07 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 AS-10 MXF for end-to-end production workflow. Enquiries please to info@AMWA.tv Published MXF for Production AS-11 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 AS-11 UK DPP SD Delivery of finished SD programs to Digital Production Partnership (DPP) broadcasters. FURTHER INFORMATION Business Requirements Owner: Andrew Dunne, Andrew.Dunne@bbc.co.uk Published & STABLE MXF Program Contribution – UK DPP SD AS-11 UK DPP HD Delivery of finished HD programs to Digital Production Partnership (DPP) broadcasters. FURTHER INFORMATION Business Requirements Owner: Andrew Dunne, Andrew.Dunne@bbc.co.uk Published & STABLE MXF Program Contribution – UK DPP HD AS-11 X1 Delivery of finished UHD programs to Digital Production Partnership (DPP) broadcasters. FURTHER INFORMATION Business Requirements Owner: Phil Tudor, Phil.Tudor@bbc.co.uk Published MXF Program Contribution – DPP UHD AS-11 X2 Delivery of finished HD AVC Intra programs to a broadcaster or publisher. FURTHER INFORMATION Enquiries please to info@AMWA.tv Published MXF Program Contribution – HD Intra AS-11 X3 Delivery of finished HD AVC Long GOP programs to a broadcaster or publisher. FURTHER INFORMATION Enquiries please to info@AMWA.tv Archived MXF Program Contribution – HD Long GOP (25p, 50p) AS-11 X4 Delivery of finished HD AVC Long GOP programs to a broadcaster or publisher. FURTHER INFORMATION Enquiries please to info@AMWA.tv Archived MXF Program Contribution - HD Long GOP (23.98p (24/1.001p), 59.94p (60/1.001p)) AS-11 X5 Delivery of finished commercials and promos based heavily on AS-11 X1. FURTHER INFORMATION Business Requirements Owner: Bill Brown, bill.brown@itv.com Work in Progress MXF Program Contribution - DPP UHD Commercials & Promotions AS-11 X6 Delivery of finished commercials and promos based heavily on AS-11 X2. FURTHER INFORMATION Business Requirements Owner: Bill Brown, bill.brown@itv.com Published MXF Program Contribution - DPP HD Commercials & Promotions AS-11 X7 Delivery of finished SD D10 programs to a broadcaster or publisher. FURTHER INFORMATION Enquiries please to info@AMWA.tv Published MXF Program Contribution – SD AS-11 X8 Delivery of finished HD (MPEG-2) programs to North American Broadcasters Association (NABA) broadcasters. FURTHER INFORMATION Business Requirements Owner: Douglas Pelenberg for NABA, depelenberg@pbs.org Archived MXF Program Contribution - NABA DPP HD (MPEG-2) AS-11 X9 Delivery of finished HD (AVC) programs to North American Broadcasters Association (NABA) broadcasters. FURTHER INFORMATION Business Requirements Owner: Douglas Pelenberg for NABA, depelenberg@pbs.org Published MXF Program Contribution - NABA DPP HD (AVC) AS-11 X10 Delivery of finished High Dynamic Range (HDR) UHD and HD TV Programmes (AVC) to North American Broadcasters Association (NABA) broadcasters. FURTHER INFORMATION Business Requirements Owner: Douglas Pelenberg for NABA, depelenberg@pbs.org Work in Progress MXF Program Contribution - NABA DPP HDR UHD and HD (AVC) AS-12 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 MXF AS-02 AS-11 BCP-Specs BCP-001-03 This Best Current Practice (BCP) describes the AMWA’s Working Group and Specification development process, including how Working Groups are formed, how work is initiated, levels and types of AMWA documents. The goals of the AMWA Specification process are 1) interoperability, 2) satisfying business needs, 3) technical robustness, 4) reusability and composability, and 5) timeliness. Project Owner: Brad Gilmer, Brad.Gilmer@AMWA.tv Published AMWA Specification Process BCP-002-01 How to group related Resources in NMOS specifications Business Requirements Owner: NMOS Steering group, NMOS-Steering@AMWA.tv Published Natural Grouping of NMOS Resources BCP-002-02 Defines how to provide human-readable distinguishing information for NMOS Nodes and Devices Business Requirements Owner: NMOS Steering group, NMOS-Steering@AMWA.tv Published NMOS Asset Distinguishing Information BCP-003-01 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 BCP-003-02 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 BCP-003-03 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 BCP-004-01 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 BCP-005-01 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 BCP-006-01 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 Published Use of NMOS with JPEG XS DOT-ISR AAF format for intelligence, surveillance and reconnaissance. Project Owner: AMWA Board of Directors, Enquiries please to info@AMWA.tv Published AAF for ISR IS-Specs IS-01 AAF C++ SDK reference implementation. Project Owner: Phil Tudor, phil.tudor@bbc.co.uk Published AAF toolkit IS-03 AAF Java API. Project Owner: Phil Tudor, phil.tudor@bbc.co.uk Published Media Authoring with Java (MAJ) API IS-04 Discovery and Registration Business Requirements Owner: NMOS Steering group, NMOS-Steering@AMWA.tv Published & STABLE NMOS Discovery & Registration API IS-05 Device Connection Management Business Requirements Owner: NMOS Steering group, NMOS-Steering@AMWA.tv Published & STABLE NMOS Device Connection Management API IS-06 NMOS Network Control Specification Business Requirements Owner: NMOS Steering group, NMOS-Steering@AMWA.tv Deprecated NMOS Network Control IS-07 Event & Tally Business Requirements Owner: NMOS Steering group, NMOS-Steering@AMWA.tv Published NMOS Event & Tally API IS-08 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 IS-09 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 IS-10 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 IS-11 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 IS-12 Sets out the rules and requirements for implementing the NMOS Device Control protocol in devices and controllers. Business Requirements Owner: NMOS Steering group, NMOS-Steering@AMWA.tv Work in Progress NMOS Control Protocol IS-13 Allows control and monitoring applications to update resource labels, descriptions and tags. Business Requirements Owner: NMOS Steering group, NMOS-Steering@AMWA.tv Work in Progress NMOS Annotation API DM-Specs MS-01 AAF Data Model. Project Owner: Phil Tudor, phil.tudor@bbc.co.uk Published MS-02 Mapping from AAF objects to Structured Storage. Project Owner: Phil Tudor, phil.tudor@bbc.co.uk Published MS-03 Structured Storage Specification. Project Owner: Phil Tudor, phil.tudor@bbc.co.uk Published MS-04 A model for identity and timing in AMWA NMOS specifications. Business Requirements Owner: NMOS Steering group, NMOS-Steering@AMWA.tv Published MS-05-01 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. Info-Docs INFO-001 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 john.mailhot@imaginecommunications.com Published Control / Monitoring / Management Architectural Sprint INFO-002 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 INFO-003 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 INFO-004 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 INFO-005 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) View Application Specifications Data Model Specifications The data models lie at the heart of the media workflow technologies. View Data Model Specifications Interface Specifications The interface specifications are used to create interoperation between equipment and applications in the media workflow. View Interface Specifications 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. View Best Current Practices

AS-11 AS-11 UK DPP HD: MXF Program Contribution – UK DPP HD ​ This is a Specification in the AS-11 family of Specifications . It defines an MXF file format for the delivery of finished HD programs to UK Digital Production Partnership (DPP) broadcasters. ​ See the specification - Full Specification on GitHub ​​ AS-11 DPP Certification: Certification Authority – AS-11 DPP AS-11 DPP Certificates This rules based Specification supersedes the original defined in a PDF document, with no material differences. ​

Bylaws, Policy Documents & Licenses AMWA Constitution Bylaws AMWA By-Laws (PDF, 294k) Articles of Incorporation (PDF, 13k) Certificate of Amendment (PDF, 61k) ​ ​ ASSOCIATION Policy Documents These documents contain policies of the AMWA Association: Board Participation Policy (PDF, 20k) Conflict of Interest Policy (PDF, 9k) Document Succession and Referencing Policy (PDF, 96k) Dues Payment Policy - as of 12/08/2021 (PDF, 384k) Member Press Releases Policy (PDF, 30k) Non-member Meeting Policy (PDF, 105k) Private Metadata Policy (PDF, 32k) AMWA Software Contribution Rules (PDF, 25k) AMWA Specification Process (PDF, 641k) Project Work Proposal Template (PDF, 27k) Trademark Usage Policy (PDF, 150k) Product Certification Policy (PDF, 147k) Universal Label Policy (PDF, 413k) Insensitive and Offensive Terminology Policy (PDF, 49k) ​ ​ Intellectual Property Rights AAF SDK PUBLIC SOURCE LICENSE AGREEMENT Version 2.0 PDF, 63k) Intellectual Property Policy 3.0 (pdf, 305k) Intellectual Property Rights Fact Sheet 3.0 (PDF, 104k) Meeting Invocation 2.0 (PDF, 27k) AMWA Meeting Sign-In Sheet (PDF, 8k) AMWA Policy on participants in project work groups (PDF, 21k) ​ ​ ASSOCIATION Licenses These documents contain licenses related to the AMWA Association: Advanced Authoring Format Implementer's Agreement 2.0 (PDF, 52k) Microsoft Structured Storage License (PDF, 116k) SchemaSoft-AAFA SSL License Available to AMWA members only. Please contact us at info@AMWA.tv to arrange for copy. SchemaSoft Object Code Redistribution Terms (PDF, 46k) Independent Contractor Agreement for SchemaSoft (DOC, 40k) ​ ​ BLANK TEMPLATES FOR PROCESS DOCUMENTS AMWA Project Proposal Template (DOC, 117k) AMWA NMOS Rules Document (PDF, 166k) ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ByLaws PolicyDocs Licenses Templates

Join AMWA - Associate Membership Online Application for AMWA Associate Membership Please complete and submit the online application below for membership to the Advanced Media Workflow Association (AMWA). Membership rights and privileges will commence when AMWA has received full payment of membership fees. ​ If you prefer, download the membership form (PDF) and send a scanned file to info@AMWA.tv *Preferred Invoice Billing Cycle ​ Payment of Fees Invoice Amount: $2,400 Payment Method: You will be invoiced for membership dues. ​ Acknowledgement * I agree to the payment of fees for AMWA Associate membership. (For future marketing purposes, provide the name of the person and/or company who referred you for membership.) ​ ​ Applicant Authorization By clicking the "Submit" button below, the applicant acknowledges and agrees that, when accepted by AMWA, this application represents a binding contract between the parties. More specifically, by clicking the "Submit" button, the Applicant: Certifies that it meets the conditions of Membership specified in the By-laws. Commits to (i) payment of annual membership dues and fees as determined from time to time by the Board of Directors and (ii) comply with all the terms and conditions of AMWA Certificate of Incorporation, By-laws, Intellectual Property Rights Policy(the applicant hereby acknowledging its review of these documents which can be found on the Bylaws, Policy Documents & Licenses page) and such other rules and policies as the Board of Directors and/or committees may from time to time adopt. Acknowledges that the AMWA has elected to avail itself of certain protections offered by the National Cooperative Research and Production Act of 1993, as amended, which requires disclosure of the names of all members of AMWA, and hereby appoints such person who shall be the Executive Director or acting Executive Director of AMWA as the undersigned's true and lawful attorney-in-fact and authorizes him or her to: ​ Notify government agencies of the undersigned's membership in AMWA, make, approve the form of, execute and deliver filings with government agencies on behalf of AMWA and on behalf of the undersigned as a member of AMWA, receive notifications, including without limitation, notifications pursuant to the National Cooperative Research and Production Act on behalf of AMWA and on behalf of the undersigned as a member of AMWA, and authorize and direct other officers of, and/or counsel to AMWA, to do any of the foregoing acts. * I have read and accept the applicant authorization terms Submit t Your Application

AS-11 AS-11 X10: MXF Program Contribution - NABA (HDR) UHD and HD (AVC) ​ This is a Specification in the AS-11 family of Specifications . Delivery of finished High Dynamic Range (HDR) UHD and HD TV Programmes (AVC) to North American Broadcasters Association (NABA) broadcasters. ​ See the specification - Full Specification on GitHub At present, there is no Certification program set up for this specification.

Join AMWA Business Benefits The AMWA provides an environment which lowers the financial risk of technology decisions and helps to get the maximum return on investment by enabling cost effective, well integrated systems. For media companies, all projects have clearly defined business benefits and exist to improve efficiencies in both technical resources and manpower. Close collaboration between media companies and their suppliers increases understanding and helps align the supply of products and services to end users’ operational needs. For suppliers, participation in AMWA projects can lower the perceived risk for customers when choosing products and investing substantial sums in new technology. ​ Technology Technology Benefits AMWA is the only media-industry association that focuses on enabling smoother, more efficient, workflows and system implementations. Interoperability and standardized interconnections support the design of best of breed systems. AMWA online forums provide a place for open technical discussions and consensus between a wide range of end users and suppliers. Workshops provide a safe environment to work with other organisations in software development. What we do ​ ​ Membership MEMBERSHIP BENEFITS All AMWA member dues are annual and renew on the anniversary month of membership commencement. Membership and participation in projects are open to all full time staff of a member company but not contractors. ​ Principal Members Principal members set the strategy and direction of the AMWA, and are the only level of membership eligible to serve on the Board of Directors. The AMWA Board sets the direction of the Association, including the budget and resource allocation, and approves project proposals. Principal members are entitled to all membership benefits. The AMWA posts Principal member logos on its web site and include links to specific pages on the member’s web sites. Principal member dues are $10,300 annually. Join Now ​ General Members General members share most of the Principal member entitlements except for serving on the Board of Directors. They have access to all projects and can initiate new work (which is subject to Board approval). The AMWA will post General member logos on the AMWA web site, with links to company web sites. General member dues are $5,200 annually. Join Now ​ Associate Members Associate members can join working groups creating the specifications on the NMOS project only. They can also attend the regular developer workshops and AMWA pre-show qualification events, where appropriate. They are not able to propose new projects. The AMWA will post Associate member logos on the AMWA web site. Associate member dues are $2,400 annually. Join Now ​ Individual Members Individual members have the same entitlements as Associate members but Individual membership is only offered to 1) an individual without any company affiliation in the media industry, 2) an individual in academia as a student, researcher, or in some other way actively associated with an institution of higher learning, or 3) a sole proprietor or the only employee of a corporation. Dues for Individual members are $185 annually. Join Now ​ All membership levels can access specifications before they are publicly available and have access to AMWA Reference Implementations. Benefits of Membership Principal General Associate Individual1 Eligible to participate in a Project Group One complimentary certification per year ($1,750 value) Eligible to participate in a Project Group Submit unlimited project proposals to AMWA Board of Directors Submit one project proposal per year to the AMWA Board of Directors Propose extensions/additions to existing and new specifications Access to AMWA Application reference implementations and sample files Access to AMWA community (AMWA Forum) Access to AMWA community (AMWA Forum) Attend AMWA educational events Member company logos posted to AMWA website with links to company pages Manufacturers can list AMWA-compliant products on AMWA web site Annual Membership fee Member company logos posted to AMWA website with links to company pages Annual Membership Fee US $10,300 US $5,200 US $2,400 US $185 1 JOIN AMWA NOW Apply online Principal General Associate Individual 1 - Individual memberships are limited to single parties with no employment affiliation to a media industry company except in the case of a sole proprietor. 2 - With approval of the AMWA Executive Director. 3 - Committee participation without voting privileges. ** - With sponsorship from a Principal or General Member. Download the Comparison Chart

AS-11 AS-11 X1: MXF Program Contribution - DPP UHD ​ This is a Specification in the AS-11 family of Specifications . It defines an MXF file format for the delivery of finished UHD programs to UK Digital Production Partnership (DPP) broadcasters. ​ See the specification - Full Specification on GitHub ​​ At present, there is no Certification program set up for this specification.

AS-11 AS-11 X3: MXF Program Contribution – HD Long GOP (25p, 50p) ​ This is a Specification in the AS-11 family of Specifications . It defines an MXF file format for the delivery of finished HD programs. ​ See the specification - Full Specification on GitHub ​ ​ At present, there is no Certification program set up for this specification. ​

Videos NMOS - Networked Media Open Specifications Fundamentals ​ An Introduction to the AMWA Networked Media Incubator project 4:47 Brad Gilmer, AMWA 1. Introduction to Networked Media Open Specifications 9:08 Andrew Bonney and Alex Rawcliffe, BBC R&D An introduction to the current specifications in progress, their data model and key concepts. 2. NMOS: Discovery and Registration 8:39 Andrew Bonney and Alex Rawcliffe, BBC R&D A robust and scalable approach to Discovery is essential element of real-world management networked media. This presentation describes how to use NMOS's Node, Registration and Query APIs for discovery, from small peer-to-peer cases to large installations. 3. NMOS: Connection Mangement 2:52 Andrew Bonney and Alex Rawcliffe, BBC R&D NMOS allows Senders and Receivers to be connected in a transport-agnostic way. Andrew and Alex describe how to do this using the Node API. 4. NMOS: In-stream Identity and Timing 4:18 Andrew Bonney and Alex Rawcliffe, BBC R&D NMOS provides a universal identity model for content and an end-to-end timing model, both important elements of a future-proof networked media architecture. This presentation explains these contents, and how they are mapped to media streams. Demonstration of NMOS Registration and Discovery 3:40 Alex Rawcliffe, BBC R&D An example of NMOS Registration and Discovery in action using software and hardware from multiple manufacturers. ​ Public presentations IBC 2019, IP Showcase, curated by the Video Services Forum ​ NMOS Now and Next 28:43 Peter Brightwell, BBC R&D An introduction to the AMWA Networked Media Open Specifications, including an outline of the specifications themselves, how they have been developed and tested, the state of industry adoption, and broadcaster perspectives. ​ AMWA NMOS Automated Testing 30:41 Andrew Bonney, BBC R&D and Gareth Sylvester-Bradley, Sony Europe An introduction to the open source AMWA NMOS Testing Tool, which can be used to automatically ensure that Media Nodes and other appliances are adhering to the NMOS specifications. ​ NMOS IS-07 – GPI Replacement and Much, Much More 23:58 Miroslav Jeras, Pebble Beach Systems IS-07 Event & Tally is part of the NMOS suite that defines how states and state changes are communicated in an IP environment. It is not only a GPI replacement but it also provides a platform for resolving many other problems broadcasters are facing in the IP transition. ​ Security for Discovery and Connection management of ST 2110 Media Devices 25:30 Arne Bönninghoff, Riedel Communications This session describes the current workflow of the BCP-003 Security best practices, including proposed mechanisms to encrypt NMOS APIs with TLS to prevent man in the middle attacks. Furthermore, AMWA IS-10 is reserved to specify authorization mechanisms to secure access to NMOS APIs like IS-04, -05, or -08. ​ Using AMWA IS-06 for Flow Control on Professional Media Networks 26:15 Rob Porter, Sony Europe and Sachin Vishwarupe, Cisco Systems AMWA IS-06 is an open specification for setting up and modifying flows on a professional media network, allowing the use of Software Defined Networking to both authorise and optimise network usage. This presentation describes the current IS-06 APIs and some of the future areas of development. ​ NAB 2019, IP Showcase, curated by the Video Services Forum ​ AMWA NMOS: The Whole Story 31:25 Brad Gilmer, AMWA and Peter Brightwell, BBC R&D This talk serves as an introduction to AMWA NMOS, covering all parts of this suite of interface specifications and best practices. It also touches on why we’re creating it, the approach we’re taking, and how it’s being implemented. The AMWA IS-04 and IS-05 interfaces are now recognized as being essential to the industry’s move to interoperable live IP infrastructure. They allow control applications to automatically discover and connect networked media devices and are now mature specifications featured in many products. ​ A MWA NMOS IS 04 and IS 05: Things You Might Not Know 29:31 Andrew Bonney Did you know for example, that there is no requirement for every node in a system to run the same IS-04 version? This presentation will take a look at some of the lesser-known and more advanced features of IS-04 and IS-05, along with how they may assist you in deploying anything from a small ad-hoc setup through to a large-scale multi-format facility. ​ AMWA BCP 003 NMOS API Security 17:03 Simon Rankine, BBC R&D BBC Research and Development’s Simon Rankine presents an update from AMWA’s NMOS API Interoperable Security Group which is working to apply tried and tested web technologies to the APIs in order to provide APIs that are simultaneously secure and cross-vendor interoperable. ​ NAB 2019, AMWA Booth ​ Cisco IP fabric for Media 16:28 Rahul Parameswaran, Cisco ​ SMPTE Annual Technical Conference 2018 Scalability and Performance of the AMWA NMOS IS-04 and IS-05 Specifications 27:53 Rob Porter and Gareth Sylvester-Bradley, Sony Europe A key requirement is that APIs such as those used for AMWA IS-04 and IS-05 scale successfully in the very large installations, typical of real world deployments. To help address this, Sony has been leading an AMWA NMOS Scalability study to test these protocols for installations comprising thousands of media devices. ​ SMPTE Webinar, May 2018 ​ Exploring the Role of NMOS: Discovery and Connection in an IP World 1:32:52 Peter Brightwell SMPTE ST 2110 specifies how to stream video, audio, and data between devices for professional applications using IP networks. How best to discover, connect, and monitor those devices? That is addressed by the Advanced Media Workflow Association (AMWA) Networked Media Open Specifications (NMOS). This SMPTE Technology Webcast will focus on how different parts of the AMWA NMOS work, in theory as well as in practice, and on how NMOS can be used in a range of applications, whether within a broadcast control room or a cloud-based workflow. ​ Agile Media Workflows ​ Introducing the AMWA Agile Media Blueprint 25:33 Richard Cartwright, Streampunk Media Introducing the Agile Media Blueprint (AMB), a plan for how to use the same technology platform as used for the Internet to make television, OTT media systems and to enable new kinds of creativity. A Demonstration of ZeNMOS and SDPoker 10:31 Richard Cartwright, Streampunk Media A brief demonstration of open-source testing tools ZeNMOS and SDPoker, designed to help users and suppliers to test products that support the latest IP Standards (SMTPE ST 2110) and Specifications (AMWA NMOS IS-04). ​ MXF - Media Exchange Format AS-10: MXF for Production - Acquisition to Air & Archive 8:08 Dan Shockley, CNN A presentation by Dan Shockley from NAB 2012 on the AMWA specification 'MXF for Production', AS-10 Webinar: AMWA AS-11: Introducing the New Rules-Based Specifications 38:16 Thomas Heritage, BBC and Kevin Burrows, Channel 4 The AMWA AS-11 family of Specifications define constrained media file formats for the delivery of finished media assets to a broadcaster or publisher. The business case for AS 11, MXF for Contribution. pt 1 of 2 13:11 Ian Wimsett, Red Bee Media Part 1 of a presentation given by Ian Wimsett at NAB 2012. The AMWA application specification was designed to meet the needs of publisher broadcasters who may need to process content, for example segmentation, before it is ready for air. The Business Case for AS-11: MXF for Contribution, pt 2 of 2 7:51 Ian Wimsett, Red Bee Media A presentation by Ian Wimsett given at NAB 2012 What AS-11 DPP Product Certification Means for Your Business 23:33 IBC Panel Discussion

AS-11 AS-11 X5: MXF Program Contribution - DPP UHD Commercials & Promotions ​ This is a Specification in the AS-11 family of Specifications . It defines an MXF file format for the delivery of finished UHD Commercials & Promotions to UK Digital Production Partnership (DPP) broadcasters. ​ See the specification - Full Specification on GitHub ​​ At present, there is no Certification program set up for this specification.

NMOS View the NMOS At A Glance page For a Business Overview (Read Below) For a Technical Overview (start here) To see the Specifications (start here) For the NMOS Wiki (Start Here) BusinessOverview This page provides a non-technical overview of the AMWA’s work to create Networked Media Open Specifications. The information has been provided in the form of Frequently Asked Questions. If you have any further questions, don’t hesitate to Contact Us . ​ Technical information which has been published, is available at https://amwa-tv.github.io/nmos/ ​ What are Networked Media Open Specifications? Who is supporting this initiative? What is the technical basis for the NMOS project? What is the Networked Media Incubator? What are IS-04, IS-05, IS-06, etc? Where can I find technical details of the specifications? How can my company participate? Is there an NMOS compliance / certification process? When will NMOS specifications become standards? ​ What are Networked Media Open Specifications? The Networked Media Open Specifications (NMOS) have been developed for use in IP-based infrastructures to provide a control and management layer in addition to the transport layer provided by SMPTE ST2110. The goal is to provide a means for straightforward interoperability between products from a wide range of manufacturers, in order that end users and service providers can build best-of-breed systems. ​ As in the past, successful sales by a supplier will depend on matching their customer’s needs for functionality. NMOS simply seeks to make the interconnection of products from competing suppliers as simple as possible. ​ The NMOS family of specifications began with projects for Discovery & Registration, Device Connection Management and Network Control. It has grown to include important subjects such as Event & Tally, Audio Channel Mapping and Interoperable Security. Additional working groups become active as new operational / business needs are identified. ​ They are a growing family of specifications which are available to both suppliers and end users, at no cost, to support the development of products and services which work within an open industry framework. Wherever possible, the specifications are being developed using Internet standards or Internet-friendly techniques. Back to the top Who is supporting this initiative?​ The NMOS initiative is supported by the Joint Task Force on Networked Media (JT-NM), comprised of four organisations; the AMWA, EBU, SMPTE and VSF. http://www.jt-nm.org/ The work of the AMWA complements and, in turn, supports the contributions from the other organisations. ​ More than 70 AMWA members, end users and their suppliers, have signed up as participants in this project and are active in the working groups that most directly affect their business. The list ranges from large, multinational suppliers to single person consultancies. The list of end users and suppliers . The JT-NM works closely with the Alliance for IP Media Solutions (AIMS) to provide education and advocacy across our industry. Back to the top What is the technical basis for the NMOS project? In 2015, the JT-NM published a Reference Architecture which describes a conceptual model for interoperability. It is designed for contribution that will allow end users and manufacturers to truly benefit from the cost saving, flexibility and scalability of an Internet-based approach. ​ However, the Joint Task Force did not go as far as working on specifications or encouraging implementations. Instead, they laid out the Reference Architecture and a collection of best practices, leaving it to initiatives such as NMOS and the AMWA Networked Media Incubator project to work out the details and to get implementers together to create interoperable solutions. Back to the top ​ What is the Networked Media Incubator? This is a key project set up to enable the creation of a family of Open Specifications. ​ The Networked Media Incubator project is sponsored by the AMWA to enable open, multi-vendor interoperability in professional media networks. The activity is focused on getting early tangible results by concentrating on specific technical areas through a series of collaborative development activities and facilitating virtual and physical interchanges between system developers. The technical goals of the group are guided by the JT-NM’s Reference Architecture. ​ The Networked Media Incubator (also simply called the "Incubator”) was set up in September 2015 as an “umbrella” project, under which the working groups could operate. The number of working groups has grown steadily and most hold weekly or fortnightly conference calls in addition to technical discussions on the Basecamp project forum. ​ Regular developer workshops take place throughout the year. These are open to any AMWA member which has software to test. The workshops provide a supportive environment where developers share experiences to the mutual benefit of all participants. To encourage openness and discussion, there is strict rule not to speak negatively about any other participant who takes part in a workshop. Back to the top ​ ​ What are IS-04, IS-05, IS-06, etc? These are Interface Specification (IS) identifiers assigned to the NMOS specs. Specifications are formally given an IS number once they reach Specification status. Other supporting specifications may have different numbering, such as "BCP", for Best Current Practice. Details of all specifications can be found by the link at the top of this page. NMOS APIs are built on widely adopted patterns used on the Internet/Web, using open-source components wherever available. Back to the top Where can I find technical details of the specifications? An overview can be found at https://amwa-tv.github.io/nmos/ with more detailed documentation starting at https://github.com/AMWA-TV/ . ​ NMOS specifications are made publicly available (Apache 2 licence) as early as is practical, and at the latest on elevation to AMWA Specification. Note that some specifications are in private repos in their early stages. These are accessible to AMWA NMOS participants (if you are a member who needs access, please contact the Incubator or activity lead). ​ As well as proprietary implementations, several open-source implementations of IS-04 and IS-05 are available. These are available via the first link above. At the time of writing, they all use the Apache 2.0 license, which matches the NMOS specifications themselves. If you have an implementation you would like added, please create an issue against this repository indicating where it is available from. Back to the top ​ ​ How can my company participate? Any company can join this work by becoming a member of the AMWA and signing the Rules document **. Membership provides access to all current NMOS projects and a shared IPR framework through the AMWA’s IPR policy. ​ There are three company membership levels plus an individual membership. Details of the range of membership benefits are available via the JOIN button at the top of this page. If you have questions of any sort, please use the CONTACT button above. Please note that the NMOS Incubator project is "RAND-Z" so it requires any contributions to be made available on a reasonable and non-discriminatory basis at zero cost. ​ ** The Rules document exists simply to support open, honest communication and ensure that no participant speaks negatively about a competitor following discussions and / or developer workshops. Back to the top Is there an NMOS compliance / certification process? At present, there are interoperability checklists at workshops and in preparation for public demonstrations but these are for use for testing by suppliers and do not let vendors formally claim compliance. ​ The AMWA does not currently provide a certification process for NMOS implementations. Back to the top When will NMOS specifications become standards? Development of an Interface Specification reaches a point where it is sufficiently advanced to be formally elevated to an “AMWA Specification”. ​ However, further versions of NMOS specifications are likely, for example, to support the additional requirements of newer, later specifications. Also, as the professional networked media industry matures we can expect end user requirements to evolve so, although individual versions will become “Stable” and widely implemented, NMOS will not stand still. ​ This need to accommodate evolving end user requirements does not allow as easy fit with the traditional standards processes which have worked so well for transport streams such as SMPTE ST2110. Back to the top ​ ​ ​ NMOSfaq1 NMOSfaq2 NMOSfaq3 NMOSfaq4 NMOSfaq5 NMOSfaq6 NMOSfaq7 NMOSfaq8 NMOSfaq9

White Papers & Reference Documents NETWORKED MEDIA OPEN SPECIFICATIONS (NMOS) Networked Media Systems - The Big Picture (528kb) Pebble - Navigating from SDI to IP (11.8Mb) ​ AGILE MEDIA Live Cloud Requirements (pdf) Agile Media Blueprint (AMB) Discussion Document (pdf, 1.58Mb) ​ MATERIAL EXCHANGE FORMAT (MXF) A Quick Tour of Wrappers and MXF (pdf, 651k) The AMWA Family of Application Specifications for MXF (pdf, 298k) AAF to Application Specifications: How They Fit An Advanced Media Workflow (pdf, 123k) Quick Introduction to MXF AS02 and AS03 (pdf, 944k) Business Drivers for AS02 and AS03 (pdf, 691k) MXF: Joined-Up Workflows & Business Efficiencies (pdf, 414k) Accelerating Standards Development (pdf, 269k) Avid Viewpoint: The Promise of AS-02 (pdf, 223k) MXF for Program Contribution, AS-11 (pdf, 533k) The Life of a Commercial, AS-12 provides solutions to the problems that arise in existing workflows (pdf, 372k) Are Fully Digital Workflows A Pipe Dream? (pdf, 295k) Smooth Asset Workflows, Bigfoot, and UFOs (pdf, 888k) The pipe dream becomes real: Advertising workflows have come of age (pdf, 523k) Encoding Data into MXF files: BER and KLV encoding (pdf, 669k) The Structure of an MXF file: The Physical view (pdf, 669k) ​ ADVANCED AUTHORING FORMAT (AAF) "AAF" - EBU Technical Review (pdf, 270k) Enabling Better Media Workflows: An Overview of the Advanced Authoring Format (pdf, 530k) ​ ​

Dodo Reference Manual ​ Dodo .DOD source files are simply a set of macros ​ These macros are expanded differently depending on the macro file used, so the same DOD file can produce both a COM API header and a COM wrapper for the related Impl function with a similar name. ​ Return to Developers In some Macro files a lot of the macros are simply null. Macro Arguments The arguments passed to Macros can be several lines long (especially in the case of comments). Occurrences of ( ) parentheses and , commas in the arguments passed to macro have to be escaped with a backslash. Some macros such as AD_METHOD1 are nested because AD_METHOD1 with 6 arguments invokes AD_XMETHOD1 with an extra argument in the base.mac file, as a result of this, escaped characters in AD_METHOD1 have to be escaped twice, an open parentheses in a comment has to be preceded by three back slashes \\\( . A \ (backslash) character immediately before a newline, indicates a continuation line escaped so that it will not appear in the output. Usage: dodo -f macro_file ​ Expects input .dod file on standard input, writes the expanded output to standard out. The macro files also include the base.mac file which contains common definitions. Some of the macro files are only used once to generate an initial framework for an implementation file, for instance once you have a constructed a .dod file for your interface you can generate a empty implementation with the command: dodo -m macros/cpp.mac < AAFMyInterface.dod Comments ​ The comments for methods and interfaces follow a pretty repetitive format, since they are extracted from the IDL file by the DocJet tool to generate the COMAPI manual it is best to follow the existing style of indentation and line breaks. The macros subdirectory contains the following different variants: All Dodo directives in the macro file start at the beginning of a line, and start with the '#' character. Macro Arguments The arguments passed to a macro are substituted in the body with the notation %n, where n is a digit starting at 1 for the first argument. Comments Dodo comment lines begin with #c Directives the #import directive will include another macro file Macro definitions are delimited with #startm ... #endm Whenever the macro_name() is encountered in the source file, it will be replaced with the multi-line macro expansion in the output file. Special Macros conventionally defined at the top of each dod file .this-module expanded to the class or interface name such as C.this-module and Impl.this-module ​ .parent-module the parent class for public inheritance at the implementation level, used to aggregate the interfaces at the COM API level by importing the methods of the parent. Special Rules Any arguments specified within a macro expansion specification using the %n syntax must have numbers that are 1 or greater, and are less than or equal to the num_args value for that macro. Any macro invocation in the input file must be given precisely the number of arguments given in the num_args field of the macro's definition. ​ ​ ​

Rebuilding Derived headers on Windows ​ This page describes the procedure for running dodo on Windows using the Cygwin GNU tools. It is also possible to build dodo with Visual Studio and the commercial MKS tools running AAF/dodo/makefile rather than AAF/dodo/GNUmakefile. Required tools (all part of cygwin ): Gnu Make C++ compiler Perl Bash Shell0 ​ If you add an extra interface file, you need to follow this procedure: if you don't already have it, checkout the dodoWin module from CVS, this should give you the dodo directory and the extra make files required. create your AAFmyInterface.dod macro file by editing a similar example generate a new UUID for your COM interface add your Implementation and Unit Test for your interface (you can use dodo to manually generate the basic files) add the AAFmyInterface to dodo/aafobjects.mk run GNUmakefile in the dodo directory by simply typing 'make' add the AAFmyInterface.dod macro file to CVS run the midl compiler ?? add the new derived files to CVS ref-impl/src/com-api/: CAAFmyInterface.cpp CAAFmyInterface.h Rebuild the Mac and Win SDKs to copy ref-api headers to their sub-directories (Win build MakeSDK target, Mac run MakeSDK MPW script) CVS checkin all the affected derived files such as ref-impl/include/com-api AAF.idl, AAF.h, AAF_i.c The following table shows the steps that the main Dodo makefile goes through to update the Derived files: Return to Developers GNUmakefile ​ ../build/common.mk determines platform/environment ../build/Pdefs-Win.mk used by common.mk after checking OS type tool/GNUmakefile builds the DODO executable Runs PERL script sync_copyright.pl to update the copyright text in macros/base.mac ​ dodotargets.mak creates a list of DODO targets using aafobjects.mk as the input file and running GenTargets.sh on this to create targets.mk NOTE: new Target *.dod files must be added manually to aafobjects.mk dododepend.mak creates DODO dependency information in its output file depend.mk , using aafobjects.mk as input and running in sequence GenDepend.sh and then GenDepend2.sh on this file. depend.mk included in maketargets.mak to provide the dependencies for the targets. maketargets_gnu.mak where the bulk of the work is done (builds all the targets). Creates all *.idl files using shell scripts: GenAafPrivateIdl.sh GenAafIdl.sh GenPluginIdl.sh Creates various headers (*.h) using shell scripts: GenAafPrivateh.sh GenAafh.sh GenPluginh.sh Creates various *_i.refh files using shell scripts: GenAafPrivate_i.sh GenAaf_i.sh GenPlugin_i.sh Creates AAFClassIds.impl file with GenClassIds.sh Creates AAFClassIds.comh file with GenClassIds.sh Creates AAFObjectTable.comh file with GenObjectTable.sh Creates AAFObjectTable_i.refh file with GenObjectTable_i.sh Creates CAAF*.h and CAAF*.cpp files for each corresponding input *.dod file Uses the Microsoft IDL compiler to generate ref-impl/include/com-api files (only available under Windows NT, it says) Thanks to Dudley Beenham at Sony for tracing out this summary. ​ ​

Defining the business need Developing open specifications Ensuring interoperability Enabling networked media NMOS AT A GLANCE Benefits to end users, vendors and integrators Free downloads and test tools Proven products from a range of suppliers How to specify NMOS in your procurement process And more Advanced Authoring Format A file interchange format designed for the video post-production and authoring. ​ ​ ​ ​ Material Exchange Format AMWA Application Specifications define a set of rules that constrain the MXF standard for a particular application, includes AS-11. ​ Networked Media Open Specifications Networked Media Open Specifications result from the development of interoperable protocols for control and monitoring of media devices in an IP-based environment. Business Agility in Media Workflows ​ A new research initiative to understand the evolving requirements of media companies ​ ​ ​ News AMWA WORKSHOP ON SECURITY IN MEDIA INFRASTRUCTURES. Click through. More Information ​ Developers Brochures White Papers & Reference Documents Videos Newsletter Archive Logos ByLaws, Policy Documents & Licenses Subscribe to our newsletter Liaison Organisations