AMWA Advanced Media Workflow Association, makers of NMOS, Networked Media Open Specifications, video and audio IP based architectures for broadcast media, professional video and audio facilities. NMOS is instrumental for IPMX and ST 2110. If you use ST 2110 or IPMX, you likely rely on NMOS already. Find out what else it can do for you. Proven products from a range of suppliers. NMOS – What's in it for you as an end user, manufacturer, or integrator? • NMOS is the open-source "special sauce" that enables connection, management, and control of your IP video and audio devices from different manufacturers – in a common eco-system and in an interoperable way. NMOS works whether you're using 2110 or IPMX, locally or in the cloud. • NMOS (networked media open specifications) lets equipment from different companies all work together. Since AMWA's NMOS is an open set of specifications, it gives you a significant advantage by preventing vendor lock-in. It means you can choose the equipment you prefer, and build the system that best meets your needs, without being tied to any specific manufacturer. Members Principal Members General General Members Associate Members Individual Individual Members Phil Bernal PB Technologies Group LLC Kenny Munro Jim Trainor Jed Deame Nextera Phillip Nguyen Pedro Ferreira BISECT, LDA Joost Rovers Rovers IT Eben Jenkins Nicolas Sturmel Defining the business need Developing open specifications Ensuring interoperability Enabling networked media 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. Business Agility in Media Workflows "IT Thinking" can deliver the business agility needed by today's media companies. More Information Developers Brochures White Papers & Reference Documents Videos Newsletter Archive Logos ByLaws, Policy Documents & Licenses Liaison Organisations

This page isn't available. Sorry about that. Try going back to the homepage. Return Home

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.

