%dbcent; %extensions; ]> CarlHetherington Hello, and welcome to DCP-o-matic!

DCP-o-matic is a program to generate Digital Cinema Packages (DCPs) from DVDs, Blu-Rays, video files such as MP4 and AVI, or still images. The resulting DCPs will play on modern digital cinema projectors. You might find it useful to make DVDs easier to present, to encode independently-shot feature films, or to generate local advertising for your cinema.

DCP-o-matic is licensed under the GNU GPL.

This manual uses icons from the Tango Desktop Project, with thanks.

To install DCP-o-matic on Windows, download the installer from http://dcpomatic.com/ and double-click it. Click through the installer wizard, and DCP-o-matic will be installed onto your machine. If you are using a 32-bit version of Windows, you will need the 32-bit installer. For 64-bit Windows, either installer will work, but I suggest you used the 64-bit version as it will allow DCP-o-matic to use more memory. You may find that DCP-o-matic crashes if you run many parallel encoding threads (more than 4) on the 32-bit version.

DCP-o-matic will run on Mac OS X version 10.6 (Snow Leopard) and higher. To install it, download the DMG from http://dcpomatic.com/ and double click to open it. Then drag the DCP-o-matic icon to your Applications folder or wherever else you would like to install it.

You can install DCP-o-matic on Ubuntu 12.04 (‘Precise Pangolin’), 12.10 (‘Quantal Quetzal’), 13.04 (‘Raring Ringtail’) or 13.10 (‘Saucy Salamander’) using .deb packages: download the appropriate package from http://dcpomatic.com/ and double-click it. Ubuntu will install the necessary bits and pieces and set DCP-o-matic up for you.

Packages are also available for Debian 7 (squeeze) from http://dcpomatic.com/.

Packages for Arch Linux are available from https://aur.archlinux.org/packages/dcpomatic/, thanks to Stefan Karner.

Installation on non-Ubuntu Linux is currently a little involved, as there are no packages available (yet); you will have to compile it from source. If you are using a non-Ubuntu distribution, do let me know via the mailing list and I will see about building some packages. The following dependencies are required: FFmpeg libsndfile OpenSSL libopenjpeg ImageMagick Boost libssh GTK (on Linux) wxWidgets libquickmail libxml++ xmlsec curl libzip libdcp libcxml Once you have installed the development packages for the dependencies, download the source code from http://dcpomatic.com/, unpack it and run the following commands from inside the source directory: ./waf configure ./waf build sudo ./waf install With any luck, this will build and install DCP-o-matic on your system. To run it, enter: dcpomatic in a shell.

In this chapter we will see how to create a video DCP using DCP-o-matic. We will gloss over the details and look at the basics.

Let's make a very simple DCP to see how DCP-o-matic works. First, we need some content. Download the low-resolution trailer for the open movie Sintel from their website. Generally, of course, one would want to use the highest-resolution material available, but for this test we will use the low-resolution version to save everyone's bandwidth bills. Now, start DCP-o-matic and its window will open. First, we will create a new ‘film’. A ‘film’ is how DCP-o-matic refers to some pieces of content, along with some settings, which we will make into a DCP. DCP-o-matic stores its data in a folder on your disk while it creates the DCP. You can create a new film by selecting New from the File menu, as shown in .

This will open a dialogue box for the new film, as shown in .

In this dialogue box you can choose a name for the film. This will be used to name the folder to store its data in, and also as the initial name for the DCP itself. You can also choose whereabouts you want to create the film. In the example from the figure, DCP-o-matic will create a folder called ‘DCP Test’ inside my home folder (carl) into which it will write its working files.

The next step is to add the content that you want to use. DCP-o-matic can make DCPs from multiple pieces of content, but in this simple example we will just use a single piece. Click the Add file(s)... button, as shown in , and a file chooser will open for you to select the content file to use, as shown in .

Select your content file and click Open. In this case we are using the Sintel trailer that we downloaded earlier. When you do this, DCP-o-matic will take a look at your file. After a short while (when the progress bar at the bottom right of the window has finished), you can look through your content using the slider to the right of the window, as shown in .

Dragging the slider will move through your video. You can also click the Play button to play the content back. Note that there will be no sound, and playback might not be entirely accurate (it may be slightly slower or faster than it should be, for example). This player is really only intended for brief inspection of content; if you need to check it more thoroughly, use another player such as Totem, mplayer or VLC.

