All these documents are to be used at your own risk, strictly voluntary, not to be used for implementing products, no warranty expressed or implied. These are provided for convenience only.
SMPTE Documents needed for SMPTE-DCP packages: https://cinepedia.com/references/
A presentation on the differences between Interop DCP and SMPTE DCP is available here.
DCP Current Practice:
If you want an editable version of these documents, please contact email@example.com and you can get a word/pages document.
ISDCF Document 1 - Digital Cinema Content Naming Convention
ISDCF maintains the recommendation for naming DCP files. The current version is posted on-line at http://isdcf.com/dcnc
ISDCF Document 3 - Hard Disc Drive formats
ISDCF – Distribution Device File System Recommendations
Current version: http://isdcf.com/papers/ISDCF-Doc3-Delivery-Recs.pdf
ISDCF Document 4 - Audio Channel Assignments
16‐Channel Audio Packaging Guide for both Interop-DCP and SMPTE-DCP. Interop DCP does not have a standardized way of sending multichannel packages. The attached documents describe a common way of transporting multi-channel and the labeling to be consistent with SMPTE-DCP packages.
Current version: http://isdcf.com/papers/ISDCF-Doc4-Audio-channel-recommendations.pdf
ISDCF Document 5 - Guideline formulations for SMPTE-KDMs
Actual DCI-compliant systems are now starting to appear in the field. Some KDM providers have been sending KDMs containing ContentAuthenticator to be used with Interop content. This will not work on a DCI-compliant system. This document describes formulations for successful KDMs.
Permalink-Current pdf version: http://isdcf.com/papers/ISDCF-Doc5-kdm-certs.pdf
ISDCF Document 7 - Language Codes
Latest pdf version: http://isdcf.com/papers/ISDCF-Doc7-DigitalCinemaLanguageCodes.pdf
ISDCF Document 12 - Ingest Behavior (a document under development)
NOT YET APPROVED. Under consideration only: http://isdcf.com/papers/ISDCF-Doc12-Recommended-Practice-for-Ingest-Behavior-DRAFT-20170322.pdf
OLD-ISDCF Document 6 - Composition Metadata Guidelines - Now in SMPTE and published. SMPTE members can go to
ST 429-16:2014 Additional Composition Metadata and Guidelines (http://dx.doi.org/10.5594/S9781614828327)
ISDCF Document 9 - Closed Caption Authoring Best Practices
Closed caption devices have some strange and unusual behavior - from limited number of display characters to limited number of lines to unique fonts. Captured here are some suggestions to maximize the quality of closed captions
Current pdf version: http://isdcf.com/papers/ISDCF-Doc9-Closed-Caption-Authoring-Best-Practices.pdf
ISDCF Document 10 - Subtitles and Captions in Digital Cinema
Subtitles and Captions in Digital Cinema. Digital cinema provides for subtitles and captions, both on the main screen and off. This paper provides a brief description of these capabilities.
ISDCF Document 2 - SMPTE-DCP compared to Interop-DCP Informational only
The Digital Cinema industry is moving from Interop-DCP to SMPTE-DCP, hopefully starting in April 2012. Posted here is the comparison between these two delivery packages.
Permalink-current pdf version: http://isdcf.com/papers/ISDCF-Doc2-DCP-TransitionReview.pdf
ISDCF Document 11 - How Loud is a Movie? – a New Measurement Procedure
Leq(m10)2.0 A procedure is introduced to measure the subjective loudness of an entire movie and to develop a suitable metric. Leq(m) has been used for over 15 years to measure and then control the level of trailers and commercials, both in the US and overseas. The method to be described takes a ten-minute rolling average of Leq(m) throughout an entire movie, and then integrates the values above a given threshold. The procedure is not intended to constrain the levels of movies, simply to come up with a metric to describe the subjective loudness. A suggested descriptive is Leq(m10). Reposted Accepted for publication and copyright SMPTE - reproduced by permission. Ioan Allen Author.
Current pdf version: http://isdcf.com/papers/ISDCF-Doc11-MovieLoudnessMeasurement20160315.pdf
Go http://www.dcimovies.com/specification/index.html for the document.
The Following are documents that are out of date and not approved and not being worked on at this time
DRAFT-ISDCF Document 8 - Theater Key Retrieval (a work in progress)
Tired of using EMail to send KDMs to theaters? Here is a very rough proposal for a TKR that uses open standards to deliver Keys. This is a WORKING DRAFT.
Current pdf version: http://isdcf.com/papers/ISDCF-Doc8-TheaterKeyRetrieval-TKR-v03.pdf
ISDCF - High Frame Rate (a work in progress)
A high frame rate movie was distributed in SMPTE-DCP at the end of 2012. To facilitate the interoperability of the release, here is a very drafty specifications for 48 FPS per eye distribution.
Permalink-current pdf version: ISDCF-HighFrameRate-DCP.pdf
Other Technical Background Documents that are out of date.
DCI Compliance Update
There are now many projector products that have passed the DCI compliance test plan. These are posted to the DCI website: http://www.dcimovies.com/compliance/
NIST/FIPS-140-2 Update (June 21, 2010 update)
There has been considerable conversation at ISDCF over the NIST update to FIPS-140. The question included the DCI-Specification, the Compliance Test Plan, and SMPTE documents referring to a soon-to-not-exist (or recently changed) standard. Posted at the NIST site are draft NIST publications (go HERE) and in particular are public comments (go HERE for all comments) of most interest are DCI comments that were submitted - go HERE for the DCI comments.
3D Screen Luminance Measurement (updated June 2010)
How to measure the screen brightness of a 3D screen came up in a discussion in the January 2010 time frame. A discussion thread has been underway with no conclusions, but some good input. Peter Wilson put the thread together into a .pdf document. It’s posted HERE.
Facility Identifiers (In Process)
Facility Identifiers provide the mechanism for a unique ID for a theatre location. Facility identifiers are required with the SMPTE 430-7 Facility List Message (FLM), an important message type in the automation of security key management. The entity that manages the identifier may be the theatre owner or designated representative. It is logical that the UUID could become the identifier of choice as it requires no registry. However, an additional problem is that there are multiple identifiers managed by multiple entities for the same location. Because of this, it"s useful to know whose identifier one is looking at. For this purpose, the proposal below outlines an identifier scheme presented to ISDCF. It is proposed that the scheme be formalized as a unique name type under the Uniform Resource Name (URN) standard naming scheme managed by the IETF.
Updated Link: http://mkpe.com/digital_cinema/isdcf/identifier/2010-11-11%20Cinema%20Facility%20Identifier.pdf
Key Delivery Message (KDM) Naming Convention (In Process)
KDMs arrive in theatres from many sources, typically by email. Theatre operators have a difficult time sorting and identifying the emails and files that are sent. The KDM Naming Convention is the recommended naming scheme for ZIP files containing KDMs, and for the KDM filename itself. It is based on the many of the name types used in the Digital Cinema Naming Convention (see below). This naming scheme is still evolving, so users should check back for updates. The KDM Naming Convention is described at kdmNamingConvention.com.
NIST Security Standards (Subject to change)
Digital cinema security, per the DCI specification, relies on a series of NIST standards that, due to their complexity and nature, are perpetually in amendment. NIST documents that affect digital cinema are listed below.
NIST Miscellaneous and Special Publications