NMOS Overview. AMWA's Networked Media Open Specifications (NMOS) exist to support the industry adoption of an open, inter-operable approach to IP-based infrastructures. A family of open-source, free-of-charge specifications that enable interoperability on the control layer for media devices on an IP infrastructure. If you use ST 2110 or IPMX, it's likely you already rely on NMOS. 🎯 NMOS is the open-source "special sauce" that enables connection, management, and control of your IP video and audio devices from different manufacturers – in a common eco-system and in an interoperable way. NMOS works whether you're using ST 2110 or IPMX, locally or in the cloud. 🎯 NMOS (networked media open specifications) lets equipment from different companies all work together. Since AMWA's NMOS is an open set of specifications, it gives you a significant advantage by preventing vendor lock-in. It means you can choose the equipment you prefer, and build the system that best meets your needs, without being tied to any specific manufacturer. A guide to Resources for Implementers and Integrators is here to make life easier. "NMOS – What's In It For Me? " See the video here . Whether you work in Broadcast or Pro-AV, the ability to quickly and reliably set up a working system is vital to business efficiency. This may be building permanent or temporary facilities - or changing operational set-ups between TV shows or professional AV activities. If you work in traditional media or a professional communications environment, NMOS, Networked Media Open Specifications, exists to provide an effective open control layer to get you working as easily as possible. How Does NMOS Help? Read What NMO S is. What NM OS isn’t . A non-technical overview which also explains the benefits to your job in the media industry. NMOS offers significant benefits over proprietary solutions . Watch a video on Why We More Than Ever Need an Open Control Plane Watch a video describing what NMOS is, and how NMOS has evolved Beyond Routing Control. NMOS is a fundamental building block in an open, fully-functioning architecture. Read how it fits within the JT-NM full stack and the EBU Technology Pyramid . NMOS benefits if you're a manufacturer or supplier: You can integrate your products into larger ecosystems without developing proprietary protocols Your equipment becomes more attractive to customers who want flexible, multi-vendor solutions You save development time/costs by using established open standards You can participate in shaping the standard's evolution Your products gain broader market appeal since they can work alongside competitors' equipment You avoid the costs and complexity of maintaining proprietary protocols No need to develop custom control protocols or monitoring solutions Equipment status and health monitoring become standardized NMOS benefits if you're a customer, integrator, or end user: Freedom from vendor lock-in gives you more choice and control You can select best-of-breed equipment for each part of their system Lower total cost of ownership by avoiding proprietary ecosystem costs More flexible upgrade paths since you’re not tied to a single vendor Easier to expand systems gradually with equipment from different suppliers Freedom to choose equipment that fits your budget Simpler training and operations with standardized interfaces Reduced risk since you’re not dependent on a single vendor's business decisions Consistent status monitoring and control across the entire system The NMOS ROADMAP Since the NMOS developments began, there has been a steady demand from users to provide additional functionality. Version 2 of the NMOS Roadmap shows all of these key developments, now grouped to show the overall benefits and how they work together. These include the many developments that are finished and deployed, along with “work in progress” and future additions. Much of the new work is focused on operational control of devices, accommodation of compressed video formats to extend the use of NMOS between media premises and to / from the Cloud, and new developments for monitoring and configuration are coming up. Also, as the IPMX standard is adopted in the Pro AV market, NMOS will bring valuable plug and play benefits to both end users and suppliers alike. The roadmap includes Interface Specifications (IS-xx), Best Current Practices (BCP-xx) and Data Model Specifications (MS-xx), to show the functionality and benefits that they offer. Please note - there is a range of supporting material for these technical developments. These can be found as INFO documents on the Specifications page of AMWA.tv . What you will find Core F unctionality Security Features Compressed Streams Control and Monitoring System Features Testing Tools Join the family of NMOS users and suppliers AMWA members have invested thousands of hours in developing the open specifications that are in use today. But we also encourage non-members to benefit from this development time by including the code, free of charge, in their product range. See below for a range of resources that are available to help you. How can I use it? Get started with the easy-NMOS tool from NVIDIA. Watch the presentations which explain the benefits and how to use the easy-NMOS tool, with a practical demonstration. The business benefits of using NMOS with DNS-SD for discovery of devices on your network. Use the free of charge test suites . Watch the NMOS Test Tool tutorial with a demos of installation and a typical test. Read how new versions and upgrades are handled, for example on IS-04. NMOS is available fROm a broad range of vendors Suppliers and customers worldwide have signed up to participate in the NMOS developments. Big industry names and small independent specialists are contributing to the working groups, showing a long-term commitment to the success of this initiative. The JT-NM Tested program offers confidence to purchasers that products have been thoroughly checked by industry experts. Where can I FIND IT? The AMWA maintains a catalog of NMOS-enabled products and software . You'll find links to the existing catalogs and application form so that new entries can be added. The JT-NM Tested program has catalogs for successful products with carefully documented procedures and results. Watch the JT-NM Tested presentation from IBC . nmos developments are based on real business needs End users and their suppliers are working towards open standards and specifications to escape the limitations of closed technology solutions. Customers want the ability to build systems using products with the best features. Vendors value the ability to make sales into the widest customer markets. Will it help my business? Read What NMOS is. What NMOS isn’t to learn how all vendors and their customers can benefit by adopting NMOS. Many suppliers are participating in the AMWA's NMOS initiative to participate in developments and implement the APIs. NMOS is a fundamental part of an ip-based infrastructure If you're using ST 2110, it's likely you're already using AMWA's NMOS. And NMOS is a part of IPMX. For an excellent picture of how end users are employing NMOS and IP-based architectures - plus how their suppliers have stepped up to satisfy those needs, please use the Resources option on the AIMS IP Showcase website. There you will find many presentations delivered online and at trade shows. And if you want to specify NMOS in your procurement processes, there is a standard form of words at the bottom of this section, prepared by the EBU. Is there a risk in adopting it? Four media organisations joined a panel discussion at IBC on Real-World SMPTE ST 2110 and AMWA NMOS Implementations . At IBC, Riedel gave a presentation on secure Discovery and Connection of ST 2110 Media Devices An example of the practical application of NMOS is included in the Mellanox (now NVIDIA) presentation at IBC in "Simplifying JT-NM TR-1001-1 Deployments Through Microservices". How to specify NMOS in a system tender or specification. SO what for the future? IP-based infrastructures take us on important first steps, liberating workflows from traditional, hard-wired, point-to-point installations. However, the professional media industry can also harness the power of IT infrastructures that we have come to expect every day in our office systems. AMWA's NMOS control, NMOS minimum status reporting, and NMOS as a key part of IPMX are working now and continue to evolve. The future vision NMOS provides a path to true IT infrastructures. A presentation by Brad Gilmer explains the business benefits that an IT infrastructure can deliver and how flexible professional media workflows can be built using IT principles. At IBC, Gordon Castle of Discovery / Eurosport gave his vision for an IT future .

