SMPTE ST 2067-101-2018 Interoperable Master Format - Output Profile List - Common Image Definitions and Macros.pdf

上传人:orderah291 文档编号:1046709 上传时间:2019-03-27 格式:PDF 页数:17 大小:201.12KB
下载 相关 举报
SMPTE ST 2067-101-2018 Interoperable Master Format - Output Profile List - Common Image Definitions and Macros.pdf_第1页
第1页 / 共17页
SMPTE ST 2067-101-2018 Interoperable Master Format - Output Profile List - Common Image Definitions and Macros.pdf_第2页
第2页 / 共17页
SMPTE ST 2067-101-2018 Interoperable Master Format - Output Profile List - Common Image Definitions and Macros.pdf_第3页
第3页 / 共17页
SMPTE ST 2067-101-2018 Interoperable Master Format - Output Profile List - Common Image Definitions and Macros.pdf_第4页
第4页 / 共17页
SMPTE ST 2067-101-2018 Interoperable Master Format - Output Profile List - Common Image Definitions and Macros.pdf_第5页
第5页 / 共17页
点击查看更多>>
资源描述

1、 Approved February 22, 2018 Copyright 2018 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 445 Hamilton Avenue., White Plains, NY 10601 (914) 761-1100 SMPTE ST 2067-101:2018 Revision of ST 2067-101:2014 SMPTE STANDARD Interoperable Master Format Output Profile List Common Image Definitions

2、 and Macros Page 1 of 17 pages Table of Contents 1 Scope 3 2 Conformance Notation 3 3 Normative References 3 4 XML Schema Definitions 4 5 Reference Image 4 6 Pixel Color Schemes 5 7 Pixel Decoder Macro 6 7.1 Structure 6 7.2 Processing Model 7 7.3 Output 8 8 Pixel Encoder Macro 8 8.1 Structure 8 8.2

3、Processing Model 9 8.3 Output 9 9 Image Crop Macro 9 9.1 Structure 9 9.2 ImageCropMacroType 11 9.3 Processing Model 12 9.4 Output 12 10 Image Scale Macro 13 10.1 Structure 13 10.2 Processing Model 15 10.3 Output 15 Annex A Lanczos Scaling (Normative) 16 Annex B Consolidated Schema (Informative) 17 S

4、MPTE ST 2067-101:2018 Page 2 of 17 pages Foreword SMPTE (the Society of Motion Picture and Television Engineers) is an internationally-recognized standards developing organization. Headquartered and incorporated in the United States of America, SMPTE has members in over 80 countries on six continent

5、s. SMPTEs Engineering Documents, including Standards, Recommended Practices, and Engineering Guidelines, are prepared by SMPTEs Technology Committees. Participation in these Committees is open to all with a bona fide interest in their work. SMPTE cooperates closely with other standards-developing or

6、ganizations, including ISO, IEC and ITU. SMPTE Engineering Documents are drafted in accordance with the rules given in its Standards Operations Manual. This SMPTE Engineering Document was prepared by Technology Committee 35PM. Intellectual Property At the time of publication no notice had been recei

7、ved by SMPTE claiming patent rights essential to the implementation of this Engineering Document. However, attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. SMPTE shall not be held responsible for identifying any or all such patent

8、rights. SMPTE ST 2067-101:2018 Page 3 of 17 pages 1 Scope This document specifies definitions, data structures and Macros applicable to image essence for use with the Interoperable Master Format (IMF) Output Profile List framework. 2 Conformance Notation Normative text is text that describes element

9、s of the design that are indispensable or contains the conformance language keywords: “shall“, “should“, or “may“. Informative text is text that is potentially helpful to the user, but not indispensable, and can be removed, changed, or added editorially without affecting interoperability. Informativ

10、e text does not contain any conformance keywords. All text in this document is, by default, normative, except: the Introduction, any section explicitly labeled as “Informative“ or individual paragraphs that start with “Note:” The keywords “shall“ and “shall not“ indicate requirements strictly to be

11、followed in order to conform to the document and from which no deviation is permitted. The keywords, “should“ and “should not“ indicate that, among several possibilities, one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is prefer

12、red but not necessarily required; or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. The keywords “may“ and “need not“ indicate courses of action permissible within the limits of the document. The keyword “reserved” indicates a provision that i

13、s not defined at this time, shall not be used, and may be defined in the future. The keyword “forbidden” indicates “reserved” and in addition indicates that the provision will never be defined in the future. A conformant implementation according to this document is one that includes all mandatory pr

14、ovisions (“shall“) and, if implemented, all recommended provisions (“should“) as described. A conformant implementation need not implement optional provisions (“may“) and need not implement them as described. Unless otherwise specified, the order of precedence of the types of normative information i

15、n this document shall be as follows: Normative prose shall be the authoritative definition; Tables shall be next; then formal languages; then figures; and then any other language forms. 3 Normative References The following standards contain provisions which, through reference in this text, constitut

