Making a DCP on a Budget

For years, "you need a DCP" was code for "you need to pay a post facility," and the cost — often several hundred to a couple thousand dollars per version — put cinema and festival screenings out of reach for a lot of indies. That barrier is gone. Free, open-source software now lets you convert your master into a fully valid, cinema-playable DCP on your own computer, and the standard tool the indie world uses is DCP-o-matic — free, cross-platform, actively maintained, and genuinely capable of producing DCPs that play in real cinemas. Making a DCP with it isn't difficult; it's mostly a matter of feeding it your correct master and setting a handful of parameters properly, then letting it churn. This chapter walks the process at a level that demystifies it. (It's not a click-by-click manual — the software changes and has good documentation — but a map of what you're doing and the choices that matter, so you approach it with confidence instead of dread.)

The DCP-making process

Turning your master into a DCP, step by step:

• Start from a correct master. Feed it your best-quality master (from Chapter 2) at the right resolution and frame rate. Garbage in, garbage out — a DCP can't fix a bad source, so get the master right first.
• Set the container & resolution. Choose the DCP container size — 2K (2048×1080) or 4K (4096×2160) — and the aspect ratio (Flat 1.85 or Scope 2.39). Match what your festival/cinema specified. Most indie DCPs are 2K, which plays everywhere.
• Set the frame rate. Use your film's actual frame rate (commonly 24fps for DCP). Mismatches cause playback problems. DCP frame-rate support is specific, so confirm your rate is a valid DCP rate.
• Handle color conversion. The software converts your Rec.709 master to the cinema's DCI-P3/XYZ color. Choose the correct input color space so your grade translates faithfully — getting this wrong makes the DCP look washed out or off.
• Configure audio. Map your audio to the correct DCP channels (e.g. stereo or 5.1 layout). Make sure left/right/center and surrounds land in the right channels — cinema audio routing is specific.
• 2D, unencrypted, single reel — keep it simple. For most festival submissions, an unencrypted 2D DCP is what you want (encryption needs KDMs — next chapter — and festivals usually prefer unencrypted). Then let it encode. It takes time; a feature can run many hours.

Get the inputs right and let it run

The mindset that makes DCP creation painless is realizing that the tool does the hard technical work; your job is to give it correct inputs and settings. You're not hand-encoding JPEG2000 or writing XML recipe files — DCP-o-matic does all of that. What you control is: the right master in, the right container/resolution/aspect, the right frame rate, the correct color-space conversion, and the correct audio mapping. Get those right and the output is a valid DCP; get one wrong and you get a DCP that's the wrong shape, wrong color, or won't play. So slow down on the settings and match them to your target's spec exactly, then be patient with the long encode. A few practical realities. DCP encoding is slow and CPU-heavy — budget hours, not minutes, for a feature, and don't do it the night before a deadline. DCPs are large — often tens to over a hundred gigabytes — so you need the drive space, and you'll deliver it on a physical drive (usually a specifically-formatted CRU/EXT drive for cinemas, though many festivals now accept upload). Name it properly using DCP naming conventions (the software helps), because cinema servers read those names. And most importantly — which is the entire next chapter — you must test the finished DCP before you send it, because a DCP that fails at a screening with a live audience is a nightmare, and a surprising number of home-made DCPs have small errors that only show up on playback. But none of this is beyond a determined solo filmmaker. The first DCP you make will feel like an achievement; the second will feel routine. The point of this chapter is simply this: a required DCP is no longer a reason to pay a lab or skip a festival — it's an afternoon (plus a long render) with free software. You made the film; you can make the DCP. Next, we make sure it actually works, and cover encryption and KDMs.