This standard defines the services and protocols contained within the physical, data link, network, transport, and session layers of ESlan-1, a control and data network for use in television and audio program production, post-production, and distribution equipment. ESlan-1 is intended for application in small-to moderate-sized facilities requiring modest levels of performance. A study to determine limiting parameters on the size of ESlan-1 installations is currently being undertaken by the SMPTE. — This standard is to be read in conjunction with SMPTE EG 29, SMPTE EG 30, and with other documents listed in clause 2 and annex C.

This standard defines the status monitoring and diagnostics protocol (SMDP) used with a general-purpose communication link that connects to equipment used in the production, post-production, and/or transmission of visual and audio information. The communication link is separate and distinct from the supervisory interface for digital control (ANSI/SMPTE 207M). SMDP may be used when querying equipment for status and diagnostics information.

This standard describes the data format for the interchange of a list of audio/video content decisions which specify an audio/video product. Exchange of this information allows the audio/video product to be reproduced on a compatible editing system. Such a list is commonly referred to as an edit decision list. The transfer medium and storage format are not specified in this standard.

This standard defines the electrical and mechanical characteristics of an interface system comprised of a general-purpose communication channel and interface device(s) used for the transfer of data and digital control signals between equipment utilized in the production, post-production, and/or transmission of visual and aural information. It is intended that the communication channel and device(s) described in this standard be part of an overall equipment interface, allowing interconnection of programmable and nonprogrammable control and accessory equipment as required to configure an operational system with a defined function. The standard is also intended to allow rapid reconfiguration of a system providing more than one defined function utilizing a given group of equipment. — (1.1.1) The electrical and mechanical specifications set forth in this standard are intended for use in both fixed plant and field operational environments. These specifications take into account the requirement to function reliably without causing undue interference with other signals normally found in these environments. — (1.1.2) This standard defines the electrical and mechanical characteristics of the communication channel and the associated interface device(s), to the exclusion of design specifications, performance requirements, safety requirements, and the communications protocol used in or by such equipment. — (1.1.3) The primary intent of this standard is to establish an electrical and mechanical interface and communication channel for the purpose of interconnecting equipment by external means. This standard, or sections thereof, may be applied to the interconnection of elements within an item of equipment.

This document is Part 1 of a series of documents that specify the concepts, data structures and operations required to control modern media devices. This document presents a platform agnostic model that can in turn be adapted to any protocol, platform and/or architecture, for the purpose of machine level control of media devices on Internet Protocol networks. Further documents in this series will supply protocol and platform specific adaptations of this model. The Media Device Control (MDC) suite of standards addresses the low level, atomic operations needed to control media devices over the Internet Protocol, in a deterministic, low-latency manner. MDC is designed to bridge the gap between workflow level interfaces and the physical hardware and is intended for use on private networks, with sufficient bandwidth and bounded latency. While the control of devices over the Internet may be inherently supported, it is not recommended for low-latency applications, due to the unpredictable nature of public, general-purpose, networks.

The Media Device Control (MDC) specification defines a platform and protocol agnostic framework for the control of network-attached devices over Internet Protocol (IP) networks. The framework, known as the Media Device Control Framework (MDCF) defined by SMPTE ST 2071-1, can be implemented with nearly any Internet Protocol based transport protocol, but in order to support interoperability between implementations a single, minimal compliance, transport protocol must be defined. This single, minimal compliance protocol is referred to as the Media Device Control Protocol (MDCP). The Media Device Control Protocol (MDCP) is based on existing industry standards, simplifying the implementation and reducing the cost to implement, while supporting the implementation of vendor specific APIs, third party APIs, protocol extensions and the implementation of many existing standards relating to the control of media devices. Additional protocols may be implemented, but all implementations must implement the Media Device Control Protocol (MDCP) as it is defined within this document. These additional protocols should provide an additional means for controlling devices, but must not be required nor expose functionality that is not available via the Media Device Control Protocol (MDCP).

Purpose:

This document has an associated Data Supplement, accessible for download from the “Media” tab when the user has full-text access rights. SMPTE Data Supplements contain files intended for use with the SMPTE Engineering Document (Standard, Recommended Practice, or Engineering Guideline) with the corresponding filename and publication date. Use of these files without consulting the corresponding SMPTE Engineering Document is NOT supported. Interoperability will generally require adherence to additional guidelines and constraints specified in the corresponding prose document.

This document describes the Zero Configuration (ZeroConf) and service discovery mechanisms defined for the Media Device Control (MDC) [SMPTE ST 2071] suite of standards. Defining how MDC compliant devices utilize existing network services, or in the absence of such services, use existing Zero Configuration (ZeroConf) techniques and standards to automatically construct a fully functional system.

The Broadcast eXchange Format (BXF) defines the format and content of XML Messages for the interchange of data and metadata among professional systems, as follows: — 1. Broadcast schedules, including playout and record schedules — 2. As run information — 3. Content metadata, such as Content ID, Title, Duration, etc. — 4. Content management requests such as dub and purge requests — 5. Requests for transfer of content some of which will result in the transfer of Content essence between professional systems. — 6. Ports as used by TCP/IP for the exchange of messages. — The primary systems envisioned as users of this standard are: — Program Management Systems — Broadcast Traffic Systems — Master Control Automation Systems — Content Distribution Systems. — This document serves as the master document for the 2021 suite (thus its Part 1 designation). It includes general BXF details as well as informative notes. SMPTE 2021-0 provides a Roadmap for the 2021 Document Suite. Unless otherwise specified the order of precedence of the types of normative information in this document shall be as follows. Normative prose shall be the authoritative definition. Tables shall be next, followed by formal languages, then figures, and then any other language forms. In the event of a conflict between the schema and other information in this document, the schema is authoritative.

Purpose:

This document has an associated Data Supplement, accessible for download from the “Media” tab when the user has full-text access rights. SMPTE Data Supplements contain files intended for use with the SMPTE Engineering Document (Standard, Recommended Practice, or Engineering Guideline) with the corresponding filename and publication date. Use of these files without consulting the corresponding SMPTE Engineering Document is NOT supported. Interoperability will generally require adherence to additional guidelines and constraints specified in the corresponding prose document.

This Recommended Practice provides documentation of the BXF SDK, a set of DLLs provided alongside this document, intended to facilitate improved interoperability among Traffic and Automation Systems.

Purpose:

This document has an associated Data Supplement, accessible for download from the “Media” tab when the user has full-text access rights. SMPTE Data Supplements contain files intended for use with the SMPTE Engineering Document (Standard, Recommended Practice, or Engineering Guideline) with the corresponding filename and publication date. Use of these files without consulting the corresponding SMPTE Engineering Document is NOT supported. Interoperability will generally require adherence to additional guidelines and constraints specified in the corresponding prose document.

This recommended practice has the following objectives: Describe the types of messages that will be communicated amongst applications and their corresponding formats within BXF SMPTE 2021. Describe the aspects of the BXF protocol which are recommended that applications support to achieve maximum interoperability and also to identify those aspects of the protocol that are not recommended at this time. Describe the approaches for representing errors within BXF messages. Describe how XML schema extensions should be implemented to maximize interoperability between systems. Describe the following extensions: Usage attribute extension; Filename element extension; Configuration extension.