16、e provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below. SM

17、PTE ST 377-1:2011, Material Exchange Format (MXF) File Format Specification Amendment 1:2012 to SMPTE ST 377-1:2011 Amendment 2:2012 to SMPTE ST 377-1:2011 SMPTE ST 2067-2:2016, Interoperable Master Format Core Constraints SMPTE ST 2067-101:2018 Page 4 of 17 pages SMPTE ST 2067-100:2014, Interoperab

18、le Master Format Output Profile List IEEE 754-2008, Standard for Floating-Point Arithmetic IETF (2005, January). RFC 3986 Uniform Resource Identifier (URI): Generic Syntax World Wide Web Consortium (W3C) (2004, October 28). XML Schema Part 1: Structures (Second Edition) World Wide Web Consortium (W3

19、C) (2004, October 28). XML Schema Part 2: Datatypes (Second Edition) 4 XML Schema Definitions This section shall apply whenever a data structure is specified using XML schema definitions as specified in W3C XML Schema Part 1: Structures and W3C XML Schema Part 2: Datatypes. In order to avoid duplica

20、tion between text and schema, the cardinality and default values of elements are specified in the schema definitions only. In the event of a conflict between schema definitions and the prose, the prose shall take precedence. Note: The prefix associated with each namespace in an XML Schema definition

21、 document is arbitrary, and an Output Profile List instance can use other prefix value for the same namespace. The target namespace of XML Schema definitions, i.e. the value of the targetNamespace attribute of the schema element, allows implementations to unambiguously identify the defining specific

22、ation. Specifications that modify the schema definitions or the semantics of the elements, including future versions of this specification, shall use a different target namespace and no two distinct schemas shall have the same target namespace. 5 Reference Image For commonality across Macros operati

23、ng on images, a Reference Image is defined. Each Macro can specify the use of Reference Image depending on the associated image operation. For example, the Image Crop Macro is independent of pixel representation and a conversion to Reference Image is not required. Implementations need not implement

24、support for Reference Image exactly as specified herein, but are expected to produce output substantially equivalent to what would have been produced by the operations against the reference image. A reference image sequence shall consist of an ordered sequence of reference images, and, as illustrate

25、d in Figure 1, each reference image shall consist of a rectangular pixel array. SMPTE ST 2067-101:2018 Page 5 of 17 pages Figure 1. Reference Image The pixel at the intersection of column i and row j of the rectangular array is denoted P(i, j), with P(0,0) denoting the topmost and leftmost pixel. Ea

26、ch pixel P(i, j) shall consist of a 4-tuplet ( P1, P2, P3, P4 ) of IEEE 754 binary32 values, as specified in IEEE 754. When mapping common image formats to Reference Images, P1, P2 and P3 should each correspond to a component associated with a color encoding coordinate, and P4 to an alpha channel. 6

27、 Pixel Color Schemes For commonality across Macros operating on images, the following defines a framework for defining a pixel color scheme and representing a pixel color value in such a pixel color scheme. This specification does not specify concrete Pixel Color Schemes, which is left to other spec

28、ifications. A Pixel Color Scheme shall specify the following: a URI (as specified in IETF RFC 3986) that uniquely and globally identifies the Pixel Color Scheme; a mapping from images using the Pixel Color Scheme to the Reference Image specified in Section 5; a mapping from Reference Image specified

29、 in Section 5 to images using the Pixel Color Scheme; a structure representing a single pixel in the Pixel Color Scheme, in the form of a concrete XML Schema type definition derived by extension from ColorEncodingType, as specified in Table 1. 0,0 0,1 N-1,0 N-1, M-1 0, M-1 1,0SMPTE ST 2067-101:2018

30、Page 6 of 17 pages Table 1. ColorEncodingType Schema Definition A Macro definition can then use ColorEncodingType as the type of an element intended to represent a pixel color value in any Pixel Color Scheme. An instance of such a Macro can then use a concrete pixel color as the value of the element

31、. EXAMPLE: The XML schema definition of a Macro wishing to represent a pixel color value using the ColorEncodingType can be declared as: and a corresponding instance as: 1 255 255 where REC709-RGB-8-ColorEncodingType uniquely identifies the Pixel Color Scheme and the triplet 1 255 255 corresponds to

32、 a color in the Pixel Color Scheme. 7 Pixel Decoder Macro 7.1 Structure The Pixel Decoder Macro maps source pixels to Reference Image pixels (see Section 5). Note: The Pixel Decoder Macro does not perform conversion between different color encoding colorimetric systems. This functionality can be pro

33、vided by a specialized Macro. A Pixel Decoder Macro instance shall be a Macro instance with the type PixelDecoderType specified in Table 2. SMPTE ST 2067-101:2018 Page 7 of 17 pages Table 1. PixelDecoderType schema definition 7.1.1 InputImageSequence 7.1.1.1 Handle The Handle element shall be a Hand

