DOCSLIB.ORG

Common Metadata Ref: TR-META-CM Version: 2.7 DRAFT DRAFT Date: September 23,2018

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Common Metadata Ref: TR-META-CM Version: 2.7 DRAFT DRAFT Date: September 23,2018 Common Metadata Ref: TR-META-CM Version: 2.7 DRAFT DRAFT Date: September 23,2018 Common Metadata ‘md’ namespace Motion Picture Laboratories, Inc. i Common Metadata Ref: TR-META-CM Version: 2.7 DRAFT DRAFT Date: September 23,2018 CONTENTS 1 Introduction .............................................................................................................. 1 1.1 Overview of Common Metadata ....................................................................... 1 1.2 Document Organization .................................................................................... 1 1.3 Document Notation and Conventions ............................................................... 2 1.3.1 XML Conventions ...................................................................................... 2 1.3.2 General Notes ........................................................................................... 3 1.4 Normative References ...................................................................................... 4 1.5 Informative References..................................................................................... 7 1.6 Best Practices for Maximum Compatibility ........................................................ 8 2 Identifiers ............................................................................................................... 10 2.1 Identifier Structure .......................................................................................... 10 2.1.1 ID Simple Types ...................................................................................... 11 2.2 Asset Identifiers .............................................................................................. 11 2.2.1 ContentID ................................................................................................ 11 2.2.2 APID ........................................................................................................ 13 2.3 Organization ID ............................................................................................... 14 3 General Types Encoding ....................................................................................... 15 3.1 Language Encoding ........................................................................................ 15 3.2 Region encoding ............................................................................................. 15 3.3 Date and Time encoding ................................................................................. 16 3.3.1 Duration ................................................................................................... 16 3.3.2 Time ........................................................................................................ 16 3.3.3 Dates and times ...................................................................................... 16 3.3.4 Date and time ranges .............................................................................. 17 3.4 String encoding ............................................................................................... 17 3.5 Organization Naming and Credits ................................................................... 17 3.5.1 CompanyDisplayCredit-type .................................................................... 18 3.5.2 AssociatedOrg-type ................................................................................. 18 3.6 People Naming and Identification ................................................................... 19 3.6.1 PersonName-type.................................................................................... 19 3.6.2 PersonIdentifier-type ............................................................................... 20 3.7 Money-type and Currency .............................................................................. 20 3.8 Role Encoding, Role-type ............................................................................... 20 3.9 Keywords Encoding ........................................................................................ 21 3.9.1 Name/Value Pairs, NVPair-type, NVPairMoney-type .............................. 21 3.10 Personal/Corporate Contact Information, ContactInfo-type ............................ 21 3.11 Cryptographic Hash ........................................................................................ 22 3.12 GroupingEntity-type ........................................................................................ 22 3.13 Private Data .................................................................................................... 23 3.14 MIME .............................................................................................................. 23 3.15 Workflow Attribute Group ................................................................................ 23 3.16 Gender-type .................................................................................................... 24 Motion Picture Laboratories, Inc. ii Common Metadata Ref: TR-META-CM Version: 2.7 DRAFT DRAFT Date: September 23,2018 3.17 Compliance-type ............................................................................................. 25 4 Basic Metadata ...................................................................................................... 27 4.1 BasicMetadata-type ........................................................................................ 27 4.1.1 Basic Metadata Definitions ...................................................................... 29 4.1.2 BasicMetadataInfo-type ........................................................................... 35 4.1.3 ContentIdentifier-type, AltIdentifier-type .................................................. 39 4.1.4 BasicMetadataPeople-type ...................................................................... 39 4.2 Compilation Object ......................................................................................... 45 4.2.1 CompObj-type ......................................................................................... 45 4.2.2 CompObjID-type ...................................................................................... 45 4.2.3 CompObjData-type .................................................................................. 45 4.2.4 Comp-ObjEntry-type ................................................................................ 46 4.3 Content Related To ........................................................................................ 47 4.3.1 ContentRelatedTo-type ........................................................................... 47 4.3.2 ContentRelatedToRelationship-type ........................................................ 48 4.3.3 ContentRelatedToWork-type ................................................................... 49 5 Digital Asset Metadata ........................................................................................... 50 5.1 Digital Asset Metadata Description ................................................................. 50 5.2 Definitions ....................................................................................................... 50 5.2.1 DigitalAssetMetadata-type and DigitalAssetSet-type............................... 50 5.2.2 DigitalAssetAudioData-type ..................................................................... 51 5.2.3 DigitalAssetAudioEncoding-type ............................................................. 53 5.2.4 DigitalAssetVideoData-type ..................................................................... 59 5.2.5 DigitalAssetVideoEncoding-type ............................................................. 61 5.2.6 DigitalAssetVideoPicture-type ................................................................. 65 5.2.7 DigitalAssetSubtitleData-type .................................................................. 77 5.2.8 DigitalAssetImageData-type .................................................................... 80 5.2.9 DigitalAssetInteractiveData-type ............................................................. 81 5.2.10 DigitalAssetWatermark-type .................................................................... 85 5.2.11 Cards ....................................................................................................... 85 5.2.12 DigitalAssetAncillary-type ........................................................................ 87 6 Container Metadata ............................................................................................... 90 6.1 Container Metadata Description ..................................................................... 90 6.2 Definitions ....................................................................................................... 90 6.2.1 ContainerMetadata-type .......................................................................... 90 6.2.2 ContainerProfile-type ............................................................................... 93 7 Content Ratings ..................................................................................................... 94 7.1 Description ...................................................................................................... 94 7.2 Rules .............................................................................................................. 94 7.3 Definition ......................................................................................................... 94 7.3.1 ContentRating-type.................................................................................
Load more