In most cases, some adjustments would be made to DCP-o-matic's settings once the content has been added. For our simple test, however, the default values will suffice, so we can go straight onto making the DCP. Choose Make DCP from the Jobs menu. 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 .

When it has finished, the DCP will end up on your disk inside the film's folder. You can then copy this to a projector via a USB stick, hard-drive or network connection. See for details about the files that DCP-o-matic creates. Alternatively, if you have a projector or TMS that is accessible via SCP across your network, you can upload the content directly from DCP-o-matic. See the preferences in .

DCP-o-matic can also be used to create DCPs of one or more still images, perhaps for an advertisement or an on-screen announcement. This chapter shows you how to do it. As with video DCPs, the first step is to create a new ‘Film’; select New from the File menu and the new film dialogue will open as shown in .

Enter a name and click OK. Now we need to add the content. As before, click Add file(s).... For our example, we will add a single image file, as shown in .

As with video DCPs, most of the default settings will be fine for a simple test. The one thing that you might wish to change is the length of the still. Select the Timing tab and you will see a Length setting, as shown in .

This length is a ‘timecode’: it consists of four numbers. The first is hours, the second minutes, the third seconds, and the fourth frames. Enter the duration that you want and then click Set. Finally, as with video, you can choose Make DCP from the Jobs menu to create your DCP. This will be much quicker than creating a video DCP, as DCP-o-matic only needs to encode a single frame which it can then repeat. The previous chapters showed DCP generation using the default settings. DCP-o-matic offers a range of features to adjust the content that goes into your DCP, and this chapter describes those features in detail.

At the top of the Content tab is a list of the content that will go into our DCP. There can be as many pieces of content as you like, and they can be of the following types: Movie — a file containing some video, probably some audio and possibly some subtitles; for example, a MOV, MP4 or VOB. Sound — a file containing one or more channels of audio; for example, a WAV or AIFF file. Still image — a file containing a single still image; for example, a JPEG, PNG or TIFF file. Moving image — a directory containing many still images which should be treated as the frames of a video. To add one or more movie, sound or still-image files, select Add file(s)... and choose them from the selector. To add a directory of images, choose Add directory... and do similar. You can remove a piece of content by clicking on its name and then clicking the Remove button.

Below the content list are the controls to set content properties. To adjust the properties for a piece of content, click its name in the content list. The content property controls will then become active for that piece of content. The content properties are split up into four sections: Video, Audio, Subtitles and Timing. Not all of these sections will be active for all content types. The controls in each section are described below.

The Video tab controls properties of the image, as shown in .

The first option on this tab is the ‘type’ of the video. This specifies how DCP-o-matic should interpret the video's image. 2D is the default; this just takes the video image as a standard 2D frame. The 3D left/right option tells DCP-o-matic to interpret the frame as a left-right pair, as shown in .

Alternatively the 3D top/bottom option tells DCP-o-matic to see the frame as a top-bottom pair, as shown in .

The ‘filters’ settings allow you to apply various video filters to the image. These may be useful to try to improve poor-quality sources like DVDs. You can set up the filters by clicking the Edit button next to the filters entry in the setup area of the DCP-o-matic window; this opens the filters selector as shown in .

After changing the filters setup, you will need to regenerate the DCP to see the effect on the cinema screen. The preview in DCP-o-matic will update itself whenever filters are changed, though of course this image is much smaller and of lower resolution than a projected image!

The ‘crop’ settings can be used to crop your content, which can be used to remove black borders from round the edges of DVD images, for example. The specified number of pixels will be trimmed from each edge, and the content image in the right of the window will be updated to show the effect of the crop. The Scale to option governs the shape that DCP-o-matic will scale the content's image into. Select the aspect ratio that your content should be presented in.

At the bottom of the video tab is a short description of what will happen to your video with the current settings. In the example of , DCP-o-matic is telling you that the video file is 1920x1080 pixels (which is a ratio of 1.78:1). Since the controls specify ‘Flat’ for the ratio, DCP-o-matic scales the content image to 1998x1080, which is the DCI flat resolution at 2K. This description also gives the frame rate of the content and what will happen to it when it is played at the DCP's frame rate.

The Audio tab controls properties of the image, as shown in .

The Show Audio button will instruct DCP-o-matic to examine the audio in your content and plot a graph of its level over time. This can be useful for getting a rough idea of how loud the sound will be in the cinema auditorium. A typical plot is shown in