34、le that shall uniquely identify the input image sequence. 7.1.1.2 Annotation The Annotation element shall be a free-form, human-readable annotation describing the input images. It is intended to be displayed to the user. 7.1.2 OutputReferenceImageSequence The Annotation element shall be a free-form,

35、 human-readable annotation describing the output reference image sequence. It is intended to be displayed to the user. 7.2 Processing Model Each image of the input image sequence shall be transformed, in order, into an output reference image with the same rectangular pixel array dimensions. Each pix

36、el of the input image shall be mapped into the corresponding pixel of the output reference image according to the Pixel Color Scheme (see Section 6) of the input image sequence. SMPTE ST 2067-101:2018 Page 8 of 17 pages 7.3 Output A Pixel Decoder Macro instance defines a single output corresponding

37、to the sequence of output reference images specified in Section 7.2. The Handle of the output in the context of the Macro instance shall be: images 8 Pixel Encoder Macro 8.1 Structure The Pixel Encoder Macro maps reference image pixels, as specified in Section 5, to encoded color pixels conforming t

38、o a scheme specified in the instance. Note: The Pixel Encoder Macro does not perform conversion between different color encoding colorimetric systems. This functionality can be provided by a specialized Macro. A Pixel Encoder Macro instance shall be a Macro instance with the type PixelEncoderType as

39、 specified in Table 3. Table 3. PixelEncoderType schema definition SMPTE ST 2067-101:2018 Page 9 of 17 pages 8.1.1 InputReferenceImageSequence 8.1.1.1 Handle The Handle element shall be a Handle as specified in SMPTE ST 2067-100 and shall reference a sequence of Reference Images. 8.1.1.2 Annotation

40、The Annotation element shall be a free-form, human-readable annotation describing the input reference images. It is intended to be displayed to the user. 8.1.2 OutputImageSequence 8.1.2.1 Annotation The Annotation element shall be a free-form, human-readable annotation describing the output image se

41、quence. It is intended to be displayed to the user. 8.1.2.2 ColorEncoding The ColorEncoding element is the color encoding of the output image pixels. It shall be the URI of a Pixel Color Scheme conforming to Section 6. 8.2 Processing Model Each image of the reference input image sequence shall be tr

42、ansformed, in order, into an output image with the same rectangular pixel array dimensions. Each pixel of the input reference image shall be mapped into the corresponding pixel of the output image according to the image pixel color scheme specified by the ColorEncoding element. 8.3 Output A Pixel En

43、coder Macro instance defines a single output corresponding to the sequence of output images specified in Section 8.2. The Handle of the output in the context of the Macro instance shall be: images 9 Image Crop Macro 9.1 Structure An Image Crop Macro instance shall be a Macro instance with the type I

44、mageCropMacroType as specified in Table 4. SMPTE ST 2067-101:2018 Page 10 of 17 pages Table 4. ImageCropMacroType schema definition SMPTE ST 2067-101:2018 Page 11 of 17 pages 9.2 ImageCropMacroType 9.2.1 InputImageSequence 9.2.1.1 Annotation The Annotation element shall be a free-form, human-readabl

45、e annotation describing the input images. It is intended to be displayed to the user. 9.2.1.2 Handle The Handle element shall be a Handle as specified in SMPTE ST 2067-100 that reference the sequence of input images from which output images are generated. 9.2.2 ReferenceRectangle The ReferenceRectan

46、gle element indicates a rectangle within the input image, as specified in Table 5. Table 5. MXF Rectangle Enum Values Value Meaning Stored Stored Rectangle as specified in SMPTE ST 377-1 Sampled Sampled Rectangle as specified in SMPTE ST 377-1 Display Display Rectangle as specified in SMPTE ST 377-1

47、 Active Active Area Rectangle as specified in SMPTE ST 2067-2 9.2.3 Inset The Inset element specifies insets to be applied to the rectangle specified by the ReferenceRectangle element. 9.2.4 OutputImageSequence 9.2.4.1 Annotation The Annotation element shall be a free-form, human-readable annotation

48、 describing the output images. It is intended to be displayed to the user. 9.2.4.2 Padding The Padding element specifies the padding to be applied to the pixels copied from the input image. 9.2.4.3 FillColor The FillColor element indicates the background color of the output image. It shall correspon

49、d to a Pixel Color Scheme conforming to Section 6. SMPTE ST 2067-101:2018 Page 12 of 17 pages 9.3 Processing Model Figure 2. Image Crop Macro As illustrated in Figure 2, each input image in the sequence referenced by the Handle element (Section 9.2.1.2) shall be transformed, in the order in which they appear, into a single output image according to the following: All pixels within the Source Rectangle of the input image shall be copied without modification to the Destination Rectangle within the output image. The Source Rectangle shall be the rectangle specified by

展开阅读全文
相关资源
猜你喜欢
相关搜索

当前位置:首页 > 标准规范 > 国际标准 > 其他

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1