Specifications

5-1

Using the DCP and Self KDM

When a DCP of a feature film is created, it is usually encrypted with the

decryption key stored in the KDMs. The decryption key in each KDM is

also encrypted, and it can be decrypted only with the private key of the

respective D-Cinema player for whom it was created. The conclusion of

this is that, once a DCP is created, it cannot be modified or checked for

flaws that may have occurred during the encoding and/or wrapping

process. The DCP together with a KDM and all other extra files are self-

contained, intended only for a specific usage in a defined period of time

on a particular device.

DVS’s solution to this problem is the self KDM of CLIPSTER that can be

created together with the other KDMs. It has to be generated with the

public key of a CLIPSTER DCI Mastering system (hardware accelerat-

ed). This system can afterwards be used to load the DCP. Although the

self KDM carries a validity same as the other KDMs, with CLIPSTER you

will be able to use the content nevertheless.

Once the DCP is loaded into CLIPSTER with the self KDM, you can, for

example, play out and check its content, create other KDMs (e.g. for

later releases) or modify it (e.g. exchange audio). Additional finalizing

processes will be performed only where alterations were made, i.e. the

DCP will not be generated again completely.

This section describes how to use a self KDM as well as a DCP once they

have been created. It will be explained, for example, how to configure

the creation of a self KDM, how to load a DCP with CLIPSTER and how

to use a DCP to create additional KDMs.

DCPs can also be created unencrypted, for example, for trailers

or advertisements. Then, of course, they do not require KDMs

or a self KDM. Unencrypted DCPs as well can be used as de-

scribed in this chapter, but will not prompt for a self KDM.