1、 Copyright 2010 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue., White Plains, NY 10601 (914) 761-1100 Approved June 24, 2010 Table of Contents Page Foreword . 2 Intellectual Property 2 Introduction 2 1 Scope . 3 2 Conformance Notation . 3 3 Normative References . 3 4 Cons
2、trained Tag Image File Format 4 4.1 Channel Mapping . 4 4.2 Data Format . 4 4.3 Integer Pixel Representation 4 4.4 Image Orientation . 4 4.5 Image Structures 5 4.6 Byte Order 5 4.7 Image Subfile . 5 4.8 Compression 5 4.9 Encryption 5 5 File Naming and Numbering Convention . 5 6 Digital Leader . 6 7
3、Metadata 6 Annex A Constrained TIFF Tags (Normative). 7 Annex A.1 ICC Profile Tag . 9 Annex B Sample C Code for TIFF file creation (Informative) . 10 Annex C Examples of additional DCDM image information (Informative) 12 Annex D Example ICC profile (Informative) 14 Annex E Bibliography (Informative)
4、 16 Page 1 of 16 pages SMPTE RP 428-5:2010 SMPTE RECOMMENDED PRACTICE D-Cinema Distribution Master Mapping of Images into Constrained Tag Image File SMPTE RP 428-5:2010 Page 2 of 16 pages Foreword SMPTE (the Society of Motion Picture and Television Engineers) is an internationally-recognized standar
5、ds developing organization. Headquartered and incorporated in the United States of America, SMPTE has members in over 80 countries on six continents. SMPTEs Engineering Documents, including Standards, Recommended Practices, and Engineering Guidelines, are prepared by SMPTEs Technology Committees. Pa
6、rticipation in these Committees is open to all with a bona fide interest in their work. SMPTE cooperates closely with other standards-developing organizations, including ISO, IEC and ITU. SMPTE Engineering Documents are drafted in accordance with the rules given in Part XIII of its Administrative Pr
7、actices. SMPTE RP 428-5 was prepared by Technology Committee 21DC. Intellectual Property At the time of publication no notice had been received by SMPTE claiming patent rights essential to the implementation of this Standard. However, attention is drawn to the possibility that some of the elements o
8、f this document may be the subject of patent rights. SMPTE shall not be held responsible for identifying any or all such patent rights. Introduction This recommended practice is intended to facilitate the interchange of the uncompressed image files that make up a Digital Cinema Distribution Master (
9、DCDM) between post production facilities. It is expected to be used for finished trailers as well as full-length feature films. It also defines the input image file format that would be supported by JPEG 2000 encoding tools. It can also be used for film preview screenings or an archive of the featur
10、e film project. An appropriate file format for storing the DCDM Image files should be capable of containing a complete or partial Composition. These files should also be easily processed to create a D-Cinema Package (DCP) (including compatibility with compression, encryption and wrapping processes).
11、 The file naming and directory structure should support random frame reading and writing, allowing access to scenes or other specific frame sequences for frame inserts or frame replacements. The Tag Image File Format (TIFF) with 16 bits each per X, Y and Z channel, stored in Photometric R, G and B c
12、hannels was selected for several reasons: It is widely supported in professional and consumer software applications. Several open source libraries are available. It is supported by digital cinema packaging, color space conversion, and JPEG2000 encoding applications. In this application, the scope is
13、 narrowed to a constrained version of the TIFF file format to simplify implementation and interoperability testing. SMPTE RP 428-5:2010 Page 3 of 16 pages 1 Scope This recommended practice defines the file formats, file naming conventions, file sequences, and metadata for the interchange of uncompre
14、ssed picture files that make up the Digital Cinema Distribution Master (DCDM), utilizing a constrained version of the tag image file format (TIFF). 2 Conformance Notation Normative text is text that describes elements of the design that are indispensable or contains the conformance language keywords
15、: “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. Informative text does not contain any conformance keywords. All text in this document is, by d
16、efault, 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 followed in order to conform to the document and from which no deviation is permitte
17、d. 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 preferred but not necessarily required; or that (in the negative form) a certain possibili
18、ty 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 is not defined at this time, shall not be used, and may be defined in the future. The
19、 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 provisions (“shall“) and, if implemented, all recommended provisions (“should“) as des
20、cribed. 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 in this document shall be as follows: Normative prose shall be the authoritative defi
21、nition; Tables shall be next; followed by formal languages; then figures; and then any other language forms. 3 Normative References The following standards contain provisions which, through reference in this text, constitute provisions of this recommended practice. At the time of publication, the ed
22、itions indicated were valid. All standards are subject to revision, and parties to agreements based on this recommended practice are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below. SMPTE 428-1-2006, D-Cinema Distribution Master Image Ch
23、aracteristics SMPTE RP 428-6-2009, D-Cinema Distribution Master Digital Leader ISO 12639:2004(E) Graphic Technology Prepress Digital Data Exchange Tag Image File Format for Image Technology (TIFF/IT) ISO/IEC 646:1991, Information Technology ISO 7-Bit Coded Character Set for Information Interchange S
24、MPTE RP 428-5:2010 Page 4 of 16 pages 4 Constrained Tag Image File Format DCDM images shall be mapped as full color images in the Tag image file format, as defined in ISO 12639:2004(E), Subclause 7.1, Structure of TIFF/IT file, and as constrained in this recommended practice. Where ISO 12639:2004(E)
25、 defines a TIFF/IT file format for prepress graphic technology, this recommended practice defines a DCDM constrained tag image file format for digital cinema. Where requirements of this recommended practice and ISO 12639:2004(E) are in conflict, this recommended practice shall take precedence. 4.1 C
26、hannel Mapping The DCDM X, Y and Z color channel data, as defined in SMPTE 428-1, DCDM Image Characteristics, shall be mapped to Photometric R, G and B channels as follows. For reference, see Annex A, Tag 262, PhotometricInterpretation. X channel of DCDM to Photometric R channel, Y channel of DCDM t
27、o Photometric G channel, and Z channel of DCDM to Photometric B channel. The code values shall retain the gamma 2.6 encoding of the original X, Y and Z channels. 4.2 Data Format The pixel interleaved data format shall be used (“chunky” format). The X, Y and Z channels shall be stored as contiguous s
28、amples (XYZ). For reference, see Annex A, Tag 284, PlanarConfiguration. Note: The pixel packing data structure was chosen for compatibility with real-time disk playback systems used in color correction and quality control operations in post production. The XYZ interleaved code values shall be organi
29、zed in a single image plane as a rectangular array of pixels with ImageWidth columns (number of pixels per row) and ImageLength rows, in a single strip. For reference, see Annex A, Tag 256, ImageWidth, Tag 257, ImageLength, and Tag 278, RowsPerStrip. The code values shall utilize 16 bits for each sa
30、mple (color channel), with 3 color channels for each pixel. For reference, see Annex A, Tag 258, BitsPerSample, and Tag 277, SamplesPerPixel. 4.3 Integer Pixel Representation Each pixel in a compliant file shall be represented by three unsigned integer code values, each with a minimum of 12 bits. Th
31、e 12-bit code values shall be stored in the top 12 most significant bits of the 16 bits. The remaining four least significant bits should be set to 0111. DCDM constrained tag image files created in compliance with this recommended practice are intended to be used as input to a 12-bit compression pro
32、cess. The compression process will therefore truncate or round the 16-bit samples from the files. Users are cautioned to perform appropriate rounding when creating compliant files to avoid any introduction of image artifacts due to truncated LSBs. 4.4 Image Orientation The image orientation shall pl
33、ace the first pixel of a compliant file in the upper left corner of the image. The 0th row shall represent the visual top of the image, and the 0th column shall represent the visual left-hand side. For reference see Annex A, Tag 274, Orientation. SMPTE RP 428-5:2010 Page 5 of 16 pages 4.5 Image Stru
34、ctures The image pixel array contained in a compliant file shall conform to one of the Image Structures defined in SMPTE 428-1, DCDM Image Characteristics. 4.6 Byte Order The Byte Order used within a compliant file shall be from the most significant to the least significant, for both 16-bit and 32-b
35、it integers. This is called big-endian byte order. Bytes 0 1 of the image file header at the beginning of the file shall have the values “MM” or 4D4D.h. For reference, see ISO 12639:2004(E), Subclause 7.1.2, Header. 4.7 Image Subfile A compliant file shall convey only main image data in one image su
36、bfile, with one Image File Directory (IFD). For reference, see ISO 12639:2004(E), Subclause 7.1.3, Image subfiles. 4.8 Compression No compression shall be applied to the image files themselves. For reference, see Annex A, Tag 259, Compression. 4.9 Encryption No encryption shall be applied to the ima
37、ge files themselves. 5 File Naming and Numbering Convention Each image shall be contained in a separate image file. An image sequence shall comprise a directory containing a series of image files where the image files have like parameters. The file names shall be formed of only ISO 646 single byte c
38、haracters, constrained to digits (character values 48 through 57), upper and lower case letters (character values 65 through 90, and 97 through 122), the underscore “_“ (character value 95), the dash “-“ (character value 45), and the period or dot “.”(character value 46). The file name shall end wit
39、h the file name extension: “.tif” (delimited by the period character “.”). The file name extension shall be preceded by a frame number identifier. The frame number identifier may optionally be preceded by a string of characters as constrained in this section, delimited from the frame number identifi
40、er by another period character “.”. The file name shall not exceed 128 characters in length, including the frame number and file name extension. The frame number identifiers shall be in an ascending numbered sequence with no gaps in the sequence for a given image sequence. Leading zeros shall be use
41、d to maintain a constant number of digits. Post production reel names and abbreviations may be used. Any character strings used in the filename shall be constant for all image files intended for the same image sequence. The only characters that shall change from one file name to another within an im
42、age sequence shall be the digits that make up the frame number identifier. SMPTE RP 428-5:2010 Page 6 of 16 pages When sorted alphanumerically, all files in an image sequence shall be in the intended temporal display order. Example1: Your_Movie_R1_SCOPE.000192.tif Your_Movie_R1_SCOPE.000193.tif Exam
43、ple2: My_Movie_TRLR-J_FLAT.000000.tif My_Movie_TRLR-J_FLAT.000001.tif Example3: 086400.tif 086401.tif Example4: 172800.tif 172801.tif Note: From example 3, 086400 equals 01:00:00:00 in frames at 24 frames per second. Using one particular file naming method, this would correspond to the “picture star
44、t” frame in the head leader for reel 1. Likewise, frame number 086592, which equals 01:00:08:00 in frames at 24 frames per second, would correspond to the first frame of action (FFOA) in reel 1 after the head leader. From example 4, 172800 equals 02:00:00:00 in frames at 24 frames per second, which
45、could be for reel 2. 6 Digital Leader For synchronizing consistency with the digital audio files, each image file sequence that comprises a post production reel shall begin with a digital head leader that has a duration of eight seconds before the First Frame of Action. SMPTE RP 428-6, DCDM Digital
46、Leader, defines a digital leader that should be utilized. A post production reel is an image file sequence that may be made into a D-Cinema Track File. For example, with 24 frames per second content, 192 image files would be placed in the sequence before the First Frame of Action. Likewise, with 48
47、frames per second content, the count of frames in the digital leader would be 384. For more examples, with DCDM Additional Frame Rates of 25, 30, 50 or 60, the count of frames in the digital leader would be 200, 240, 400 or 480, respectively. 7 Metadata Each frame in the file sequence shall contain
48、accurate and complete metadata within the TIFF fields as defined in Annex A (Normative). Examples of additional information about the D-Cinema Distribution Master (DCDM) that may be carried in one or more separate XML files are shown in Annex C (Informative). SMPTE RP 428-5:2010 Page 7 of 16 pages A
49、nnex A Constrained TIFF Tags (Normative) This annex defines the TIFF tag numbers and fields that are utilized in the entries of the IFD (Image File Directory) of a compliant DCDM constrained tag image file. For reference, see ISO 12639:2004(E), Subclause 7.1.4, IFD (Image File Directory), and Subclause 7.1.5, IFD entry. All numeric values are expressed in decimal notation, unless otherwise indicated. A letter h is suffixed to indicate a hexadecimal value. Literal character strings are denoted
copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1