1 <?xml version="1.0" encoding="utf-8"?>
3 <!ENTITY % sgml.features "IGNORE">
4 <!ENTITY % xml.features "INCLUDE">
5 <!ENTITY % dbcent PUBLIC "-//OASIS//ENTITIES DocBook Character Entities V4.5//EN"
6 "/usr/share/xml/docbook/schema/dtd/4.5/dbcentx.mod">
8 <!ENTITY % extensions SYSTEM "extensions.ent">
11 <book xmlns="http://docbook.org/ns/docbook" xmlns:mml="http://www.w3.org/1998/Math/MathML" version="5.0" xml:lang="en">
14 <title>DCP-o-matic users' manual</title>
15 <author><firstname>Carl</firstname><surname>Hetherington</surname></author>
18 <chapter xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en">
19 <title>Introduction</title>
22 Hello, and welcome to DCP-o-matic!
25 <!-- ============================================================== -->
27 <title>What is DCP-o-matic?</title>
30 DCP-o-matic is a program to generate <ulink
31 url="http://en.wikipedia.org/wiki/Digital_Cinema_Package">Digital
32 Cinema Packages</ulink> (DCPs) from almost any video, audio and/or
33 subtitle source files. The resulting DCPs will play on modern digital
40 <!-- ============================================================== -->
42 <title>Licence</title>
45 DCP-o-matic is free and open-source and is licensed under the <ulink
46 url="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html">GNU
53 <!-- ============================================================== -->
55 <title>Acknowledgements</title>
58 This manual uses icons from the <ulink url="http://tango.freedesktop.org/">Tango Desktop Project</ulink>, with thanks.
63 <!-- ============================================================== -->
65 <title>This manual</title>
68 This manual presents bits of DCP-o-matic's user interface (such as menu items or buttons) <guilabel>like this</guilabel>.
72 Notes of an advanced nature are presented like this. Ignore them unless you want to know the gory details.
79 <!-- ============================================================== -->
80 <chapter xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en">
81 <title>Installation</title>
84 <!-- ============================================================== -->
86 <title>Windows</title>
89 To install DCP-o-matic on Windows, download the installer from
90 <ulink url="http://dcpomatic.com/">http://dcpomatic.com/</ulink>
91 and double-click it. Click through the installer wizard, and
92 DCP-o-matic will be installed onto your machine.
96 If you are using a 32-bit version of Windows, you will need the 32-bit
97 installer. For 64-bit Windows, either installer will work, but I
98 suggest you used the 64-bit version as it will allow DCP-o-matic to
99 use more memory. You may find that DCP-o-matic crashes if you run
100 many parallel encoding threads (more than 4) on the 32-bit
107 <!-- ============================================================== -->
109 <title>Mac OS X</title>
112 DCP-o-matic will run on Mac OS X version 10.6 (Snow Leopard) and
113 higher. To install it, download the <code>.dmg</code> from <ulink
114 url="http://dcpomatic.com/">http://dcpomatic.com/</ulink> and double
115 click to open it. Then drag the DCP-o-matics icon to your
116 <guilabel>Applications</guilabel> folder or wherever else you would
121 You do not have to install all the applications, but you must always
122 install <code>DCP-o-matic 2.app</code> as the other applications
128 <!-- ============================================================== -->
130 <title>Debian or Ubuntu Linux</title>
133 You can install DCP-o-matic on:
137 <listitem>Debian 7 (‘wheezy’)</listitem>
138 <listitem>Debian 8 (‘jessie’)</listitem>
139 <listitem>Debian unstable (‘sid’)</listitem>
140 <listitem>Ubuntu 12.04 (‘Precise Pangolin’)</listitem>
141 <listitem>Ubuntu 14.04 (‘Trusty Tahr’)</listitem>
142 <listitem>Ubuntu 15.10 (‘Wily Werewolf’)</listitem>
143 <listitem>Ubuntu 16.04 (‘Xenial Xerus’)</listitem>
147 using <code>.deb</code> packages: download the appropriate package
148 from <ulink url="http://dcpomatic.com/">http://dcpomatic.com/</ulink>
149 and double-click it. Debian or Ubuntu will install the necessary bits and
150 pieces and set DCP-o-matic up for you.
153 <!-- ============================================================== -->
156 <!-- ============================================================== -->
158 <title>Fedora Linux</title>
160 <para>There are <code>.rpm</code> packages for Fedora 22 and 23 on
161 <ulink url="http://dcpomatic.com/">http://dcpomatic.com/</ulink>
164 <!-- ============================================================== -->
167 <!-- ============================================================== -->
169 <title>Centos Linux</title>
170 <para>There are <code>.rpm</code> packages for Centos 5, 6.5 and 7 on
171 <ulink url="http://dcpomatic.com/">http://dcpomatic.com/</ulink>
174 <!-- ============================================================== -->
177 <!-- ============================================================== -->
179 <title>Arch Linux</title>
181 Packages for Arch Linux are available from <ulink
182 url="https://aur.archlinux.org/packages/dcpomatic/">https://aur.archlinux.org/packages/dcpomatic/</ulink>,
183 thanks to Stefan Karner.
188 <!-- ============================================================== -->
190 <title>Other Linux distributions</title>
193 Installation on other Linux systems (for which no packages are
194 available) is quite hard as it must be compiled from source. If you
195 can't download packages for your distribution, do let me know by
196 <ulink url="mailto:carl@dcpomatic.com">email</ulink> and I will look
197 into providing packages on the website.
201 The following dependencies are required:
203 <listitem><ulink url="http://ffmpeg.org/">FFmpeg</ulink></listitem>
204 <listitem><ulink url="http://www.mega-nerd.com/libsndfile/">libsndfile</ulink></listitem>
205 <listitem><ulink url="http://www.mega-nerd.com/SRC/">libsamplerate</ulink></listitem>
206 <listitem><ulink url="http://www.openssl.org/">OpenSSL</ulink></listitem>
207 <listitem><ulink url="http://www.openjpeg.org/">libopenjpeg</ulink></listitem>
208 <listitem><ulink url="http://www.imagemagick.org/script/index.php">ImageMagick</ulink></listitem>
209 <listitem><ulink url="http://www.boost.org/">Boost</ulink></listitem>
210 <listitem><ulink url="http://www.libssh.org/">libssh</ulink></listitem>
211 <listitem><ulink url="http://www.gtk.org/">GTK (on Linux)</ulink></listitem>
212 <listitem><ulink url="http://www.wxwidgets.org/">wxWidgets</ulink></listitem>
213 <listitem><ulink url="http://libxmlplusplus.sourceforge.net/">libxml++</ulink></listitem>
214 <listitem><ulink url="http://www.aleksey.com/xmlsec/">xmlsec</ulink></listitem>
215 <listitem><ulink url="http://curl.haxx.se/">curl</ulink></listitem>
216 <listitem><ulink url="http://www.nih.at/libzip/">libzip</ulink></listitem>
217 <listitem><ulink url="http://carlh.net/libdcp/">libdcp</ulink></listitem>
218 <listitem><ulink url="http://carlh.net/libsub/">libsub</ulink></listitem>
219 <listitem><ulink url="http://carlh.net/libcxml/">libcxml</ulink></listitem>
220 <listitem><ulink url="http://site.icu-project.org">libicu</ulink></listitem>
225 Once you have installed the development packages for the dependencies,
226 download the source code from <ulink
227 url="http://dcpomatic.com/">http://dcpomatic.com/</ulink>,
228 unpack it and run the following commands from inside the source
239 With any luck, this will build and install DCP-o-matic on your system. To run it, enter:
254 <!-- ============================================================== -->
255 <chapter xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en">
256 <title>Creating a DCP from a video</title>
259 In this chapter we will see how to create a DCP from a video file using
260 DCP-o-matic. We will gloss over the details and look at the basics.
264 <title>Creating a new film</title>
267 Let's make a very simple DCP to see how DCP-o-matic works. First, we
268 need some content. Download the low-resolution trailer for the open
269 movie <ulink url="http://sintel.org/">Sintel</ulink> from <ulink
270 url="http://ftp.nluug.nl/ftp/graphics/blender/apricot/trailer/Sintel_Trailer1.480p.DivX_Plus_HD.mkv">their
271 website</ulink>. Generally one would want to use the
272 highest-resolution material available, but for this test we will use
273 the low-resolution version to save everyone's bandwidth bills.
277 Now, start DCP-o-matic and its window will open. First, we will
278 create a new ‘film’. A ‘film’ is how DCP-o-matic refers to
279 some pieces of content, along with some settings, which we will make into
280 a DCP. DCP-o-matic stores its data in a folder on your disk while it
281 creates the DCP. You can create a new film by selecting
282 <guilabel>New</guilabel> from the <guilabel>File</guilabel> menu, as
283 shown in <xref linkend="fig-file-new"/>.
286 <figure id="fig-file-new">
287 <title>Creating a new film</title>
290 <imagedata fileref="screenshots/file-new&scs;"/>
296 This will open a dialogue box for the new film, as shown in <xref
297 linkend="fig-video-new-film"/>.
300 <figure id="fig-video-new-film">
301 <title>Dialogue box for creating a new film</title>
304 <imagedata fileref="screenshots/video-new-film&scs;"/>
310 In this dialogue box you can choose a name for the film. This will be
311 used to name the folder to store its data in, and also as the initial
312 name for the DCP itself. You can also choose whereabouts you want to create
313 the film. In the example from the figure, DCP-o-matic will create a
314 folder called ‘DCP Test’ inside my home folder (carl) into which it
315 will write its working files.
321 <!-- ============================================================== -->
323 <title>Adding content</title>
326 The next step is to add the content that you want to use. DCP-o-matic
327 can make DCPs from multiple pieces of content, but in this simple
328 example we will just use a single piece. Click the <guilabel>Add
329 file(s)...</guilabel> button, as shown in <xref
330 linkend="fig-add-file"/>, and a file chooser will open for you to
331 select the content file to use, as shown in <xref
332 linkend="fig-video-select-content-file"/>.
335 <figure id="fig-add-file">
336 <title>Adding content files</title>
339 <imagedata fileref="screenshots/add-file&scs;"/>
344 <figure id="fig-video-select-content-file">
345 <title>Selecting a video content file</title>
348 <imagedata fileref="screenshots/video-select-content-file&scs;"/>
354 Select your content file and click <guilabel>Open</guilabel>. In this
355 case we are using the Sintel trailer that we downloaded earlier.
359 When you do this, DCP-o-matic will take a look at your file. After a
360 short while (when the progress bar at the bottom right of the window
361 has finished), you can look through your content using the slider to
362 the right of the window, as shown in <xref linkend="fig-examine-content"/>.
365 <figure id="fig-examine-content">
366 <title>Examining the content</title>
369 <imagedata fileref="screenshots/examine-content&scs;"/>
375 Dragging the slider will move through your video. You can also click
376 the <guilabel>Play</guilabel> button to play the content back. <emphasis>Note
377 that there will be no sound</emphasis>, and playback might not be entirely
378 accurate (it may be slightly slower or faster than it should be, for
379 example). This player is really only intended for brief inspection of
380 content; if you need to check it more thoroughly, use another player
382 url="http://projects.gnome.org/totem/index.html">Totem</ulink>, <ulink
383 url="http://www.mplayerhq.hu/design7/news.html">mplayer</ulink> or
384 <ulink url="http://www.videolan.org/vlc/index.html">VLC</ulink>.
392 <!-- ============================================================== -->
394 <title>Making the DCP</title>
396 <para>In most cases, some adjustments would be made to DCP-o-matic's
397 settings once the content has been added. For our simple test,
398 however, the default values will suffice, so we can go straight onto
399 making the DCP.</para>
402 Choose <guilabel>Make DCP</guilabel> from the
403 <guilabel>Jobs</guilabel> menu. DCP-o-matic will encode your DCP.
404 This may take some time (many hours in some cases). While the job is
405 in progress, DCP-o-matic will update you on how it is getting on with
406 the progress bar in the bottom of its window, as shown in <xref
407 linkend="fig-making-dcp"/>.
410 <figure id="fig-making-dcp">
411 <title>Making the DCP</title>
414 <imagedata scale="50" fileref="screenshots/making-dcp&scs;"/>
420 When it has finished, the DCP will end up on your disk inside the
421 film's folder. You can then copy this to a projector via a USB
422 stick, hard-drive or network connection. See <xref
423 linkend="ch-files"/> for details about the files that DCP-o-matic creates.
427 Alternatively, if you have a projector or Theatre Management System
428 (TMS) that is accessible via SCP or FTP across your network, you can upload
429 the content directly from DCP-o-matic. See the <xref
430 linkend="sec-prefs-tms" endterm="sec-prefs-tms-short"/> in <xref linkend="sec-prefs-tms"/>.
437 <!-- ============================================================== -->
438 <chapter xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en">
439 <title>Creating a DCP from a still image</title>
442 DCP-o-matic can also be used to create DCPs of one or more still images, perhaps
443 for an advertisement or an on-screen announcement. This chapter shows you
448 As with DCPs made from video files, the first step is to create a new
449 ‘Film’; select <guilabel>New</guilabel> from the
450 <guilabel>File</guilabel> menu and the new film dialogue will open as
451 shown in <xref linkend="fig-still-new-film"/>.
454 <figure id="fig-still-new-film">
455 <title>Dialogue box for creating a new film</title>
458 <imagedata fileref="screenshots/still-new-film&scs;"/>
464 Enter a name and click <guilabel>OK</guilabel>. Now we need to add
465 the content. As before, click <guilabel>Add file(s)...</guilabel>.
466 For our example, we will add a single image file, as shown in <xref
467 linkend="fig-still-select-content-file"/>.
470 <figure id="fig-still-select-content-file">
471 <title>Selecting a still content file</title>
474 <imagedata fileref="screenshots/still-select-content-file&scs;"/>
480 Most of the default settings will be fine for a simple test. The one
481 thing that you might wish to change is the length of the still.
482 Select the <guilabel>Timing</guilabel> tab and you will see a
483 <guilabel>Play length</guilabel> setting, as shown in <xref
484 linkend="fig-timing-tab"/>.
487 <figure id="fig-timing-tab">
488 <title>The timing tab</title>
491 <imagedata fileref="screenshots/timing-tab&scs;"/>
497 This length is a ‘timecode’: it consists of four numbers.
498 The first is hours, the second minutes, the third seconds, and the
499 fourth frames. Enter the duration that you want and then click <guilabel>Set</guilabel>.
503 Finally, as with video, you can choose <guilabel>Make DCP</guilabel>
504 from the <guilabel>Jobs</guilabel> menu to create your DCP. This will
505 be much quicker than creating a DCP from a video file, as DCP-o-matic only needs
506 to encode a single frame which it can then repeat.
512 <!-- ============================================================== -->
513 <chapter xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en">
514 <title>Manipulating existing DCPs</title>
517 Frequently DCP-o-matic is used to take content in formats such as MP4
518 and convert it to JPEG2000 for a DCP. It can also be used
519 to take existing DCPs and modify them in various ways.
523 <title>Importing a DCP into DCP-o-matic</title>
526 If you want to do something to an existing DCP the first step is to
527 import it. Click <guilabel>Add folder...</guilabel> and select your
528 DCP's folder. It will be added to the DCP-o-matic project. If the
529 DCP is unencrypted you can preview it in the normal way, though
530 playback will be very slow as decoding of DCPs is almost as
531 computationally intensive as encoding them.
535 If your DCP is a Version File (VF), in other words it refers to
536 another DCP's assets, you should import it as follows:
540 <listitem>Use <guilabel>Add folder...</guilabel> to import the VF DCP.
541 The VF DCP will be added to the content list and marked “NEEDS
542 OV”.</listitem>
543 <listitem>Right-click on the VF DCP in the content list and choose <guilabel>Add OV...</guilabel> from the menu.</listitem>
544 <listitem>Choose the folder that contains the OV DCP. The VF will now be playable as normal.</listitem>
551 <title>Decrypting encrypted DCPs</title>
554 DCPs can be encrypted (see <xref linkend="ch-encryption"/> for
555 details). If you import an encrypted DCP you will need a key, in the
556 form of a Key Delivery Message (KDM), to decrypt it.
560 KDMs must be prepared by the organisation which created the DCP. They
561 contain the keys to decrypt the DCP wrapped up in such a way that only
562 the intended recipient can read them. You will need to provide the
563 organisation with a certificate which identifies your copy of
564 DCP-o-matic and allows them to create a KDM for you.
568 To get DCP-o-matic's decryption certificate, open the Preferences
569 dialogue (see <xref linkend="ch-preferences"/>) and go to the
570 <guilabel>Keys</guilabel> tab. Click the <guilabel>Export DCP
571 decryption certificate...</guilabel> button at the bottom of this tab
572 and save the certificate. Send this certificate to the DCP creators
573 and they can create a KDM to allow DCP-o-matic to decrypt their DCP.
577 Once you have your KDM, right-click the DCP's name in DCP-o-matic and
578 choose <guilabel>Add KDM...</guilabel>. Specify your KDM and (all
579 being well) the DCP will be decrypted and become available for preview.
586 <title>Making a DCP from a DCP</title>
589 In many ways, using DCPs as <emphasis>content</emphasis> in
590 DCP-o-matic is the same as using any other content. There are a few
591 things to note, though.
596 <title>Re-use of existing data</title>
599 Where possible DCP-o-matic will re-use existing JPEG2000-compressed
600 data from DCP content without modification. This has the advantage
601 that creation of the new DCP will be quick, as the time-consuming
602 JPEG2000 encoding is not necessary.
606 DCP-o-matic can do this if you <emphasis>avoid</emphasis> changes to
607 the following content settings:
611 <listitem>Crop</listitem>
612 <listitem>Scaling</listitem>
613 <listitem>Subtitle burn-in</listitem>
614 <listitem>Fades</listitem>
615 <listitem>Colour conversion</listitem>
619 If you do change any of these settings on a piece of DCP content
620 DCP-o-matic will decode and then re-encode the JPEG2000 data.
627 <title>Making overlay files</title>
630 With its default settings, DCP-o-matic will take any data from DCP
631 content and copy it into the DCP that it creates. See <xref linkend="fig-dcp-copy"/>.
634 <figure id="fig-dcp-copy">
635 <title>Creating a new DCP by copying an existing one</title>
636 <mediaobject><imageobject><imagedata scale="100" fileref="diagrams/dcp-copy&dia;"/></imageobject></mediaobject>
640 This can be inefficient in some cases. Consider, for example, a film
641 which has ten different translations for which the subtitles are
642 different but video and audio are the same. If the video and audio
643 content takes up, say, 100Gb this means that the set of DCPs for every
644 translation would be about 1Tb with a lot of duplicated data.
648 The DCP format has a solution to this problem. One DCP can refer to
649 the ‘assets’ (picture, sound or subtitle) of another DCP.
650 For our translation example this means that we could have a
651 ‘base’ DCP (often called the OV or Original Version)
652 containing video, audio and one set of subtitles and then any number
653 of overlay DCPs (often called VF or Version Files) which refer to the
654 base version and replace the original subtitles with their own. <xref
655 linkend="fig-dcp-refer"/> shows this principle for one of our
656 translations. The DCP that we make refers to the original content
657 DCP's video and audio rather than containing a copy.
660 <figure id="fig-dcp-refer">
661 <title>Creating a new DCP by referring to an existing one</title>
662 <mediaobject><imageobject><imagedata scale="100" fileref="diagrams/dcp-refer&dia;"/></imageobject></mediaobject>
666 To play back the subtitled DCP the projectionist ingests both the base
667 (OV) DCP and the overlay (VF) DCP, then plays the VF one.
671 To make a DCP like this:
675 <listitem>Import your ‘Content DCP’ to a DCP-o-matic project.</listitem>
676 <listitem>Add whatever replacement you want in your new DCP (replacement subtitles or audio files, for example).</listitem>
677 <listitem>Select the DCP in the content list</listitem>
678 <listitem>Tick the <guilabel>Refer to existing DCP</guilabel> checkbox
679 in the tabs for the parts of the DCP that you want to refer to in your
680 new DCP. For example, to refer to the Content DCP's video and audio you would select the <guilabel>Video</guilabel> tab, click <guilabel>Refer to existing DCP</guilabel> then select the <guilabel>Audio</guilabel> tab and do the same.</listitem>
681 <listitem>Do <guilabel>Make DCP</guilabel> as usual and your VF DCP will be created.</listitem>
691 <!-- ============================================================== -->
694 <!-- ============================================================== -->
695 <chapter xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en">
696 <title>Content settings</title>
699 The previous chapters showed DCP generation using the default
700 settings. DCP-o-matic offers a range of features to adjust the
701 content that goes into your DCP, and this chapter describes those
706 <title>Adding and removing content</title>
709 At the top of the <guilabel>Content</guilabel> tab is a list of the
710 content that will go into our DCP. There can be as many pieces of
711 content as you like, and they can be of the following types:
715 <listitem>Movie — a file containing some video, probably some
716 audio and possibly some embedded subtitles; for example, a MOV, MP4 or VOB.
719 <listitem>Sound — a file containing one or more channels of
720 audio; for example, a WAV or AIFF file.
723 <listitem>Still image — a file containing a single still image; for
724 example, a JPEG, PNG or TIFF file.
727 <listitem>Moving image — a directory containing many still
728 images which should be treated as the frames of a video.
731 <listitem>Subtitle — a file containing subtitle which will be
732 superimposed on the image of the DCP. These can be
733 <guilabel>.srt</guilabel>, <guilabel>.ssa</guilabel> or <guilabel>.xml</guilabel>
736 <listitem>DCP — an existing DCP.</listitem>
740 To add one or more movie, sound, still-image or subtitle files, select
741 <guilabel>Add file(s)...</guilabel> and choose them from the selector.
745 To add a directory (folder) of images or a DCP, choose <guilabel>Add
746 folder...</guilabel> and choose the directory from the selector. If
747 you select a folder of images DCP-o-matic will open a small dialogue
748 box where you can enter the frame rate that the image sequence should
753 You can remove a piece of content by clicking on its name and then
754 clicking the <guilabel>Remove</guilabel> button.
759 <!-- ============================================================== -->
761 <title>Adding existing DCPs</title>
763 <para>Adding existing DCPs to a DCP-o-matic film is a little different
764 to adding other types of content. Most content has to be converted to
765 JPEG2000, the compression scheme used by DCPs, which is a very
766 time-consuming process. Existing DCPs are already in JPEG2000 format
767 so do not require conversion. This means that, provided no settings
768 such as crop are used on the DCP content, picture and sound data will
769 be passed from existing to new DCP unaltered.
772 <para>Encrypted DCPs that are added as content will require a KDM
773 targeted at DCP-o-matic so that DCP-o-matic can decrypt them. You
774 should ask the creator of the imported DCP to provide a KDM for
775 DCP-o-matic's decryption certificate, which can be obtained by
776 clicking <guilabel>Export DCP decryption certificate...</guilabel>
777 from the <guilabel>Keys</guilabel> tab of the
778 <guilabel>Preferences</guilabel> dialog (see <xref
779 linkend="sec-prefs-keys"/>).
784 <!-- ============================================================== -->
786 <title>Content Properties</title>
789 Below the content list are the controls to set content properties. To
790 adjust the properties for a piece of content, click its name in the
791 content list. The content property controls will then become active
792 for that piece of content.
796 If you want to change the properties for multiple pieces of content at
797 the same time, select the content in the list by clicking the first
798 piece then clicking the other pieces with <keycap>shift</keycap> key
799 held down. Note that not all settings can be changed in this way.
803 The content properties are split up into four sections:
804 <guilabel>Video</guilabel>, <guilabel>Audio</guilabel>,
805 <guilabel>Subtitles</guilabel> and <guilabel>Timing</guilabel>. Not
806 all of these sections will be active for all content types. The controls
807 in each section are described below.
813 <!-- ============================================================== -->
818 The <guilabel>Video</guilabel> tab controls properties of the image, as shown in <xref linkend="fig-video-tab"/>.
821 <figure id="fig-video-tab">
822 <title>Video settings tab</title>
825 <imagedata fileref="screenshots/video-tab&scs;"/>
831 <!-- ============================================================== -->
833 <title>Image type</title>
836 The first option on this tab is the ‘type’ of the video.
837 This specifies how DCP-o-matic should interpret the video's image.
838 <guilabel>2D</guilabel> is the default; this just takes the video
839 image as a standard 2D frame. The <guilabel>3D
840 left/right</guilabel> option tells DCP-o-matic to interpret the frame as a
841 left-right pair, as shown in <xref linkend="fig-3d-left-right"/>.
844 <figure id="fig-3d-left-right">
845 <title>3D left/right image type</title>
848 <imagedata scale="100" fileref="diagrams/3d-left-right&dia;"/>
854 Alternatively the <guilabel>3D top/bottom</guilabel> option tells
855 DCP-o-matic to see the frame as a top-bottom pair, as shown in <xref
856 linkend="fig-3d-top-bottom"/>.
859 <figure id="fig-3d-top-bottom">
860 <title>3D top/bottom image type</title>
863 <imagedata scale="100" fileref="diagrams/3d-top-bottom&dia;"/>
869 Another option is <guilabel>3D alternate</guilabel> which takes the
870 first frame of the content as for the left eye, the second for the
871 right eye, the third for the left, and so on. Finally, you can
872 specify <guilabel>3D left only</guilabel> or <guilabel>3D right
873 only</guilabel> if this content contains only the the left or right
874 eye images. This is useful when you have the left and right eye image
875 sets in different files; you can specify one content as <guilabel>3D
876 left only</guilabel> and another as <guilabel>3D right only</guilabel>
877 and DCP-o-matic will pick up the appropriate frames from each.
883 <!-- ============================================================== -->
885 <title>Filtering</title>
888 The ‘filters’ settings allow you to apply various video
889 filters to the image. These may be useful to try to improve
890 poor-quality sources like DVDs. You can set up the filters by clicking the
891 <guilabel>Edit</guilabel> button next to the filters entry in the
892 setup area of the DCP-o-matic window; this opens the filters selector
893 as shown in <xref linkend="fig-filters"/>.
896 <figure id="fig-filters">
897 <title>Filters selector</title>
900 <imagedata fileref="screenshots/filters&scs;"/>
906 After changing the filters setup, you will need to regenerate the DCP
907 to see the effect on the cinema screen. The preview in DCP-o-matic
908 will update itself whenever filters are changed, though of course this
909 image is much smaller and of lower resolution than a projected image!
915 <!-- ============================================================== -->
917 <title>Colour conversion</title>
920 The <guilabel>Colour conversion</guilabel> setting specifies what
921 colour transforms and gamma correction DCP-o-matic will use when
922 converting the selected content into the XYZ colourspace for the DCP.
926 The easiest way to select the required conversion is to choose one of
927 DCP-o-matic's presets. DCP-o-matic knows how to convert from four
928 common colourspaces: sRGB, Rec. 601, Rec. 709 and P3. If you do not
929 know which preset you should use, refer to the suggestions in <xref
930 linkend="tab-colour-conversion"/>.
933 <table id="tab-colour-conversion">
934 <title>Suggested colour conversion settings</title>
935 <tgroup cols='2' align='left' colsep='1' rowsep='1'>
936 <colspec colwidth='1*'/>
937 <colspec colwidth='5*'/>
940 <entry>sRGB</entry><entry>Still images in RGB, e.g. photographs</entry>.
943 <entry>Rec. 601</entry><entry>Standard-definition content (fewer than about 1000 pixels across) including DVD rips.</entry>
946 <entry>Rec. 709</entry><entry>High-definition content including Blu-Ray rips.</entry>
949 <entry>P3</entry><entry>Content explicitly graded to P3.</entry>
956 For other required colour conversions, and if you know what you are
957 doing, you can choose <guilabel>Custom</guilabel> which will open the full
958 colour conversion editing dialogue box:
961 <figure id="fig-colour-conversion">
962 <title>Dialogue box for custom colour conversion</title>
965 <imagedata fileref="screenshots/colour-conversion&scs;"/>
971 Alternatively, choose <guilabel>None</guilabel> if your source files
972 are already in the XYZ colour space and require no conversion.
976 DCP-o-matic's colour conversion processes are discussed in much more
977 detail in a separate document <ulink
978 url="http://dcpomatic.com/manual/colour.pdf">colour.pdf</ulink>.
983 <!-- ============================================================== -->
985 <title>Other settings</title>
988 The <guilabel>crop</guilabel> settings can be used to crop your content,
989 which can be used to remove black borders from round the edges of DVD
990 images, for example. The specified number of pixels will be trimmed
991 from each edge, and the content image in the right of the window will
992 be updated to show the effect of the crop.
996 The <guilabel>fade in</guilabel> and <guilabel>fade out</guilabel>
997 settings can be used to apply linear fades into and out of a piece of
998 content. Specify the time for each, clicking <guilabel>Set</guilabel>
999 after making any changes.
1003 The <guilabel>Scale to</guilabel> option governs the shape that
1004 DCP-o-matic will scale the content's image into. Select the aspect
1005 ratio that your content should be presented in.
1010 <!-- ============================================================== -->
1012 <title>Video description</title>
1015 At the bottom of the video tab is a short description of what will
1016 happen to your video with the current settings. In the example of
1017 <xref linkend="fig-video-tab"/>, DCP-o-matic is telling you that the
1018 video file is 1920x1080 pixels and it has square pixels (a pixel
1019 aspect ratio of 1.00) hence its display aspect ratio is 1.78:1. Since
1020 the controls specify ‘16.9’ for the ratio, DCP-o-matic
1021 does not scale the image but pads it to the DCP's container ratio of
1022 1.85:1. For a 2K DCP this is 1998x1080 pixels.
1026 This description also gives the frame rate of the content and what
1027 will happen to it when it is played at the DCP's frame rate. See
1028 <xref linkend="ch-frame-rates"/> for details of DCP-o-matic's
1029 frame-rate conversion.
1037 <!-- ============================================================== -->
1039 <title>Audio</title>
1042 The <guilabel>Audio</guilabel> tab controls properties of the image, as shown in <xref linkend="fig-audio-tab"/>.
1045 <figure id="fig-audio-tab">
1046 <title>Audio settings tab</title>
1049 <imagedata fileref="screenshots/audio-tab&scs;"/>
1055 <!-- ============================================================== -->
1057 <title>The audio map</title>
1060 The section at the bottom of the audio tab is the ‘audio
1061 map’. This governs how sound from the content will be arranged
1066 Down the left-hand side of the map is the list of audio channels in
1067 the currently-selected piece of content. These are labelled with two
1068 numbers; the first is the stream index within the content and the
1069 second is the channel number within that stream. Some content will
1070 have different streams for different languages or audio mixes. Along
1071 the top is each channel in the DCP. A green box means that the
1072 corresponding content channel will be copied into the corresponding
1077 When content channels are copied into DCP channels they can be done
1078 with variable gain. If, for example, you want to copy a channel
1079 as-is, you can set a gain of 0dB. Alternatively, if you want to mix
1080 two channels into one, you may want to use a gain of -6dB on each one
1081 to prevent clipping when the two channels are added.
1085 The green boxes of the audio mapping view tell you (very roughly) how
1086 much gain is applied to each channel. A full-height box means 0dB
1087 (i.e. unity) gain. Any less height indicates lower gain.
1091 To map one channel to another with 0dB gain, click in the empty box
1092 and it will turn green to reflect the mapping. A second click will
1093 turn the mapping back off. To set some other gain, right-click on the
1094 box to open the gain menu. This allows you to set
1095 <guilabel>Off</guilabel> (no mapping or negative infinity gain),
1096 <guilabel>Full</guilabel> (0dB gain), -6dB gain or
1097 <guilabel>Edit</guilabel> which allows you to set the required gain
1102 Consider, for example, the case in <xref linkend="fig-audio-map-eg1"/>.
1105 <figure id="fig-audio-map-eg1">
1106 <title>Audio map example 1</title>
1109 <imagedata fileref="screenshots/audio-map-eg1&scs;"/>
1115 Here, we have two channels in the source which are mapped to left and
1116 right, respectively, in the DCP. The full green boxes show that the
1117 mapping is at unity gain (0dB) in each case. Imagine that we modify
1118 the settings to those shown in <xref linkend="fig-audio-map-eg2"/>
1121 <figure id="fig-audio-map-eg2">
1122 <title>Audio map example 2</title>
1125 <imagedata fileref="screenshots/audio-map-eg2&scs;"/>
1131 We now have the content's streams mapped to left and right and also
1132 mixed together and placed in the DCP's centre channel. The smaller
1133 green boxes on the centre mappings show that those channels are added
1134 with some non-unity gain; you can see by hovering the mouse pointer
1135 over those boxes that the gain for content channels 1 and 2 is -6dB
1136 when being sent to the centre channel and 0dB when being sent to left
1140 <figure id="fig-audio-map-eg3">
1141 <title>Audio map example 3</title>
1144 <imagedata fileref="screenshots/audio-map-eg3&scs;"/>
1150 As a final example, the map in <xref linkend="fig-audio-map-eg3"/>
1151 shows the mapping of a 5.1 source into a 5.1 DCP.
1157 <!-- ============================================================== -->
1159 <title>Other controls</title>
1162 ‘Audio Gain’ is used to alter the volume of the
1163 soundtrack. The specified gain (in dB) will be applied to each sound
1164 channel of your content before it is written to the DCP.
1168 If you use a sound processor that DCP-o-matic knows about, it can help
1169 you calculate changes in gain that you should apply. Say, for
1170 example, that you make a test DCP and find that you have to run it at
1171 volume 5 instead of volume 7 to get a good sound level in the screen.
1172 If this is the case, click the <guilabel>Calculate...</guilabel>
1173 button next to the audio gain entry, and the dialogue box in <xref
1174 linkend="fig-calculate-audio-gain"/> will open.
1177 <figure id="fig-calculate-audio-gain">
1178 <title>Calculating audio gain</title>
1181 <imagedata fileref="screenshots/calculate-audio-gain&scs;"/>
1187 For our example, put 5 in the first box and 7 in the second and click
1188 <guilabel>OK</guilabel>. DCP-o-matic will calculate the audio gain
1189 that it should apply to make this happen. Then you can re-make the
1190 DCP (this will be reasonably fast, as the video data will already have
1191 been done) and it should play back at the correct volume with 7 on
1192 your sound-rack fader.
1196 Current versions of DCP-o-matic only know about the Dolby CP650 and
1197 CP750. If you use a different sound processor, and know the gain
1198 curve of its volume control, <ulink url="mailto:carl@dcpomatic.com">get in
1203 <guilabel>Audio Delay</guilabel> is used to adjust the synchronisation
1204 between audio and video. A positive delay will move the audio later
1205 with respect to the video, and a negative delay will move it earlier.
1212 <!-- ============================================================== -->
1214 <title>Subtitles</title>
1217 The subtitles tab contains settings related to subtitles in your
1218 content, as shown in <xref linkend="fig-subtitles-tab"/>.
1221 <figure id="fig-subtitles-tab">
1222 <title>Subtitle settings tab</title>
1225 <imagedata fileref="screenshots/subtitles-tab&scs;"/>
1231 DCP-o-matic can either:
1235 <listitem>Extract subtitles that are embedded in video files, or</listitem>
1236 <listitem>Use subtitles from SubRip (<code>.srt</code>), SubStation
1237 Alpha (<code>.ssa</code>) or DCP XML files. You may find the great
1239 url="http://www.nikse.dk/subtitleedit/">Subtitle Edit</ulink> useful
1240 for creating such files.</listitem>
1244 Embedded subtitles are usually represented using a set of bitmaps,
1245 especially on files that have come from DVD or BluRay. Such subtitles
1246 can (currently) only be ‘burnt’ into the DCP (that is,
1247 they are included in the image and not overlaid by the projector).
1251 With SubRip, SubStation Alpha or DCP subtitles you have the choice to
1252 either burn-in or include the subtitles as separate subtitle
1253 ‘asset’ within your DCP (in which case the projector
1254 overlays them onto the image on playback). The difference between
1255 burn-in and overlay is illustrated by <xref linkend="fig-burn-in"/>
1256 and <xref linkend="fig-discrete"/>.
1259 <figure id="fig-burn-in">
1260 <title>Burnt-in subtitles</title>
1263 <imagedata scale="100" fileref="diagrams/burn-in&dia;"/>
1268 <figure id="fig-discrete">
1269 <title>Separate subtitles</title>
1272 <imagedata scale="100" fileref="diagrams/discrete&dia;"/>
1278 The advantage of separate subtitles is that the same video content can
1279 be used for DCPs in many different languages. This means that only a
1280 small text file needs to be changed for each target language, rather
1281 than a large video file. It also means that the time-consuming video
1282 encoding need only be done once for the project rather than once for
1287 Select the <guilabel>Use Subtitles</guilabel> check-box to enable
1288 the subtitles in the selected content.
1292 Select the <guilabel>Burn subtitles into image</guilabel> check-box to
1293 burn these subtitles into the image; if this is not ticked the
1294 subtitles will be included separately in the DCP to be rendered by the
1295 projector. This check-box will always be ticked if you are using
1296 embedded ‘image’ subtitles.
1300 The <guilabel>X Offset</guilabel> and <guilabel>Y Offset</guilabel>
1301 controls move the subtitles around within the image. The offsets are
1302 expressed as a percentage of the video frame size; 100% X offset is
1303 the entire width of the frame, and 100% Y offset is the entire height.
1304 Hence, to move the subtitles down by half the frame height you would
1305 use a Y offset of 50%.
1309 The <guilabel>X Scale</guilabel> and <guilabel>Y Scale</guilabel>
1310 controls scale the subtitles. Scale values of 1 make the subtitles
1311 the same size (relative to the size of the image) as they are on the
1312 original. Values lower than 1 make them smaller, and values higher
1313 make them larger. You can stretch the subtitles in either direction
1314 by specifying different values for X and Y scale. Subtitles from DVD
1315 and Blu Ray sources are frequently larger (relative to the video
1316 frame) than those typically used for DCP, so it is often useful to
1317 scale such subtitles down using these controls.
1321 The <guilabel>Stream</guilabel> control changes the subtitle stream
1322 that is used when the content has more than one.
1326 If you are using non-embedded (text) subtitles you can see the
1327 subtitle text and timings by clicking the <guilabel>View...</guilabel>
1328 button, or specify the fonts that should be used by clicking <guilabel>Fonts...</guilabel>.
1332 With any subtitles you can click <guilabel>Appearance...</guilabel> to
1333 change how the subtitles look.
1339 <!-- ============================================================== -->
1341 <title>Timing</title>
1344 The timing tab contains settings related to the timing of your
1345 content, as shown in <xref linkend="fig-timing-tab-detail"/>.
1348 <figure id="fig-timing-tab-detail">
1349 <title>Timing settings tab</title>
1352 <imagedata fileref="screenshots/timing-tab&scs;"/>
1358 Most of the timing tab's entries are <emphasis>time-codes</emphasis>.
1359 These are expressed as four numbers, as shown in <xref
1360 linkend="fig-timecode"/>.
1363 <figure id="fig-timecode">
1364 <title>Timecode</title>
1367 <imagedata scale="100" fileref="diagrams/timecode&dia;"/>
1373 <guilabel>Position</guilabel> is the time at which this piece of
1374 content should start within the DCP. In most cases, this will be
1375 <code>0:0:0:0</code> to make the content start at the beginning of the
1380 <guilabel>Full length</guilabel> is the length of the piece of
1381 content. This can only be set for still-image content: for video or
1382 sound content, it is fixed by the nature of the content file. If
1383 still-image content is being used you can set the length for which it
1384 should be displayed using this control.
1388 <guilabel>Trim from start</guilabel> specifies the amount that should be trimmed from the start of the content.
1392 <guilabel>Trim from end</guilabel> specifies the amount that should be trimmed from the end of the content.
1396 <guilabel>Play length</guilabel> indicates how long this piece of
1397 content will be once the trims have been applied. This will be equal
1398 to the full length minus <guilabel>trim-from-start</guilabel> and minus <guilabel>trim-from-end</guilabel>.
1402 <guilabel>Video frame rate</guilabel> specifies the frame rate for
1403 still-image content. It can also be used to override the detected
1404 frame rate of other content if DCP-o-matic has got it wrong.
1408 Each timecode control has a <guilabel>Set</guilabel> which you should
1409 click when you have entered a new value for a timecode. The
1410 <guilabel>Set</guilabel> button will make DCP-o-matic take account of
1411 any changes to the corresponding timecode.
1417 <!-- ============================================================== -->
1419 <title>Video processing pipeline</title>
1422 This section gives a little more detail about how DCP-o-matic process
1423 video as it takes it from a source and puts it into a DCP.
1427 Consider, as a somewhat over-the-top example, that we have a 720 x 576
1428 image which is letterboxed with 36 black pixels each at the top and
1429 bottom, and the video content within the letterbox should be presented
1430 in the DCP at ratio of 2.39:1 within a 1.85:1 frame (such as might
1431 happen with a trailer). The source image is shown in <xref
1432 linkend="fig-pipeline1"/>.
1435 <figure id="fig-pipeline1">
1436 <title>Example image to demonstrate video processing</title>
1439 <imagedata scale="100" fileref="diagrams/pipeline1&dia;"/>
1445 DCP-o-matic runs through the following steps when preparing an image for a DCP:
1449 <listitem>Crop</listitem>
1450 <listitem>Scale</listitem>
1451 <listitem>Place in container</listitem>
1455 First, some amount of the image can be cropped. This is almost always
1456 used to remove black borders (letterboxing and/or pillarboxing) around
1461 In our example image, we would use 36 pixels of crop from the top and
1462 bottom. This would give the new image shown in <xref
1463 linkend="fig-pipeline2"/>.
1466 <figure id="fig-pipeline2">
1467 <title>Example image after cropping</title>
1470 <imagedata scale="100" fileref="diagrams/pipeline2&dia;"/>
1476 The next step is to scale the image. Since this content should be
1477 presented in a 2.39:1 aspect ratio inside a 1.85:1 DCP we would select
1478 <guilabel>Scope</guilabel> from the <guilabel>Scale to</guilabel>
1479 option in the <guilabel>Video</guilabel> tab and
1480 <guilabel>Flat</guilabel> from the <guilabel>Container</guilabel>
1481 option in the <guilabel>DCP</guilabel> tab.
1484 <para>The <guilabel>Scale to</guilabel> option should always be set to
1485 the aspect ratio at which the content should be seen. The
1486 <guilabel>Container</guilabel> option should be set to the preset that
1487 you want to use on the projector. Of course, these two settings will
1492 Given the scaling and container information, DCP-o-matic will look at
1493 the DCP's container size, and then scale the source image up until one
1494 or both of its dimensions (width, height or both) fits the size of the
1495 container, all the while preserving the desired aspect ratio.
1499 In our example here, the DCP's container is specified as 1.85:1 (so
1500 that the DCP will play back correctly using the projector's
1501 ‘Flat’ preset). At 2K, 1.85:1 is 1998 pixels by 1080.
1502 Scaling the source up whilst preserving its 1.85:1 aspect ratio will
1503 result in the image hitting the sides of the container first, at a
1504 size of 1998 x 836. This gives us a new version of the image as shown
1505 in <xref linkend="fig-pipeline3"/>.
1508 <figure id="fig-pipeline3">
1509 <title>Example image after cropping and scaling</title>
1512 <imagedata scale="100" fileref="diagrams/pipeline3&dia;"/>
1518 The final step is to place the image into the DCP. In this case,
1519 since we have a 2.39:1 image that should be presented as a 1.85:1 DCP,
1520 we have set the <guilabel>container</guilabel> in the
1521 <guilabel>DCP</guilabel> tab to be Scope. Since the content has been
1522 scaled to 1998 x 836, and a Flat container is 1998 x 1080, there will
1523 be some black bars at the top and bottom of the image. DCP-o-matic
1524 shares out this black equally, as shown in <xref
1525 linkend="fig-pipeline3"/>.
1528 <figure id="fig-pipeline4">
1529 <title>Example image in the DCP</title>
1532 <imagedata scale="100" fileref="diagrams/pipeline4&dia;"/>
1541 <chapter xml:id="ch-dcp" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en">
1542 <title>DCP settings</title>
1545 This chapter describes the settings that apply to the whole DCP. The
1546 controls for these settings are in the <guilabel>DCP</guilabel> tab of
1547 the main window, as shown in <xref linkend="fig-dcp-tab"/>.
1550 <figure id="fig-dcp-tab">
1551 <title>DCP settings tab</title>
1554 <imagedata fileref="screenshots/dcp-tab&scs;"/>
1560 The first thing here is the name. This is generally set to the title
1561 of the film that is being encoded. If <guilabel>Use ISDCF
1562 name</guilabel> is not ticked, the name that you specify will be used
1563 as-is for the name of the DCP. If <guilabel>Use ISDCF name</guilabel>
1564 is ticked, the name that you enter will be used as part of a
1565 ISDCF-compliant name.
1569 Underneath the name field is a preview of the name that the DCP will
1570 get. To use a ISDCF-compliant name, tick the <guilabel>Use ISDCF
1571 name</guilabel> check-box. The ISDCF name will be composed using details
1572 of your content's soundtrack, the current date and other things that
1573 can be specified in the ISDCF name details dialogue box, which you can
1574 open by clicking on the <guilabel>Details</guilabel> button.
1578 If you want to take the ISDCF-compliant name that DCP-o-matic
1579 generates and modify it, click <guilabel>Copy as name</guilabel> and
1580 the ISDCF name will be copied into the <guilabel>Name</guilabel> box.
1581 You can then edit it as you wish. The DCP name should not matter (in
1582 that it should not affect how the DCP ingests or plays) but
1583 projectionists will appreciate it if you use the standard naming
1584 scheme as it makes it easier to identify details of the content.
1588 The <guilabel>Content Type</guilabel> option can be
1589 ‘feature’, ‘trailer’ or whatever; select the
1590 required type from the drop-down list. On some projection systems
1591 this will affect where your content appears in the projector's server
1592 user interface, so take care to select an appropriate type.
1596 The <guilabel>Signed</guilabel> check-box sets whether or not the DCP
1597 is signed. This is rarely important; if in doubt, tick it.
1601 The <guilabel>Encrypted</guilabel> check-box will set whether the DCP
1602 should be encrypted or not. If this is ticked, the DCP will require a
1603 KDM to play back. Encryption is discussed in <xref
1604 linkend="ch-encryption"/>.
1608 If you use encryption DCP-o-matic will generate a random encryption
1609 key for you. To specify your own key, click the
1610 <guilabel>Edit..</guilabel> button next to the key.
1614 The <guilabel>Reels</guilabel> and <guilabel>Reel length</guilabel>
1615 controls specify how the DCP will be split up into
1616 ‘reels’. See <xref linkend="sec-reels"/> below.
1620 The <guilabel>Standard</guilabel> option specifies which of the two
1621 DCP standards DCP-o-matic should use. If in doubt, use SMPTE (the
1622 more modern of the two).
1626 Ticking the <guilabel>Upload DCP to TMS after it is made</guilabel>
1627 will ask DCP-o-matic to copy the finished DCP to your configured TMS (see <xref linkend="sec-prefs-tms"/>).
1631 At the bottom of the DCP tab are a further two tabs, one each to
1632 contain the settings for the DCP's video and audio parts.
1636 The <guilabel>Container</guilabel> option sets the ratio of the image
1637 in the DCP. If this ratio is different to the ratio used for any
1638 content, DCP-o-matic will pad the content with black. In simple cases
1639 this should be set to the same ratio as that for the the primary piece
1640 of video content. Alternatively, you might want to pillarbox a small
1641 format into a Flat container: in this case, select the small format
1642 for the content's ratio and ‘Flat’ for the DCP.
1646 The <guilabel>Frame Rate</guilabel> control sets the frame rate of
1647 your DCP. This can be a little tricky to get right. Ideally, you
1648 want it to be the same as the video content that you are using. If it
1649 is not the same, DCP-o-matic must resort to some tricks to alter your
1650 content to fit the specified frame rate. Frame rates are discussed in
1651 more detail in <xref linkend="ch-frame-rates"/>.
1655 The <guilabel>Use best</guilabel> button sets the DCP video frame rate
1656 to what DCP-o-matic thinks is the best given the content that you have
1661 The <guilabel>3D</guilabel> button will set your DCP to 3D mode if it
1662 is checked. A 3D DCP will then be created, and any 2D content will be
1663 made 3D compatible by repeating the same frame for both left and right
1664 eyes. A 3D DCP can be played back on many 3D systems (e.g. Dolby 3D,
1665 Real-D etc.) but not on a 2D system.
1669 The <guilabel>Resolution</guilabel> tab allows you to choose the
1670 resolution for your DCP. Use 2K unless you have content that is of
1671 high enough resolution to be worth presenting in 4K.
1675 The <guilabel>JPEG2000 bandwidth</guilabel>; setting changes how big
1676 the final image files used within the DCP will be. Larger numbers
1677 will give better quality, but correspondingly larger DCPs. The
1678 bandwidth can be between 50 and 250 megabits per second (Mbit/s).
1679 Most commercial DCPs use bit rates between 75 and 125 MBit/s.
1683 The <guilabel>Audio Channels</guilabel> control sets the number of
1684 audio channels that the DCP will have. If the DCP has any channels
1685 for which there is no content audio they will be replaced by silence.
1686 You can only set an even number of channels here, since that is
1687 required by the DCI standard. If you want an odd number of channels,
1688 set the DCP channel count to one greater than you need and the
1689 unused channel will be filled with silence.
1693 The <guilabel>Processor</guilabel> control allows you to select a
1694 process to apply to the audio before it goes into the DCP. Three processes are currently provided:
1698 <listitem>Mid-side decode — this will take a L/R
1699 stereo input and extract the common part (corresponding to the
1700 ‘Mid’ in a mid-side signal) into the DCP's centre channel.
1701 The remaining L/R parts will be kept in the L/R channels of the DCP.
1702 This may be useful to make near-field L/R mixes more compatible with
1703 cinema audio systems.</listitem>
1704 <listitem>Stereo to 5.1 up-mixer A — this will take a stereo input and up-mix it to ‘fake’ 5.1. The input L/R are treated as follows:
1706 <listitem>DCP L is input L bandpass-filtered between 1.9kHz and 4.8kHz.</listitem>
1707 <listitem>DCP R is input R bandpass-filtered between 1.9kHz and 4.8kHz.</listitem>
1708 <listitem>DCP C is input L mixed with input R, taken down by 3dB and then bandpass-filtered between 150Hz and 1.9kHz.</listitem>
1709 <listitem>DCP Lfe is input L mixed with input R, taken down by 3dB and then bandpass-filtered between 20Hz and 150Hz.</listitem>
1710 <listitem>DCP Ls is input L bandpass-filtered between 4.8kHz and 20kHz.</listitem>
1711 <listitem>DCP Rs is input R bandpass-filtered between 4.8kHz and 20kHz.</listitem>
1714 This upmixing algorithm is due to Gérald Maruccia.
1717 <listitem>Stereo to 5.1 up-mixer B — this uses a different approach:
1719 <listitem>DCP L is input L.</listitem>
1720 <listitem>DCP R is input R.</listitem>
1721 <listitem>DCP C is input L + input R taken down by 3dB.</listitem>
1722 <listitem>DCP Lfe is DCP C bandpass filtered between 20Hz and 150Hz.</listitem>
1723 <listitem>DCP Ls and Rs are input L - input R with a 20ms delay.</listitem>
1728 <!-- ============================================================== -->
1729 <section xml:id="sec-reels">
1730 <title>Reels</title>
1733 A ‘reel’ in a DCP is a subsection of the DCP, in the same
1734 way as a 35mm reel is a section of a film. A DCP can be split up into
1735 any number of reels and the joins (the equivalent to 35mm splices)
1736 between the reels are seamless.
1740 There is no reason why you can't just use a single reel for the whole
1741 of your DCP, as there is no limit on their length. Many people choose
1746 There are, however, some possible advantages of splitting things up
1752 The picture, sound and subtitle data of the DCP will be
1753 split up into more smaller files on disk, rather than fewer larger
1754 files. This can be useful if the DCP is to be transferred on storage
1755 that have file size limits. The FAT32 filesystem, for example, can
1756 only hold files smaller than 4Gb. A 6Gb DCP with a single reel could
1757 not be transferred using a FAT32-formatted disk. If that DCP were
1758 split up into two 3Gb reels it could be transferred.
1761 It is easier to re-use DCP components if they are in reels. Consider,
1762 for example, a film company who wants to put a 5 second ident onto the
1763 beginning of DCPs that they distribute. If they receive a feature
1764 film DCP they can modify it to add their ident as a separate reel.
1765 This is easier than attaching the picture data in the DCP.
1770 DCP-o-matic offers three options for setting up the reels in your DCP:
1771 single reel, split by video content or custom.
1775 <guilabel>Single reel</guilabel>, as its name suggests, keeps the whole DCP as one reel.
1776 This is a perfectly good option if you have no particular reason to
1781 <guilabel>Split by video content</guilabel> puts each piece of source
1782 video content in its own reel, as shown in <xref linkend="fig-reels-by-video"/>.
1785 <figure id="fig-reels-by-video">
1786 <title>Making reels using split by video content</title>
1787 <mediaobject><imageobject><imagedata scale="100" fileref="diagrams/reels-by-video&dia;"/></imageobject></mediaobject>
1791 Here we have three video files (<code>ident.mp4</code>,
1792 <code>feature.ts</code> and <code>cred.mov</code>). With
1793 <guilabel>split by video content</guilabel> DCP-o-matic makes a new
1794 reel to hold each video file.
1798 <guilabel>Custom</guilabel> splits reels by the size of the files that
1799 will make up their video content. With <guilabel>Custom</guilabel>
1800 you must specify a reel length in Gb. Then no file in the DCP will be larger than this reel length.
1806 <!-- ============================================================== -->
1808 <title>Show audio</title>
1811 The <guilabel>Show Audio</guilabel> button will instruct DCP-o-matic
1812 to examine the audio in your content and plot a graph of its level
1813 over time. This can be useful for getting a rough idea of how loud
1814 the sound will be in the cinema auditorium. A typical plot is shown
1815 in <xref linkend="fig-audio-plot"/>
1818 <figure id="fig-audio-plot">
1819 <title>Audio plot</title>
1822 <imagedata fileref="screenshots/audio-plot&scs;"/>
1828 The plot gives the audio level (vertical axis, in dB) with time
1829 (horizontal axis). 0dB represents full scale, so if there is anything
1830 near this you are in danger of clipping the projector's audio outputs.
1834 There are two plot types: the peak level and the RMS, which can be
1835 shown or hidden using the check-boxes on the right hand side of the
1840 The channel check-boxes will show or hide the plot(s) for
1841 the corresponding channels in the DCP.
1845 The smoothing slider applies a variable degree of temporal smoothing
1846 to the plots, which can make them easier to read in some cases.
1850 Obviously the audio plot is no substitute for listening in an
1851 auditorium, but it can be useful to get levels in the right rough area.
1858 <chapter xml:id="ch-encryption" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en">
1859 <title>Encryption</title>
1862 It is not required that DCPs be encrypted, but they can be. This
1863 chapter discusses the basic principles of DCP encryption, and how
1864 DCP-o-matic can create encrypted DCPs and KDMs for them.
1868 <!-- ============================================================== -->
1870 <title>Basics</title>
1873 DCPs can be encrypted. This means that the picture and sound data are
1874 encoded in such a way that only cinemas ‘approved’ by the
1875 DCP's creators can read them. In particular, this means copies of the
1876 DCP can be distributed by insecure means: if an ne'er-do-well called
1877 Mallory obtains a hard drive containing an encrypted DCP, there is no
1878 way that he can play it. Only those cinemas who receive a correct key
1879 delivery message (KDM) can play the DCP.
1883 <!-- ============================================================== -->
1885 <title>How it works (in a nutshell)</title>
1888 This section attempts to summarise how DCP encryption works. You can
1889 skip it if you like. You may need some knowledge of encryption
1890 methods to understand it.
1894 We suppose that we are trying to send a DCP to
1895 Alice's cinema without a troublemaker called Mallory being able to
1900 There are two main families of encryption techniques. The first,
1901 symmetric-key encryption, allows us to encode some data using some
1902 numeric key. After encoding, no-one can decode the data unless they
1907 The first step in a DCP encryption is to encode its data with some key
1908 using symmetric-key encryption. The encrypted DCP can then be sent
1909 anywhere, safe in the knowledge that even if Mallory got hold of a
1910 copy, he could not decrypt it.
1914 Alice, however, needs to know the key so she can play the DCP in her
1915 cinema. A simple approach might be for us to send Alice the key.
1916 However, if Mallory can intercept the DCP, he might also be able to
1917 intercept our communication of the key to Alice. Furthermore, if Alice
1918 happened to know Mallory, she could just send him a copy of the key.
1922 The clever bit in the process requires the use of public-key
1923 encryption. With this technique we can encrypt a block of data using
1924 some ‘public’ key. That data can then only be decrypted
1925 using a corresponding private key which is
1926 <emphasis>different</emphasis> to the public key. The private and
1927 public keys form a pair which are related mathematically, but it is
1928 extremely hard (or rather, virtually impossible) to derive the private
1929 key from the public key.
1933 Public-key encryption allows us to distribute the DCP's key to Alice
1934 securely. The manufacturer of Alice's projector generates a public
1935 and private key. They hide the private key deep inside the bowels of
1936 the projector (inside an integrated circuit) where no-one can read it.
1937 They then make the public key available to anyone who is interested.
1941 We take our DCP's symmetric key and encrypt it using the public key of
1942 Alice's projector. We send the result to Alice over email (using a
1943 format called a Key Delivery Message, or KDM). Her projector then
1944 decrypts our message using its private key, yielding the magic
1945 symmetric key which can decrypt the DCP.
1949 If is fine if Mallory intercepts our email to Alice, since the only
1950 key which can decrypt the message is the private key buried inside
1951 Alice's projector. The projector manufacturer is very careful that
1952 no-one ever finds out what this key is. Our DCP is secure: only Alice
1953 can play it back, since only her projector knows the key (even Alice
1961 <!-- ============================================================== -->
1963 <title>Encryption using DCP-o-matic</title>
1966 There are two steps to distributing an encrypted DCP. First, the
1967 DCP's data must be encrypted, and secondly KDMs must be generated for
1968 those cinemas that are allowed to play the DCP.
1972 The first part is simple: ticking the <guilabel>Encrypted</guilabel>
1973 box in the <guilabel>DCP</guilabel> tab will instruct DCP-o-matic to
1974 encrypt the DCP that it makes using a random key that DCP-o-matic
1975 generates. The key will be written to the film's metadata file, which
1976 should be kept secure.
1980 A DCP that is generated with the <guilabel>Encrypted</guilabel> box
1981 ticked will not play on any projector as-is (it will be marked as
1982 ‘locked’, or whatever the projector manufacturer's term
1987 The second part of distributions is to generate KDMs for the cinemas
1988 that you wish to allow to play your DCP. There are two approaches to
1989 this within DCP-o-matic: using the project, or using a DKDM. These
1990 approaches are now described in turn.
1994 <title>Creating KDMs from a DCP-o-matic project</title>
1997 You can create KDMs from inside a DCP-o-matic project using the
1998 <guilabel>Make KDMs</guilabel> option on the <guilabel>Jobs</guilabel>
1999 menu. This will open the KDM dialogue box, as shown in <xref
2000 linkend="fig-kdm"/>.
2003 <figure id="fig-kdm">
2004 <title>KDM dialog</title>
2007 <imagedata fileref="screenshots/kdm&scs;"/>
2013 In order to generate KDMs for a particular projector, you need to know
2014 its <emphasis>certificate</emphasis>. These are usually made
2015 available by the projector manufacturers as text files with a
2016 <code>.pem</code> extension.
2020 DCP-o-matic can store these certificates along with details of their
2021 cinemas and screens within those cinemas. Each screen has a
2022 certificate for its projector (and optionally certificates for other
2023 trusted devices, such as the sound processor). DCP-o-matic can
2024 generate KDMs for any screens that it knows about.
2028 To add a cinema, click <guilabel>Add Cinema...</guilabel>. This opens
2029 a dialogue box into which you can enter the cinema's name, and
2030 optionally an email address. This email address can be used to
2031 get DCP-o-matic to deliver KDMs via email.
2035 Once you have added a cinema, select it by clicking on its name, then
2036 click <guilabel>Add Screen...</guilabel>. The resulting dialogue
2037 allows you to enter a name for the screen and load in its certificate
2038 from a file. The certificate should be in SHA256 PEM format.
2042 Alternatively, certificates for projection systems made by some
2043 manufacturers can be downloaded from databases provided by the
2044 manufacturer. Currently this is supported for Doremi and Dolby
2045 equipment. If you are targeting a screen with equipment by one of
2046 these manufacturers you can click <guilabel>Download</guilabel> then
2047 enter the serial number of the server in the screen and click
2048 <guilabel>Download</guilabel> again and, all being well, the certificate
2053 Using the download system you will need to know the serial number of
2054 the media server in use in the screen. Most cinema projection or
2055 technical departments will know these serial numbers.
2059 Note that the reliability of the manufacturers' certificate databases
2060 cannot be guaranteed. It is vital that KDMs are tested by the
2061 destination cinema will in advance of show time to identify any
2066 Once you have set up all the screens that you need KDMs for, select
2067 the CPL that you want to create the KDM for. You can use the
2068 drop-down list to select the CPLs in the current film project, or load
2069 a CPL from somewhere else. Select the cinemas and/or screens that you
2070 want KDMs for and fill in the start and end dates and times.
2074 You must also select the type of KDM that you want to generate. If in
2075 doubt, use <guilabel>Modified Transitional 1</guilabel>.
2079 The differences between the three KDM types are fairly subtle.
2080 <guilabel>DCI Specific</guilabel> and <guilabel>DCI Any</guilabel> add
2081 a <code><ContentAuthenticator></code> tag to the KDM which
2082 allows the exhibitor to check that the DCP and KDM have come from a
2083 bona-fide source. In addition, <guilabel>DCI Specific</guilabel> adds
2084 information on trusted devices to the KDM. This allows the KDM
2085 creator to specify devices (such as sound processors) that are allowed
2086 to use keys delivered by the KDM. At present it is not clear how
2087 widely the <guilabel>DCI Specific</guilabel> and <guilabel>DCI
2088 Any</guilabel> features are supported (or even tolerated) by servers
2089 so you are advised to use <guilabel>Modified Transitional
2094 Finally, choose what you want to do with the KDMs. They can be
2095 written to disk, to a location that you can specify by clicking
2096 <guilabel>Browse</guilabel>. Alternatively, if you choose
2097 <guilabel>Send by email</guilabel> the KDMs will be zipped up and
2098 emailed to the appropriate cinema email addresses. Click
2099 <guilabel>Make KDMs</guilabel> to generate the KDMs.
2105 <title>Creating KDMs using a DKDM</title>
2109 It can be inconvenient to need a whole DCP-o-matic project just to
2110 create KDMs for its film. Perhaps you want to archive the project to
2111 save space, or create KDMs on a different machine. In such situations
2112 it is easier to use a DKDM. This is a normal KDM, but instead of
2113 being targeted at a projection system (to allow it to decrypt the
2114 content) it is targeted at a particular users's certificate. This
2115 means that the certificate owner can create new KDMs for other users.
2116 The DKDM holds everything that is required to create further KDMs.
2120 Sometimes it is useful to create DKDMs that can be used by
2121 DCP-o-matic. If you create such a DKDM you can keep it and then, at
2122 any point in the future, use DCP-o-matic's standalone KDM creator to
2123 make KDMs for the DKDM's film for any cinema.
2127 In other cases a DKDM is sent to a 3rd party so that they can create
2128 KDMs for your films. This can be useful if, for example, you have a
2129 distributor who provides 24-hour KDM support to cinemas and can create
2130 KDMs for anybody that requires them at short notice.
2134 To create a DKDM for DCP-o-matic, open your encrypted project and
2135 select <guilabel>Make DKDM for DCP-o-matic...</guilabel> from the
2136 <guilabel>Jobs</guilabel> menu. Select the CPL that you want to make
2137 the DKDM for and click <guilabel>OK</guilabel>. This DKDM will then
2138 be available in the KDM creator. This is a separate program which you
2139 can start from the same place that you start the ‘normal’
2140 DCP-o-matic. Its window is shown in <xref linkend="fig-kdm-creator"/>.
2143 <figure id="fig-kdm-creator">
2144 <title>The KDM creator</title>
2147 <imagedata fileref="screenshots/kdm-creator&scs;"/>
2153 To create KDMs, select the cinema(s) and/or screens that you want KDMs
2154 to be created for, the date range, the DCP that the KDMs are for and
2155 the destination for the KDMs and click <guilabel>Create
2160 By default the <guilabel>DKDM</guilabel> list will list any DCPs for
2161 which you have clicked <guilabel>Make DKDM for
2162 DCP-o-matic</guilabel>in the main DCP-o-matic program. If you have
2163 other DKDMs you can add them by clicking <guilabel>Add...</guilabel> and
2164 specifying the file containing the DKDM.
2168 If another organisation wants to send you a DKDM they will ask you for
2169 a target certificate. You can get DCP-o-matic's target certificate by
2170 opening <guilabel>Preferences</guilabel> and clicking <guilabel>Export
2171 DCP decryption certificate...</guilabel> in the <guilabel>Keys</guilabel>
2179 <title>Encryption overview</title>
2181 <figure id="fig-encryption-overview">
2182 <title>Overview of encryption</title>
2185 <imagedata fileref="diagrams/crypt&dia;"/>
2195 <!-- ============================================================== -->
2196 <chapter xml:id="ch-preferences" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en">
2197 <title>Preferences</title>
2200 DCP-o-matic provides a few preferences which can be used to modify its
2201 behaviour. This chapter explains those options.
2205 <!-- ============================================================== -->
2207 <title>The preferences dialogue</title>
2210 The preferences dialogue is opened by choosing
2211 <guilabel>Preferences...</guilabel> from the <guilabel>Edit</guilabel>
2212 menu. The dialogue is split into seven tabs.
2215 <!-- ============================================================== -->
2217 <title>General</title>
2220 The general tab is shown in <xref linkend="fig-prefs-general"/>.
2223 <figure id="fig-prefs-general">
2224 <title>General preferences</title>
2227 <imagedata fileref="screenshots/prefs-general&scs;"/>
2233 <!-- ============================================================== -->
2235 <title>Language</title>
2238 If you tick the <guilabel>Set Language</guilabel> checkbox and choose
2239 a language from the list, that language will be used for DCP-o-matic.
2240 You will need to restart DCP-o-matic to see the new language.
2244 The translations for DCP-o-matic have been contributed by helpful
2245 users. If your language is not on the last, head to <ulink
2246 url="http://dcpomatic.com/i18n.php">the DCP-o-matic website</ulink> to
2247 read about how to contribute a translation.
2252 <!-- ============================================================== -->
2254 <title>Threads</title>
2257 When DCP-o-matic is encoding DCPs it can use multiple parallel threads
2258 to speed things up. Set this value to the number of threads
2259 DCP-o-matic should use. This should normally be the number of
2260 processors (or processor cores) in your machine. DCP-o-matic will try
2261 to set this up correctly when you run it for the first time.
2266 <!-- ============================================================== -->
2268 <title>Cinema and screen database file</title>
2271 This option allows you to change the file that DCP-o-matic uses to
2272 store details of the cinemas and screens used to make KDMs.
2278 <title>Integrated loudness</title>
2281 If <guilabel>Find integrated loudness, true peak and loudness range
2282 when analysing audio</guilabel> is ticked, DCP-o-matic will do extra
2283 work when analysing audio. Leave this ticked if the extra parameters
2284 are useful to you. If not, untick it and audio analysis will be
2290 <!-- ============================================================== -->
2292 <title>Updates</title>
2295 The <guilabel>Check for updates on startup</guilabel> option, if
2296 enabled, will tell DCP-o-matic to check on <ulink
2297 url="http://dcpomatic.com/">dcpomatic.com</ulink> to see if there any
2298 newer versions of DCP-o-matic then the one you are running. If so, a
2299 dialogue box will open with a link to download the new version.
2304 The <guilabel>Check for testing updates as well as stable
2305 ones</guilabel> option will also check for test updates as well as
2306 those that are formally ‘released’. This is useful if you
2307 like to live on the bleeding edge!
2311 <!-- ============================================================== -->
2313 <title>Issuer and creator</title>
2316 With these controls you can set the issuer and creator strings that
2317 will be put into the DCPs which you create.
2323 <!-- ============================================================== -->
2325 <title>Defaults</title>
2328 The defaults tab is shown in <xref linkend="fig-prefs-defaults"/>.
2331 <figure id="fig-prefs-defaults">
2332 <title>Defaults preferences</title>
2335 <imagedata fileref="screenshots/prefs-defaults&scs;"/>
2341 The options in this tab simply allow you to set up default values for
2342 various properties of new films.
2347 <!-- ============================================================== -->
2349 <title>Servers</title>
2352 The servers tab is shown in <xref linkend="fig-prefs-servers"/>.
2355 <figure id="fig-prefs-servers">
2356 <title>Servers preferences</title>
2359 <imagedata fileref="screenshots/prefs-servers&scs;"/>
2365 If <guilabel>Use all servers</guilabel> is ticked DCP-o-matic will
2366 locate encoding servers automatically (see <xref
2367 linkend="ch-servers"/>).
2371 Instead of this (or in addition) servers can be specified explicitly.
2372 To add a server, click <guilabel>Add...</guilabel> and enter the host
2373 name or IP address of the server to use.
2379 <!-- ============================================================== -->
2380 <section xml:id="sec-prefs-keys">
2384 The Keys tab (shown in <xref linkend="fig-prefs-keys"/>) holds options
2385 related to the keys and certificates used in some parts of DCP
2389 <figure id="fig-prefs-keys">
2390 <title>Keys preferences</title>
2393 <imagedata fileref="screenshots/prefs-keys&scs;"/>
2399 At the top of the tab is the chain of certificates that will be used
2400 to sign DCPs and KDMs. DCP-o-matic creates a random chain when you
2401 first run it and if you are happy to use this chain you can ignore the
2402 preferences. Otherwise, you can add or remove certificates from the
2403 chain using the <guilabel>Add...</guilabel> and
2404 <guilabel>Remove</guilabel> buttons.
2408 If you want DCP-o-matic to re-create the certificate chain (using new,
2409 random certificates) click <guilabel>Re-make
2410 certificates...</guilabel> and specify your organisation and common
2411 names in the dialogue box that opens.
2415 Underneath the certificate chain is the private key that corresponds
2416 to the leaf certificate in the chain. You can specify your own
2417 private key by clicking <guilabel>Load...</guilabel>. You must do
2418 this if you change the leaf certificate, so that the leaf private key
2419 corresponds to the public key held in the leaf certificate.
2423 Underneath the details of the certificate chain and private key for
2424 signing of DCPs and KDMs is a second chain and key which is used by
2425 DCP-o-matic when you import an encrypted DCP as a piece of content.
2426 The leaf certificate of this chain contains the public key that should
2427 be used when targeting a KDM at DCP-o-matic.
2431 If you want to import an encrypted DCP you will need to give the
2432 decryption certificate to the distributor of the DCP so that they can
2433 generate a DKDM for you. You can save this certificate to disk by
2434 clicking <guilabel>Export DCP decryption certificate...</guilabel>. As
2435 with the signing chain, DCP-o-matic will create a certificate chain
2436 and private key for you. You can also choose to load your own
2437 certificates and key or re-make the chain and key with new, random
2443 <!-- ============================================================== -->
2444 <section xml:id="sec-prefs-tms">
2446 <titleabbrev xml:id="sec-prefs-tms-short">TMS preferences</titleabbrev>
2449 The TMS tab (shown in <xref linkend="fig-prefs-tms"/>) gives some
2450 options for specifying details about your theatre management system
2451 (TMS). If you do this, and your TMS accepts SSH or FTP connections,
2452 you can upload DCPs directly from DCP-o-matic to the TMS using the
2453 <guilabel>Send DCP to TMS</guilabel> option in the
2454 <guilabel>Jobs</guilabel> menu.
2457 <figure id="fig-prefs-tms">
2458 <title>TMS preferences</title>
2461 <imagedata fileref="screenshots/prefs-tms&scs;"/>
2467 <guilabel>Protocol</guilabel> should be set to SCP or FTP as
2468 appropriate for your TMS. We know that the Arts Alliance Media (AAM)
2469 and the Doremi ranges uses SCP connections, and that Dolby's TMSs use
2470 FTP. Do let us know if you use any other type of TMS with the
2471 <guilabel>Send DCP to TMS</guilabel> feature.
2475 <guilabel>TMS IP address</guilabel> should be set to the IP address of
2476 your TMS, <guilabel>TMS target path</guilabel> to the place that DCPs
2477 should be uploaded to (which will be relative to the home directory of
2478 the SSH or FTP user). Finally, the user name and password are the
2479 credentials required to log into the TMS via SSH or FTP.
2483 Note that for this to work on Doremi servers you will need to set the
2484 <code>PasswordAuthentication</code> option in your server's
2485 <code>sshd_config</code> to <code>yes</code>.
2491 <!-- ============================================================== -->
2493 <title>KDM email</title>
2496 The KDM email is shown in <xref linkend="fig-prefs-kdm-email"/>.
2499 <figure id="fig-prefs-kdm-email">
2500 <title>KDM email preferences</title>
2503 <imagedata fileref="screenshots/prefs-kdm-email&scs;"/>
2509 This is a template for the email that is used to send KDMs out to
2510 cinemas. You can change it to say whatever you like. A few
2511 ‘magic’ strings will be replaced by information from the
2512 KDM that is being sent:
2516 <title>‘Magic’ KDM strings</title>
2517 <tgroup cols='2' align='left' colsep='1' rowsep='1'>
2520 <entry><code>$CPL_NAME</code></entry><entry>DCP title</entry>
2523 <entry><code>$CINEMA_NAME</code></entry><entry>Cinema name</entry>
2526 <entry><code>$SCREENS</code></entry><entry>Name of screen or screens that KDMs are being generated for</entry>
2529 <entry><code>$START_TIME</code></entry><entry>The time from which the KDMs are valid</entry>
2532 <entry><code>$END_TIME</code></entry><entry>The time until which the KDMs are valid</entry>
2539 The <guilabel>Reset to default text</guilabel> will replace the current KDM email with DCP-o-matic's default.
2545 <!-- ============================================================== -->
2546 <section xml:id="sec-prefs-advanced">
2547 <title>Advanced</title>
2548 <titleabbrev xml:id="sec-prefs-advanced-short">Advanced preferences</titleabbrev>
2551 The advanced preferences are shown in <xref linkend="fig-prefs-advanced"/>.
2554 <figure id="fig-prefs-advanced">
2555 <title>Advanced preferences</title>
2558 <imagedata fileref="screenshots/prefs-advanced&scs;"/>
2564 <guilabel>Maximum JPEG2000 bandwidth</guilabel> specifies the maximum
2565 bit-rate of JPEG2000 that DCP-o-matic will allow you to create. You
2566 are advised to leave this at 250Mbit/s in normal use for maximum DCP
2571 <guilabel>Allow any DCP frame rate</guilabel> removes the limits on
2572 the DCP video frame rates that DCP-o-matic will create. This may be
2573 useful for experimentation. Again, you are strongly advised to leave
2574 this unticked for normal use.
2578 <guilabel>Only servers encode</guilabel> makes DCP-o-matic encode
2579 JPEG2000 data only on encoding servers and not on the host. We
2580 suggest you leave this un-ticked unless you have a good reason to do otherwise.
2584 The four checkboxes labelled <guilabel>Log</guilabel> control what
2585 sort of messages DCP-o-matic writes to its log file when creating a
2586 DCP. It is useful to leave <guilabel>General</guilabel>,
2587 <guilabel>Warnings</guilabel> and <guilabel>Errors</guilabel> ticked
2588 as this makes the log files useful for tracking down bugs.
2592 The <guilabel>Timing</guilabel> checkbox will enable extra log entries
2593 to allow developers to investigate and optimize the speed of
2594 DCP-o-matic. It will significantly increase the size of the log files
2595 that are generated, so in normal use it is best to leave this
2603 <chapter xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en" xml:id="ch-frame-rates">
2604 <title>Frame rates</title>
2607 In an ideal world, a DCP would be created using content at the same
2608 video frame and audio sampling rates as the DCP. This is not,
2609 however, always possible.
2613 <!-- ============================================================== -->
2615 <title>DCP frame rate limitations</title>
2618 There are some limitations to video and audio frame rates in DCPs. This is
2619 complicated by the fact that not all projectors will play DCPs at the
2620 same frame rates. It is possible to create a DCP which one projector will
2621 play fine, but another (of a different type) will refuse to play, or
2622 even refuse to ingest.
2626 <!-- ============================================================== -->
2628 <title>Guaranteed rates</title>
2631 The only rates that are (pretty much) guaranteed to work on all DCI
2632 projectors are 24 frames per second (fps) for video and 48kHz or 96kHz
2633 for audio. If you are sending your DCPs to unknown places it wise to
2634 consider using these rates if at all possible.
2640 <!-- ============================================================== -->
2642 <title>Other often-supported rates</title>
2644 Many projectors now in the wild support additional video frame rates:
2650 <!-- ============================================================== -->
2652 <title>Adapting content to fit the DCP rate</title>
2655 DCP-o-matic has a few tricks to allow you to use content that is not
2656 in one of the ‘approved’ rates.
2660 Audio is easy: DCP-o-matic can resample to 48kHz from any source rate
2661 with minimal loss in quality.
2665 Video rate conversion is harder. DCP-o-matic's basic strategy to deal
2666 with a non-supported content rate is to run it at the wrong speed, and
2667 to adjust the audio to keep it in sync.
2670 <para>Let us consider the example of a 25fps source for which you want
2671 to create a 24fps DCP. DCP-o-matic will put the frames from the
2672 source directly into the DCP without modification, but will tell the
2673 projector to play them back at 24fps. This means that the DCP's video
2674 will run slightly slower than the original.
2678 If DCP-o-matic did nothing else, the result of this would be that the
2679 audio would be running at the original speed with the video running
2680 slowly. Hence the audio would drift slowly out of sync. To avoid
2681 this, DCP-o-matic also resamples the audio such that the projector
2682 will play it too slow by the same amount. Hence it will sound
2683 slightly different but will remain in sync with the video.
2687 For very low or high frame rates, DCP-o-matic can also skip or duplicate frames.
2694 <!-- ============================================================== -->
2696 <title>Setting up</title>
2699 The <guilabel>Frame Rate</guilabel> control in the
2700 <guilabel>DCP</guilabel> tab sets the video frame rate that the DCP
2701 will use. Clicking <guilabel>Use best</guilabel> sets the rate to
2702 what DCP-o-matic thinks is the best for your content. With this
2703 button, DCP-o-matic assumes that the whole range of frame rates (24,
2704 25, 30 and 48fps) are allowable.
2708 After this, the <guilabel>Video</guilabel> tab for each piece of
2709 content will give a summary of what DCP-o-matic is doing with that
2714 If you want to experiment with other non-standard frame rates, you can
2715 do so by ticking the <guilabel>Allow any DCP frame rate</guilabel> in
2716 the <guilabel>Advanced</guilabel> tab of the preferences dialogue (see the
2717 <xref linkend="sec-prefs-advanced" endterm="sec-prefs-advanced-short"/>). You are strongly advised to
2718 use this only on your own equipment, and only for experimentation
2727 <chapter xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en" xml:id="ch-servers">
2728 <title>Encoding servers</title>
2731 One way to increase the speed of DCP encoding is to use more
2732 than one machine at the same time. An instance of DCP-o-matic can
2733 offload some of the time-consuming JPEG2000 encoding to any number of
2734 other machines on a network. To do this, one ‘master’
2735 machine runs DCP-o-matic, and the ‘server’ machines run
2736 a small program called <code>dcpomatic_server</code>.
2740 The master and server machines do not need to be the same type, so you
2741 can mix Windows PCs, Macs and Linux machines as you wish.
2745 <!-- ============================================================== -->
2747 <title>Running the servers</title>
2750 There are two options for the encoding server;
2751 <code>dcpomatic_server_cli</code>, which runs on the command line, and
2752 <code>dcpomatic_server</code>, which has a simple GUI. The command line
2753 version is well-suited to headless servers, especially on Linux, and
2754 the GUI version works best on Windows where it will put an icon in the
2759 To run the command line version, simply enter:
2763 dcpomatic2_server_cli
2767 at a command prompt. If you are running the program on a machine with
2768 a multi-core processor, you can run multiple parallel encoding threads
2769 by doing something like:
2773 dcpomatic2_server_cli -t 4
2777 to run 4 threads in parallel.
2781 To run the GUI version on windows, run the ‘DCP-o-matic encode
2782 server’ from the start menu. An icon will appear in the system
2783 tray; right-click it to open a menu from whence you can quit the
2784 server or open a window to show its status.
2787 <para>If you would rather not bother installing DCP-o-matic on your
2788 server computers, the other option is to use the live-CD
2789 image that you can download from the <ulink
2790 url="http://dcpomatic.com/">DCP-o-matic web site.</ulink></para>
2792 <para>Either burn the image to CD, or write it to a USB stick (using
2793 something like <ulink
2794 url="http://unetbootin.sourceforge.net/">unetbootin</ulink>). Boot a
2795 PC from the CD or USB stick and it becomes a DCP-o-matic server
2796 without touching your standard operating system install.
2801 <!-- ============================================================== -->
2803 <title>Setting up DCP-o-matic</title>
2806 DCP-o-matic periodically looks on the local network for servers. Any
2807 that it finds are given work to do during encodes. Selecting
2808 <guilabel>Encoding Servers</guilabel> from the
2809 <guilabel>Tools</guilabel> menu brings up a window which shows that
2810 servers that DCP-o-matic has found.
2815 <!-- ============================================================== -->
2817 <title>Some notes about encode servers</title>
2820 DCP-o-matic does not mind if servers come and go; if a server
2821 disappears, DCP-o-matic will stop sending work to it, and will check
2822 it every minute or so in case it has come back online.
2826 You will probably find that using a 1Gb/s or faster network will
2827 provide a significant speed-up compared to a 100Mb/s network.
2834 <chapter xml:id="ch-files" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="en">
2835 <title>Generated files</title>
2838 DCP-o-matic generates a number of files as it makes a DCP. <xref
2839 linkend="fig-file-structure"/> shows the files that might be generated
2840 after you have created a DCP for a film called ‘DCP Test’.
2843 <figure id="fig-file-structure">
2844 <title>Creating a new film</title>
2847 <imagedata scale="100" fileref="diagrams/file-structure&dia;"/>
2853 The <code>DCP Test</code> folder is the one that you specify when you
2854 select the <guilabel>New Film</guilabel> option from DCP-o-matic's
2855 menu. Everything is stored inside this folder.
2859 DCP-o-matic generates some working files as it goes along. These are as follows:
2862 <listitem><code>log</code> is a list of notes that DCP-o-matic makes as it goes
2863 along. This can be useful for debugging purposes if something goes
2866 <listitem><code>metadata</code> stores the settings that you have made
2867 for this film: things like cropping, output format and so on.</listitem>
2869 <listitem><code>video</code> is where DCP-o-matic writes the DCP's
2870 video data as it encodes it.</listitem>
2872 <listitem><code>analysis</code> is used to keep the results of audio analysis runs.</listitem>
2874 <listitem><code>info</code> contains details of each video frame that
2875 DCP-o-matic has written so far. This is used when an encoding
2876 operation is interrupted and DCP-o-matic must resume it.</listitem>
2881 Following this is the DCP itself:
2882 <code>DCP-TEST_EN-XX_UK-U_51_2K_CSY_20130218_CSY_OV</code>. This
2883 contains some small XML files, which describe the DCP, and two large
2884 MXF files, which contain the DCP's audio and video data. It may also
2885 contain subtitles in either XML or MXF format. This folder
2886 (<code>DCP-TEST_EN-XX_...</code>) is what you should ingest, or pass
2887 to the cinema which is showing your DCP.
2893 <title>Loose ends</title>
2896 This chapter collects a few notes on bits of DCP-o-matic that do not fit elsewhere in the manual.
2900 <!-- ============================================================== -->
2902 <title>Resuming encodes</title>
2905 If you cancel a DCP encoding run half-way through, or your computer
2906 crashes... fear not. DCP-o-matic takes care to ensure that, in most
2907 cases, it can resume encoding from where it left off. When you
2908 re-start a DCP creation, using the same settings are a previous run,
2909 DCP-o-matic will first check that the existing picture frames are
2910 correct, and then resume from where it left off. The checking of
2911 existing frames does take some time, but it is much faster than
2912 running a full re-encode.
2916 This resumption is achieved by writing a digest (hash) to disk for
2917 every image frame that is written. On resumption, the existing MXF
2918 file for image data is read and its contents checked against the
projects / dcpomatic.git / blob