How to download Cygwin tools The GNU based Cygwin tools include CVS with SSH (which are required for read/write access to the repository) and a free Bash shell which is useful for the command line. Return to Developers Downloading starts with the setup tool setup.exe follow these instructions to load the minimum, bash, cygwin, openssh, cvs. Note that the recommended root directory for installs is C:\cygwin If you are not running as Administrator it's best to select the option to install as Administrator or the setup program will fail to automatically create some important files (such as cygwin's equivalent of /etc/passwd). When prompted for "Default Text File Type". The choices will be "DOS", or "Unix" - choose DOS because you want CVS to perform \n -> \r\n conversion as it checks out files. The setup.exe program can allow you to skip packages by clicking on the circular arrow icon. (Downloading the full distribution can take over an hour at 56K)

You are being referred to our external site. Click here if this does not forward automatically https://github.com/AMWA-TV/nmos/wiki/IS-04 Go to Search Results Go to the Specifications Page

This is the site map for AMWA advanced media workflow association Site Map About AMWA Mission & Vision Board of Directors & Staff Committee Chairs Events Privacy Notice Contact Specifications Specifications Overview Application Specifications Data Models Interface Specifications Join AMWA Business Benefits Technology Benefits Membership Levels Members Principal Members General Members Associate Members Individual Members External Links Basecamp Resources Logos AMWA Community Newsletters Videos White Papers Brochures Policy Documents & Licenses Developers Developer Tools AMWA Developers Library AAF SDK AAF Programming Examples AAF Tutorial

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.

You are being referred to our external site. Click here if this does not forward automatically https://github.com/AMWA-TV/nmos/wiki/IS-06 Go to Search Results Go to the Specifications Page

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)

AMWA NMOS member companies listing is here - AMWA advanced media workflow association NMOS Users & Suppliers End Users Suppliers Return to NMOS

AMWA Advanced Media Workflow Association, makers of NMOS, Networked Media Open Specifications, video and audio IP based architectures for broadcast media, professional video and audio facilities. NMOS is instrumental for IPMX and ST 2110. NMOS is open source and free NMOS Solutions This page lists open source, free and commercial implementations of NMOS specifications. This list is unlikely to be complete. Note that inclusion in this list is not an endorsement by AMWA or a guarantee of conformance to the specifications. To have an implementation added, please request a link to the submission form by (clicking here - email address link). Upon receipt, include the information required as shown in the table below. The implementation must be available, and a link to a repo, download page, or product page must be provided.