Recommended publications
  • Creating 4K/UHD Content Poster
    Creating 4K/UHD Content Colorimetry Image Format / SMPTE Standards Figure A2. Using a Table B1: SMPTE Standards The television color specification is based on standards defined by the CIE (Commission 100% color bar signal Square Division separates the image into quad links for distribution. to show conversion Internationale de L’Éclairage) in 1931. The CIE specified an idealized set of primary XYZ SMPTE Standards of RGB levels from UHDTV 1: 3840x2160 (4x1920x1080) tristimulus values. This set is a group of all-positive values converted from R’G’B’ where 700 mv (100%) to ST 125 SDTV Component Video Signal Coding for 4:4:4 and 4:2:2 for 13.5 MHz and 18 MHz Systems 0mv (0%) for each ST 240 Television – 1125-Line High-Definition Production Systems – Signal Parameters Y is proportional to the luminance of the additive mix. This specification is used as the color component with a color bar split ST 259 Television – SDTV Digital Signal/Data – Serial Digital Interface basis for color within 4K/UHDTV1 that supports both ITU-R BT.709 and BT2020. 2020 field BT.2020 and ST 272 Television – Formatting AES/EBU Audio and Auxiliary Data into Digital Video Ancillary Data Space BT.709 test signal. ST 274 Television – 1920 x 1080 Image Sample Structure, Digital Representation and Digital Timing Reference Sequences for The WFM8300 was Table A1: Illuminant (Ill.) Value Multiple Picture Rates 709 configured for Source X / Y BT.709 colorimetry ST 296 1280 x 720 Progressive Image 4:2:2 and 4:4:4 Sample Structure – Analog & Digital Representation & Analog Interface as shown in the video ST 299-0/1/2 24-Bit Digital Audio Format for SMPTE Bit-Serial Interfaces at 1.5 Gb/s and 3 Gb/s – Document Suite Illuminant A: Tungsten Filament Lamp, 2854°K x = 0.4476 y = 0.4075 session display.
    [Show full text]
  • Technical Specifications for Broadcast Program Material August 2018
    Technical Specifications for Broadcast Program Material August 2018 Delivery Specifications: Fox Networks broadcast exclusively in 1280 x 720/59.94. All material shall be delivered per SMPTE ST 296:2012 with 5.1 digital sound per ITU--R BS 775--3 (08/2012) Loudness specifications per ATSC RP/A85 (Doc. A/85 12 March 2013) Programming that does not meet this specification is subject to rejection and correction at the supplier’s expense File Delivery: Fox Networks only accepts MXF file delivery standardized in SMPTE ST 377--1:2011 The file name shall match the on air traffic I.D. SD file delivery requires prior authorization Stereo, 2--channel and monophonic deliveries require prior authorization File Format Specifications: Files shall be wrapped in MXF per SMPTE ST 378:2004, OP1a Segments within the file shall be separated by a minimum of 2 seconds black MXF files shall have one MPEG--2 video stream per ISO/IEC 13818--2:2013 MPEG--2 video essence shall be 1280 x 720/59.94, 4:2:2 profile @ high level, and 50Mbps 5.1 digital surround shall be in phase Channel Channel 1: Left 2: Right 3: Center 4: LFE‐‐‐Low Frequency Enhancement 5: Left surround 6: Right surround 7: DVS, SAP or Mono 8: Mono 9‐‐‐12: (n/a or not used) MXF files shall have 8 audio PCM 16 (16 bits @ 48 kHz PCM) or 8 audio PCM 24 (24 bits @ 48 kHz PCM) channels per SMPTE ST 377--4:2012 Dolby E is not accepted Programming shall be created such that any down mix from 5.1 to stereo or mono represents the original mix 1 Technical Specifications For Broadcast Program Material August 2018 The dynamic range of the material shall be suitable for television broadcast The loudness shall be measured across all channels, except LFE (Low--Frequency Enhancement) in units of LKFS per ATSC RP/A85 (Doc.
    [Show full text]
  • MXF Application Specification for Archiving and Preservation
    AS-AP MXF Archive and Preservation DRAFT FADGI Application Specification AS-AP MXF Archive and Preservation August 15, 2011 (rev 1h) Document Status This document-in-progress is being drafted by the Audio-Visual Working Group of the Federal Agencies Digitization Guidelines Initiative (FADGI; http://www.digitizationguidelines.gov/audio-visual/). The Working Group will transmit a refined version of this MXF Application Specification for Archive and Preservation (AS-AP) for finalization and publication by the Advanced Media Workflow Association (AMWA). Finalization will also depend upon the resolution of some technical matters that are dependencies for this specification. These dependencies are highlighted in the explanatory notes within this specification and in the accompanying document Preservation Video File Format Issues and Considerations (http://www.digitizationguidelines.gov/audio-visual/documents/FADGI_MXF_ASAP_Issues_20110815.pdf). This document has been drafted in the style of other AMWA application specifications (http://www.amwa.tv/projects/application_specifications.shtml), has borrowed a number of features from AS- 03, and refers to AS-02. Since AS-02 has not been published at this writing, this document (especially Annex B) includes wording copied from draft versions of that specification. Executive Summary This document describes 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 and metadata. Archive and Preservation and files (AS-AP files) may contain a single item, or an entire series of items. Various configurations of sets of AS-AP files are discussed in the Overview. AS-AP files are intended to be used in combination with external finding aids or catalog records.
    [Show full text]
  • Khronos Data Format Specification
    Khronos Data Format Specification Andrew Garrard Version 1.2, Revision 1 2019-03-31 1 / 207 Khronos Data Format Specification License Information Copyright (C) 2014-2019 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. This version of the Data Format Specification is published and copyrighted by Khronos, but is not a Khronos ratified specification. Accordingly, it does not fall within the scope of the Khronos IP policy, except to the extent that sections of it are normatively referenced in ratified Khronos specifications. Such references incorporate the referenced sections into the ratified specifications, and bring those sections into the scope of the policy for those specifications. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible.
    [Show full text]
  • Avid Filmscribe User's Guide
    Avid® FilmScribe™ User’s Guide ™ make manage move | media Avid ® Copyright and Disclaimer Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc. The software described in this document is furnished under a license agreement. You can obtain a copy of that license by visiting Avid's Web site at www.avid.com. The terms of that license are also available in the product in the same directory as the software. The software may not be reverse assembled and may be used or copied only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license agreement. Avid products or portions thereof are protected by one or more of the following United States Patents: 4,746,994; 4,970,663; 5,045,940; 5,077,604; 5,267,351; 5,309,528; 5,355,450; 5,396,594; 5,440,348; 5,452,378; 5,467,288; 5,513,375; 5,528,310; 5,557,423; 5,568,275; 5,577,190; 5,583,496; 5,584,006; 5,627,765; 5,634,020; 5,640,601; 5,644,364; 5,654,737; 5,724,605; 5,726,717; 5,729,673; 5,745,637; 5,752,029; 5,754,180; 5,754,851; 5,799,150; 5,812,216; 5,828,678; 5,842,014; 5,852,435; 6,061,758; 6,532,043; 6,546,190; 6,636,869; 6,747,705.
    [Show full text]
  • Yasser Syed & Chris Seeger Comcast/NBCU
    Usage of Video Signaling Code Points for Automating UHD and HD Production-to-Distribution Workflows Yasser Syed & Chris Seeger Comcast/NBCU Comcast TPX 1 VIPER Architecture Simpler Times - Delivering to TVs 720 1920 601 HD 486 1080 1080i 709 • SD - HD Conversions • Resolution, Standard Dynamic Range and 601/709 Color Spaces • 4:3 - 16:9 Conversions • 4:2:0 - 8-bit YUV video Comcast TPX 2 VIPER Architecture What is UHD / 4K, HFR, HDR, WCG? HIGH WIDE HIGHER HIGHER DYNAMIC RESOLUTION COLOR FRAME RATE RANGE 4K 60p GAMUT Brighter and More Colorful Darker Pixels Pixels MORE FASTER BETTER PIXELS PIXELS PIXELS ENABLED BY DOLBYVISION Comcast TPX 3 VIPER Architecture Volume of Scripted Workflows is Growing Not considering: • Live Events (news/sports) • Localized events but with wider distributions • User-generated content Comcast TPX 4 VIPER Architecture More Formats to Distribute to More Devices Standard Definition Broadcast/Cable IPTV WiFi DVDs/Files • More display devices: TVs, Tablets, Mobile Phones, Laptops • More display formats: SD, HD, HDR, 4K, 8K, 10-bit, 8-bit, 4:2:2, 4:2:0 • More distribution paths: Broadcast/Cable, IPTV, WiFi, Laptops • Integration/Compositing at receiving device Comcast TPX 5 VIPER Architecture Signal Normalization AUTOMATED LOGIC FOR CONVERSION IN • Compositing, grading, editing SDR HLG PQ depends on proper signal BT.709 BT.2100 BT.2100 normalization of all source files (i.e. - Still Graphics & Titling, Bugs, Tickers, Requires Conversion Native Lower-Thirds, weather graphics, etc.) • ALL content must be moved into a single color volume space. Normalized Compositing • Transformation from different Timeline/Switcher/Transcoder - PQ-BT.2100 colourspaces (BT.601, BT.709, BT.2020) and transfer functions (Gamma 2.4, PQ, HLG) Convert Native • Correct signaling allows automation of conversion settings.
    [Show full text]
  • Eidr 2.6 Data Fields Reference
    EIDR 2.6 DATA FIELDS REFERENCE Table of Contents 1 INTRODUCTION ............................................................................................................................................... 5 1.1 Introduction to Content ................................................................................................................................ 5 1.2 Composite Details ......................................................................................................................................... 5 1.3 How to read the Tables ................................................................................................................................. 6 1.4 EIDR IDs ........................................................................................................................................................ 7 2 BASE OBJECT TYPE ......................................................................................................................................... 9 2.1 Summary ...................................................................................................................................................... 9 2.2 Referent Type Details ................................................................................................................................. 25 2.3 Title Details ................................................................................................................................................ 26 2.4 Language Code Details ...............................................................................................................................
    [Show full text]
  • How Close Is Close Enough? Specifying Colour Tolerances for Hdr and Wcg Displays
    HOW CLOSE IS CLOSE ENOUGH? SPECIFYING COLOUR TOLERANCES FOR HDR AND WCG DISPLAYS Jaclyn A. Pytlarz, Elizabeth G. Pieri Dolby Laboratories Inc., USA ABSTRACT With a new high-dynamic-range (HDR) and wide-colour-gamut (WCG) standard defined in ITU-R BT.2100 (1), display and projector manufacturers are racing to extend their visible colour gamut by brightening and widening colour primaries. The question is: how close is close enough? Having this answer is increasingly important for both consumer and professional display manufacturers who strive to balance design trade-offs. In this paper, we present “ground truth” visible colour differences from a psychophysical experiment using HDR laser cinema projectors with near BT.2100 colour primaries up to 1000 cd/m2. We present our findings, compare colour difference metrics, and propose specifying colour tolerances for HDR/WCG displays using the ΔICTCP (2) metric. INTRODUCTION AND BACKGROUND From initial display design to consumer applications, measuring colour differences is a vital component of the imaging pipeline. Now that the industry has moved towards displays with higher dynamic range as well as wider, more saturated colours, no standardized method of measuring colour differences exists. In display calibration, aside from metamerism effects, it is crucial that the specified tolerances align with human perception. Otherwise, one of two undesirable situations might result: first, tolerances are too large and calibrated displays will not appear to visually match; second, tolerances are unnecessarily tight and the calibration process becomes uneconomic. The goal of this paper is to find a colour difference measurement metric for HDR/WCG displays that balances the two and closely aligns with human vision.
    [Show full text]
  • Vcube User Manual
    Table of Contents Table of Contents Welcome 1 What's New in VCube 2? 2 VCube Overview 5 How to Update 6 VCube User Interface 7 Tool and Transport Bars 11 Tool Bar 12 Transport Bar 16 Quick Settings for SD and HD Video Formats 19 Quick Settings for SD 21 Quick Settings for HD 23 Control Pages 25 Files 26 VCube Compositions 29 OMF Compositions 32 AAF and Apple XML Compositions 34 Media Files 36 Import Composition and Export Changes 38 Import Layer 39 Convert Still Images 40 Locators 42 View 44 Clips Information 45 Shortcuts 49 Workspace 50 ii Table of Contents Edit 52 Main 53 Clips 54 Layers 56 Tracks 58 Settings 59 Presets 60 Formats & Synchro 62 Video I/O 67 Xena LS Plug-in 68 Xena LH Plug-in 70 Xena 2 Plug-in 72 Overlay 74 Preview 76 Composition 78 Disk & Network Cache Buffers 81 User Interface 82 Isis 83 Encryption 84 Media Settings 90 Timeline 91 Video Engine 92 Output View 93 Script View 95 Recording and Editing 96 Recording 97 Editing 103 Timeline 104 Editing Functions 106 Layer Controls 110 iii Table of Contents Motion Rectangles (PiP) 111 Selections and Groups 114 Watermark and Text 115 Watermark 116 Text Clip 117 Utility Clips 119 Countdown Clip 120 Wipe Clip 122 Video Test Patern Clip 123 Audio Tone Clip 124 Conforming and Reconforming 125 Conversions 134 Export 135 Convert Media Files 136 Render 140 Import Images Sequence 144 Media Wrapper 146 Frame Rate Management 147 Using the QuickTime File Format 148 Using the MXF File Format 150 Using the MPEG Codec 151 Basic Settings 153 Video Settings 154 Advanced Video Settings 157 Audio Settings 164 Multiplexer Settings 167 Synchronization 171 Connections for synchronization 174 iv Table of Contents The USB Sync Board Oprtion 175 USB Sync Board Installation 176 Specific Control Panels 177 Virtual Transport 180 Network 183 VCube Chasing Pyramix through Virtual Transport.
    [Show full text]
  • Khronos Data Format Specification
    Khronos Data Format Specification Andrew Garrard Version 1.3.1 2020-04-03 1 / 281 Khronos Data Format Specification License Information Copyright (C) 2014-2019 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. This version of the Data Format Specification is published and copyrighted by Khronos, but is not a Khronos ratified specification. Accordingly, it does not fall within the scope of the Khronos IP policy, except to the extent that sections of it are normatively referenced in ratified Khronos specifications. Such references incorporate the referenced sections into the ratified specifications, and bring those sections into the scope of the policy for those specifications. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible.
    [Show full text]
  • Research & Development White Paper
    Research & Development White Paper WHP 297 July 2015 Media Synchronisation in the IP Studio Robert Wadge BRITISH BROADCASTING CORPORATION White Paper WHP 297 Media Synchronisation in the IP Studio Robert Wadge Abstract Television production and broadcast facilities currently use specialised point-to- point unidirectional links to transport real-time video and audio synchronously around the plant. Broadcast industry interest in replacing this specialised infrastructure with an Internet Protocol based solution has been gathering pace in recent times, driven by economic and technical considerations. IP networks offer a bidirectional layered communications model. Data is moved across the network in packets. Moving audio and video over an IP network involves splitting the signals into packets, separating the data from its timing signal. This is a fundamentally different paradigm to the prevailing synchronous technology, which requires a fresh approach to timing and synchronisation in particular. This paper proposes an approach to timing and synchronisation of real-time video and audio by modelling these signals as a series of Events to which timestamps sampled from a high-resolution clock are bound. The clock is distributed to all devices using IEEE 1588 Precision Time Protocol (PTP). Events can be periodic or aperiodic within a series, comprising raw or compressed audio or video, or any other arbitrary time-related data. While certain aspects of this approach are novel, the principles on which it is based draw heavily on recent work in SMPTE and AES concerning timing and synchronisation in networked environments. Additional key words: Genlock, Timecode, SDI, RTP, Media Identity, Media Timing White Papers are distributed freely on request.
    [Show full text]
  • KONA Series Capture, Display, Convert
    KONA Series Capture, Display, Convert Installation and Operation Manual Version 16.1 Published July 14, 2021 Notices Trademarks AJA® and Because it matters.® are registered trademarks of AJA Video Systems, Inc. for use with most AJA products. AJA™ is a trademark of AJA Video Systems, Inc. for use with recorder, router, software and camera products. Because it matters.™ is a trademark of AJA Video Systems, Inc. for use with camera products. Corvid Ultra®, lo®, Ki Pro®, KONA®, KUMO®, ROI® and T-Tap® are registered trademarks of AJA Video Systems, Inc. AJA Control Room™, KiStor™, Science of the Beautiful™, TruScale™, V2Analog™ and V2Digital™ are trademarks of AJA Video Systems, Inc. All other trademarks are the property of their respective owners. Copyright Copyright © 2021 AJA Video Systems, Inc. All rights reserved. All information in this manual is subject to change without notice. No part of the document may be reproduced or transmitted in any form, or by any means, electronic or mechanical, including photocopying or recording, without the express written permission of AJA Video Systems, Inc. Contacting AJA Support When calling for support, have all information at hand prior to calling. To contact AJA for sales or support, use any of the following methods: Telephone +1.530.271.3190 FAX +1.530.271.3140 Web https://www.aja.com Support Email [email protected] Sales Email [email protected] KONA Capture, Display, Convert v16.1 2 www.aja.com Contents Notices . .2 Trademarks . 2 Copyright . 2 Contacting AJA Support . 2 Chapter 1 – Introduction . .5 Overview. .5 KONA Models Covered in this Manual .
    [Show full text]