The plot gives the audio level (vertical axis, in dB) with time (horizontal axis). 0dB represents full scale, so if there is anything near this you are in danger of clipping the projector's audio outputs. There are two plot types: the peak level and the RMS, which can be shown or hidden using the check-boxes on the right hand side of the window. The channel check-boxes will show or hide the plot(s) for the corresponding channels in the DCP. The smoothing slider applies a variable degree of temporal smoothing to the plots, which can make them easier to read in some cases. Obviously the audio plot is no substitute for listening in an auditorium, but it can be useful to get levels in the right rough area.

The section at the bottom of the audio tab is the ‘audio map’. This governs how sound from the content will be arranged in the DCP. Down the left-hand side of the map is the list of audio channels in the currently-selected piece of content. Along the top is each channel in the DCP. A checked box means that the corresponding content channel will be copied into the corresponding DCP channel. Consider, for example, the case in .

Here, we have two channels in the source which are mapped to left and right, respectively, in the DCP. If we modify that as in

we now have the content's streams mapped to left and right and also mixed together and placed in the DCP's centre channel.

As a final example, the map in shows the mapping of a 5.1 source into a 5.1 DCP.

‘Audio Gain’ is used to alter the volume of the soundtrack. The specified gain (in dB) will be applied to each sound channel of your content before it is written to the DCP. If you use a sound processor that DCP-o-matic knows about, it can help you calculate changes in gain that you should apply. Say, for example, that you make a test DCP and find that you have to run it at volume 5 instead of volume 7 to get a good sound level in the screen. If this is the case, click the Calculate... button next to the audio gain entry, and the dialogue box in will open.

For our example, put 5 in the first box and 7 in the second and click OK. DCP-o-matic will calculate the audio gain that it should apply to make this happen. Then you can re-make the DCP (this will be reasonably fast, as the video data will already have been done) and it should play back at the correct volume with 7 on your sound-rack fader. Current versions of DCP-o-matic only know about the Dolby CP650 and CP750. If you use a different sound processor, and know the gain curve of its volume control, get in touch. Audio Delay is used to adjust the synchronisation between audio and video. A positive delay will move the audio later with respect to the video, and a negative delay will move it earlier. The Audio Stream option allows you to select the audio stream to use, if the content contains more than one. There might be different soundtrack languages, for example.

The subtitles tab contains settings related to subtitles in your content, as shown in .

DCP-o-matic will extract subtitles from the content, if present, and they can be ‘burnt into’ the DCP (that is, they are included in the image and not overlaid by the projector). Note that DVD and Blu-Ray subtitles are stored as bitmaps, so it is not possible (automatically) to use non-burnt-in subtitles with these sources. Select the With Subtitles check-box to enable subtitles. The offset control moves the subtitles up and down the image, and the scale control changes their size. All being well, future versions of DCP-o-matic will include the option to use text subtitles (as is the norm with most professionally-mastered DCPs).

This chapter describes the settings that apply to the whole DCP. The controls for these settings are in the DCP tab of the main window, as shown in .

The first thing here is the name. This is generally set to the title of the film that is being encoded. If Use DCI name is not ticked, the name that you specify will be used as-is for the name of the DCP. If Use DCI name is ticked, the name that you enter will be used as part of a DCI-compliant name. Underneath the name field is a preview of the name that the DCP will get. To use a DCI-compliant name, tick the Use DCI name check-box. The DCI name will be composed using details of your content's soundtrack, the current date and other things that can be specified in the DCI name details dialogue box, which you can open by clicking on the Details button. If the DCP name is long, it may not all be visible. You can see the full name by hovering the mouse pointer over the partial name. The Container option sets the ratio of the image in the DCP. If this ratio is different to the ratio used for any content, DCP-o-matic will pad the content with black. In simple cases this should be set to the same ratio as that for the the primary piece of video content. Alternatively, you might want to pillarbox a small format into a Flat container: in this case, select the small format for the content's ratio and ‘Flat’ for the DCP. Next up is the content type. This can be ‘feature’, ‘trailer’ or whatever; select the required type from the drop-down list. The Frame Rate control sets the frame rate of your DCP. This can be a little tricky to get right. Ideally, you want it to be the same as the video content that you are using. If it is not the same, DCP-o-matic must resort to some tricks to alter your content to fit the specified frame rate. Frame rates are discussed in more detail in . The Encrypted check-box will set whether the DCP should be encrypted or not. If this is ticked, the DCP will require a KDM to play back. Encryption is discussed in . The Use best button sets the DCP video frame rate to what DCP-o-matic thinks is the best given the content that you have added. The Audio Channels control sets the number of audio channels that the DCP will have. If the DCP has any channels for which there is no content audio they will be replaced by silence. The 3D button will set your DCP to 3D mode if it is checked. A 3D DCP will then be created, and any 2D content will be made 3D compatible by repeating the same frame for both left and right eyes. A 3D DCP can be played back on many 3D systems (e.g. Dolby 3D, Real-D etc.) but not on a 2D system. The Resolution tab allows you to choose the resolution for your DCP. Use 2K unless you have content that is of high enough resolution to be worth presenting in 4K. The JPEG2000 bandwidth; setting changes how big the final image files used within the DCP will be. Larger numbers will give better quality, but correspondingly larger DCPs. The bandwidth can be between 50 and 250 megabits per second (Mbit/s). The Standard option specifies which of the two DCP standards DCP-o-matic should use. If in doubt, use SMPTE (the more modern of the two). Finally, the scaler is the method that will be used to scale up your content to the required size for the DCP, if required. Bicubic is a fine choice in most situations. It is not required that DCPs be encrypted, but they can be. This chapter discusses the basic principles of DCP encryption, and how DCP-o-matic can create encrypted DCPs and KDMs for them.