NMOS Overview. AMWA's Networked Media Open Specifications (NMOS) exist to support the industry adoption of an open, inter-operable approach to IP-based infrastructures. A family of open, free of charge specifications that enable interoperability between media devices on an IP infrastructure. Any questions not answered below? Try the NMOS FAQs or ask us at info@AMWA.tv How Does NMOS Help? Read What NMOS is. What NMOS isn’t . A non-technical overview which also explains the benefits to your job in the media industry. NMOS offers significant benefits over proprietary solutions . Watch a video describing how NMOS has evolved Beyond Routing Control Watch a video about the Growth of NMOS and Why We More Than Ever Need an Open Control Plane Examine an open, fully-functioning architecture and see how NMOS is a fundamental building block in "Networked Media Systems - the Big Picture ". Also see how it fits within the JT-NM full stack and the EBU Technology Pyramid . Join the family of NMOS users and suppliers AMWA members have invested thousands of hours in developing the open specifications that are in use today. But we also encourage non-members to benefit from this development time by including the code, free of charge, in their product range. See below for a range of resources that are available to help you. How can I use it? Watch the easy-NMOS videos ; discover what it is and how to use it. Get started with the easy-NMOS tool from NVIDIA. Use the free of charge test suites . Watch the presentation on the open source AMWA NMOS Testing Tool from IBC2019. Read how new versions and upgrades are handled, for example on IS-04. NMOS is available from a broad range of vendors Suppliers worldwide have signed up to participate in the NMOS developments. Big industry names and small independent specialists are contributing to the working groups, showing a long-term commitment to the success of this initiative. The JT-NM Tested program offers confidence to purchasers that products have been thoroughly checked by industry experts. Where can I buy it? A list of hardware and software products known to the AMWA. This includes links to the supplier's own websites. The JT-NM Tested program has catalogs for successful products with carefully documented procedures and results. Watch the JT-NM Tested presentation from IBC2022 . nmos developments are based on real business needs End users and their suppliers are working towards open standards and specifications to escape the limitations of closed technology solutions. Customers want the ability to build systems using products with the best features. Vendors value the ability to make sales into the widest customer markets. Will it help my business? Read What NMOS is. What NMOS isn’t to learn how all vendors and their customers can benefit by adopting NMOS. Many end users and suppliers are supporting the AMWA's NMOS initiative to participate in developments and implement IP-based infrastructures. NMOS is a fundamental part of an ip-based infrastructure For an excellent picture of how both vendors and their customers are embracing NMOS and IP-based architectures, the AIMS IP Showcase presentations from IBC2019 shows how NMOS is being developed and adopted in a wide range of applications. And for end users who want to specify NMOS in their procurement processes, there is a standard form of words, prepared by the EBU. Is there a risk in adopting it? Four media organisations joined a panel discussion at IBC2019 on Real-World SMPTE ST 2110 and AMWA NMOS Implementations . At IBC2019, Riedel gave a presentation on secure Discovery and Connection of ST 2110 Media Devices An example of the practical application of NMOS is included in the Mellanox (now NVIDIA) presentation at IBC2019 in "Simplifying JT-NM TR-1001-1 Deployments Through Microservices". How to specify NMOS in a system tender or specification. SO what for the future? IP-based infrastructures take us on important first steps, liberating workflows from traditional, hard-wired, point-to-point installations. However, the professional media industry can also harness the power of IT infrastructures that we have come to expect every day in our office systems. The future vision NMOS provides a path to true IT infrastructures. A presentation by Brad Gilmer explains the business benefits that an IT infrastructure can deliver and how flexible professional media workflows can be built using IT principles. At IBC2019, Gordon Castle of Discovery / Eurosport gave his vision for an IT future .

AS-11 AS-11 X9: MXF Program Contribution - NABA DPP HD (AVC) This is a Specification in the AS-11 family of Specifications . Delivery of finished HD (AVC) programs 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.

Find out about NMOS for Pro AV and IMPX. AMWA's Networked Media Open Specifications (NMOS) exist to support the industry adoption of an open, inter-operable approach to IP-based infrastructures. NMOS for Pro AV NMOS comes with IPMX – NMOS is "baked into" IPMX. NMOS facilitates device discovery and registration, making IPMX more "plug and play." AMWA is collaborating with VSF and AIMS to complete and complement IMPX. What's IPMX? IPMX (Internet Protocol Media Experience) is a proposed set of open standards and specifications to enable the carriage of compressed and uncompressed video, audio and data over IP networks for the pro AV market. IPMX includes provisions for control, copy protection, connection management and security. IPMX takes an open-standards approach to ensure that accessibility, ease of use, and implementation are available to all. The authors of its components come from organizations that represent the best interests of the pro AV market as a whole, rather than the interests of the few. This is in contrast to other solutions that, while calling themselves standards, are owned by a single entity that controls their intellectual property and usage, whether it is in the form of hardware, software, or a combination of the two. IPMX builds on foundational work from AWMA, SMPTE, and VSF. More About NMOS As mentioned above, NMOS is part of the specifications that make up IPMX – but it's used in other systems and frameworks, too. SMPTE ST 2110 systems often use NMOS. You can find out more about NMOS here. Pro AV Activities Happening within AMWA • IPMX/HKEP working group

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.