X-Git-Url: https://git.carlh.net/gitweb/?p=dcpomatic.git;a=blobdiff_plain;f=doc%2Fmanual%2Fdcpomatic.xml;h=81321a83d4954e20918266c7145b7a13d107338e;hp=6b6ce83c2fa8f1ae91354491577342d1f7dd8a53;hb=b4ab9f4adc9dd10d0f1a33286d78821da580a4d1;hpb=41bab4e95911d3ae99081556db5fe1d29ac008b5
diff --git a/doc/manual/dcpomatic.xml b/doc/manual/dcpomatic.xml
index 6b6ce83c2..81321a83d 100644
--- a/doc/manual/dcpomatic.xml
+++ b/doc/manual/dcpomatic.xml
@@ -320,7 +320,20 @@ making the DCP.
Choose Make DCP from the
-Jobs menu. DCP-o-matic will encode your DCP.
+Jobs menu. Before encoding your DCP, DCP-o-matic
+will run a series of checks on your film to look for various conditions
+that might cause problems when playing back the DCP. If any potential
+problems are found, DCP-o-matic will show you a list of hints.
+Each hint describes the condition that was found and gives
+advice on how to resolve it. If hints are found and reported, you can
+either Make DCP anyway (without adjusting any
+settings), or Go back in order to make
+adjustments before encoding the DCP.
+
+
+
+If no hints were found (or you pressed Make DCP
+after hints were displayed), DCP-o-matic will encode your DCP.
This may take some time (many hours in some cases). While the job is
in progress, DCP-o-matic will update you on how it is getting on with
the progress bar in the bottom of its window, as shown in Copy as name and
the ISDCF name will be copied into the Name box.
You can then edit it as you wish. The DCP name should not matter (in
that it should not affect how the DCP ingests or plays) but
-projectionists will appreciate it if you use the standard naming
-scheme as it makes it easier to identify details of the content.
+projectionists will appreciate it if you use the
+standard naming scheme
+as it makes it easier to identify details of the content.
+
+
+
+If there is spoken language in your project's audio you can tick the
+Audio Language checkbox and then specify the language
+of that audio. This information will be used for the ISDCF name, written into
+the DCP cover sheet, and added as metadata to the audio MXF files in the DCP.
@@ -2375,7 +2396,6 @@ emailed to the appropriate cinema email addresses. Click
Creating KDMs using a DKDM
-
It can be inconvenient to need a whole DCP-o-matic project just to
@@ -2442,9 +2462,71 @@ a target certificate. You can get DCP-o-matic's target certificate by
opening Preferences and clicking Export
DCP decryption certificate... in the Keys
tab.
+
+
+
+
+
+Creating KDMs for a distributor
+
+
+Sometimes you have an encrypted DCP and you want to allow somebody else
+(for example, a distributor) to make KDMs for the DCP on your behalf.
+
+
+
+The normal way to do this is to send the distributor a KDM which they
+can use with their own KDM creation system. Such a KDM is often called
+a DKDM (the ‘D’ stands for Distribution).
+It is the same as a normal KDM except that it is made to work with another
+computer, rather than with a projection system.
+
+
+
+To make a DKDM for a distributor you will first need to ask them to send you
+a decryption certificate. This should be a small file, usually with the extension
+.pem.
+
+
+Once you have the certificate, you will need to add a ‘fake’ cinema
+and screen to the list in DCP-o-matic. This is because making a KDM for another
+computer uses the same process internally as making one for a projection system,
+it's just that DCP-o-matic does not have a nice way to present that.
+
+
+
+In either the KDM window in the main DCP-o-matic, or the KDM creator, first add
+a new cinema by clicking Add Cinema..., giving it a name
+(perhaps the name of the distributor).
+
+Then select this new cinema and click Add Screen... to open
+the screen dialog box, as shown in .
+
+
+
+ Adding a screen
+
+
+
+
+
+
+
+
+Here you can give any name (perhaps just ‘DKDM’). Then click Get from file...
+and choose the certificate file that the distributor gave you. Finally, click OK.
+
+
+
+Now you can create a KDM for this screen, and send it to the distributor. Using that KDM the distributor
+can then make KDMs for your DCP for anybody (and also, of course, decrypt the DCP if they wanted to).
+
+
+
+