DCPs can be encrypted. This means that the picture and sound data are encoded in such a way that only cinemas ‘approved’ by the DCP's creators can read them. In particular, this means copies of the DCP can be distributed by insecure means: if an ne'er-do-well called Mallory obtains a hard drive containing an encrypted DCP, there is no way that he can play it. Only those cinemas who receive a key delivery message (KDM) can play the DCP.

This section attempts to summarise how DCP encryption works. You can skip it if you like. You may need some knowledge of encryption methods to understand it. We suppose that we are trying to distribute a DCP to Alice's cinema, without a troublemaker called Mallory being able to watch it himself. There are two main families of encryption techniques. The first, symmetric-key encryption, allows us to encode some data using some numeric key. After encoding, no-one can decode the data unless they know the key. The first step in a DCP encryption is to encode its data with some key using symmetric-key encryption. The encrypted DCP can then be sent anywhere, safe in the knowledge that even if Mallory got hold of a copy, he could not decrypt it. Alice, however, needs to know the key so she can play the DCP in her cinema. A simple approach might be for us to send Alice the key. However, if Mallory can intercept the DCP, he might also be able to intercept our communication of the key to Alice. Furthermore, if Alice happened to know Mallory, she could just send him a copy of the key. The clever bit in DCP encryption requires the use of public-key encryption. With this technique we can encrypt a block of data using some ‘public’ key. That data can then only be decrypted using a different ‘private’ key. The private and public keys are related mathematically, but it is extremely hard (or rather, virtually impossible) to derive the private key from the public key. Public-key encryption allows us to distribute the DCP's key to Alice securely. The manufacturer of Alice's projector generates a public and private key. They hide the private key deep inside the bowels of the projector (inside an integrated circuit) where no-one can read it. They then make the public key available to anyone who is interested. We take our DCP's symmetric key and encrypt it using the public key of Alice's projector. We send the result to Alice over email (using a format called a Key Delivery Message, or KDM). Her projector then decrypts our message using its private key, yielding the magic symmetric key which can decrypt the DCP. If is fine if Mallory intercepts our email to Alice, since the only key which can decrypt the message is the private key buried inside Alice's projector. The projector manufacturer is very careful that no-one ever finds out what this key is. Our DCP is secure: only Alice can play it back, since only her projector knows the key (even Alice does not).

There are two steps to distributing an encrypted DCP. First, the DCP's data must be encrypted, and secondly KDMs must be generated for those cinemas that are allowed to play the DCP. The first part is simple: ticking the Encrypted box in the DCP tab of DCP-o-matic will encrypt the DCP using a random key that DCP-o-matic generates. The key will be written to the film's metadata file, so that should be kept secure. A DCP that is generated with the Encrypted box ticked will not play on any projector as-is (it will be marked as ‘locked’, or whatever the projector manufacturer's term is). The second part is to generate KDMs for the cinemas that you wish to allow to play your DCP. This is done using the Make KDMs option on the Jobs menu. This will open the KDM dialogue box, as shown in .

In order to generate KDMs for a particular projector, you need to know its certificate. These are usually made available by the projector manufacturers as text files with a .pem extension. DCP-o-matic can store these certificates to make life easier. It stores details of cinemas and screens within those cinemas. Each screen has a certificate for its projector. DCP-o-matic can generate KDMs for any screens that it knows about. To add a cinema, click Add Cinema.... This opens a dialogue box into which you can enter the cinema's name, and optionally an email address. This email address can be used to get DCP-o-matic to deliver KDMs via email, but it is optional. Once you have added a cinema, select it by clicking on its name, then click Add Screen.... The resulting dialogue allows you to enter a name for the screen and load in its certificate from a file. The certificate should be in SHA256 PEM format. Once you have set up all the screens that you need KDMs for, DCP-o-matic can generate KDMs for the last DCP that you generated for the currently-loaded film. Select the cinemas and/or screens that you want KDMs for and fill in the start and end dates and times. Finally, choose what you want to do with the KDMs. They can be written to disk, to a location that you can specify by clicking Browse. Alternatively, if you choose Send by email the KDMs will be zipped up and emailed to the appropriate cinema email addresses. Click OK to generate the KDMs.

DCP-o-matic provides a few preferences which can be used to modify its behaviour. This chapter explains those options.

The preferences dialogue is opened by choosing Preferences... from the Edit menu. The dialogue is split into five tabs.

The miscellaneous tab is shown in .

If you tick the Set Language checkbox and choose a language from the list, that language will be used for DCP-o-matic. You will need to restart DCP-o-matic to see the new language. The translations for DCP-o-matic have been contributed by helpful users. If your language is not on the last, head to the DCP-o-matic website to read about how to contribute a translation.

When DCP-o-matic is encoding DCPs it can use multiple parallel threads to speed things up. Set this value to the number of threads DCP-o-matic should use. This should normally be the number of processors (or processor cores) in your machine. DCP-o-matic will try to set this up correctly when you run it for the first time.

DCP-o-matic can send KDMs (see ) to cinemas (or anywhere else) via email. To make this work, enter a suitable outgoing mail (SMTP) server and ‘from’ address for these emails.

The next few options allow you to set up default values for several properties of new films that you create.

The colour conversions tab is shown in .

As part of the encoding process, DCP-o-matic has to convert the colour space of the source files that you use into XYZ, the colour space used by the DCI standard. Colour conversion is discussed in more detail in a separate document colour.pdf. These preferences control a list of presets which are suitable for converting from common input colour spaces to XYZ.

The metadata tab is shown in .

This allows you to set up a couple of identifiers that are written into the DCP. The default values should cause no problems.

The TMS tab (shown in ) gives some options for specifying details about your theatre management system (TMS). If you do this, and your TMS accepts SSH connections, you can upload DCPs directly from DCP-o-matic to the TMS using the Send DCP to TMS option in the Jobs menu.

TMS IP address should be set to the IP address of your TMS, TMS target path to the place that DCPs should be uploaded to (which will be relative to the home directory of the SSH user). Finally, the user name and password are the credentials required to log into the TMS via SSH.

The KDM email is shown in .

This is a template for the email that is used to send KDMs out to cinemas. You can change it to say whatever you like. The ‘magic’ string $CPL_NAME will be replaced by DCP's title.

In an ideal world, a DCP would be created using content at the same video frame and audio sampling rates as the DCP. This is not, however, always possible.

There are some limitations to video and audio rates in DCPs. This is complicated by the fact that not all projectors will play DCPs at the same rates. It is possible to create a DCP which one projector will play fine, but another (of a different type) will refuse to play, or even refuse to ingest.

The only rates that are (pretty much) guaranteed to work on all DCI projectors is 24 frames per second (fps) for video and 48kHz or 96kHz for audio. If you are sending your DCPs to unknown places it wise to consider using these rates if at all possible.

Many projectors now in the wild support additional video frame rates: 25, 30 and 48 fps.

DCP-o-matic has a few tricks to allow you to use content that is not in one of the ‘approved’ rates. Audio is easy: DCP-o-matic can resample to 48kHz from any source rate with minimal loss in quality. Video rate conversion is harder. DCP-o-matic's basic strategy to deal with a non-supported content rate is to run it at the wrong speed, and to adjust the audio to keep it in sync. Let us consider the example of a 25fps source for which you want to create a 24fps DCP. DCP-o-matic will put the frames from the source directly into the DCP without modification, but will tell the projector to play them back at 24fps. This means that the DCP's video will run slightly slower than the original. If DCP-o-matic did nothing else, the result of this would be that the audio would be running at the original speed with the video running slowly. Hence the audio would drift slowly out of sync. To avoid this, DCP-o-matic also resamples the audio such that the projector will play it too fast by the same amount. Hence it will sound slightly different but will remain in sync with the video. For very low or high frame rates, DCP-o-matic can also skip or duplicate frames.

The Frame Rate control in the DCP tab sets the video frame rate that the DCP will use. Clicking Use best sets the rate to what DVD-o-matic thinks is the best for your content. With this button, DCP-o-matic assumes that the whole range of frame rates (24, 25, 30 and 48fps) are allowable. After this, the Video tab for each piece of content will give a summary of what DCP-o-matic is doing with that content.

One way to increase the speed of DCP encoding is to use more than one machine at the same time. An instance of DCP-o-matic can offload some of the time-consuming JPEG2000 encoding to any number of other machines on a network. To do this, one ‘master’ machine runs DCP-o-matic, and the ‘server’ machines run a small program called dcpomatic_server. The master and server machines do not need to be the same type, so you can mix Windows PCs, Macs and Linux machines as you wish.

There are two options for the encoding server; dcpomatic_server_cli, which runs on the command line, and dcpomatic_server, which has a simple GUI. The command line version is well-suited to headless servers, especially on Linux, and the GUI version works best on Windows where it will put an icon in the system tray. To run the command line version, simply enter: dcpomatic_server_cli at a command prompt. If you are running the program on a machine with a multi-core processor, you can run multiple parallel encoding threads by doing something like: dcpomatic_server_cli -t 4 to run 4 threads in parallel. To run the GUI version on windows, run the ‘DCP-o-matic encode server’ from the start menu. An icon will appear in the system tray; right-click it to open a menu from whence you can quit the server or open a window to show its status. If you would rather not bother installing DCP-o-matic on your server computers, the other option is to use the live-CD image that you can download from the DCP-o-matic web site. Either burn the image to CD, or write it to a USB stick (using something like unetbootin). Boot a PC from the CD or USB stick and it becomes a DCP-o-matic server without touching your standard operating system install.

DCP-o-matic periodically looks on the local network for servers. Any that it finds are given work to do during encodes. Selecting Encoding Servers from the Tools menu brings up a window which shows that servers that DCP-o-matic has found.

DCP-o-matic does not mind if servers come and go; if a server disappears, DCP-o-matic will stop sending work to it, and will check it every minute or so in case it has come back online. You will probably find that using a 1Gb/s or faster network will provide a significant speed-up compared to a 100Mb/s network.

DCP-o-matic generates a number of files as it makes a DCP. shows the files that might be generated after you have created a DCP for a film called ‘DCP Test’.

The DCP Test folder is the one that you specify when you select the New Film option from DCP-o-matic's menu. Everything is stored inside this folder. DCP-o-matic generates some working files as it goes along. These are as follows: log is a list of notes that DCP-o-matic makes as it goes along. This can be useful for debugging purposes if something goes wrong. metadata stores the settings that you have made for this film: things like cropping, output format and so on. video is where DCP-o-matic writes the DCP's video data as it encodes it. analysis is used to keep the results of audio analysis runs. info contains details of each video frame that DCP-o-matic has written so far. This is used when an encoding operation is interrupted and DCP-o-matic must resume it. Following this is the DCP itself: DCP-TEST_EN-XX_UK-U_51_2K_CSY_20130218_CSY_OV. This contains some small XML files, which describe the DCP, and two large MXF files, which contain the DCP's audio and video data. This folder (DCP-TEST_EN-XX_...) is what you should ingest, or pass to the cinema which is showing your DCP. This chapter collects a few notes on bits of DCP-o-matic that do not fit elsewhere in the manual.

If you cancel a DCP encoding run half-way through, or your computer crashes... fear not. DCP-o-matic takes care to ensure that, in most cases, it can resume encoding from where it left off. When you re-start a DCP creation, using the same settings are a previous run, DCP-o-matic will first check that the existing picture frames are correct, and then resume from where it left off. The checking of existing frames does take some time, but it is much faster than running a full re-encode. This resumption is achieved by writing a digest (hash) to disk for every image frame that is written. On resumption, the existing MXF file for image data is read and its contents checked against the hashes.