You spent months, maybe years, on your film. You’ve beaten off the competition to get your project selected for festival screening. Then it gets bounced. Not because of the story, the acting, or the cinematography, but because your DCP failed a technical check.
Almost every rejection can be traced back to a handful of recurring but fixable mistakes. DCP-Solutions has compiled a list of the errors we regularly fix, so you can catch them before your festival does.
The short answer: most DCP rejections aren’t about the film. They come from a mismatch somewhere in the technical chain: frame rate, channel map, standard, XML integrity, or a delivery detail that wasn’t triple-checked.
Always check the festival’s latest requirements before mastering and again before delivery, because specifications vary between festivals and venues. Need a second pair of eyes? Our DCP quality control and mastering service checks your package and prepares it for reliable cinema playback.
The 10 most common DCP errors that cause festival rejection
Even a professionally mastered film can fail if the package contains technical errors. These are the issues to check, from picture and sound to subtitles, keys, and package integrity.
1. Wrong frame rate or poor frame-rate conversion
Source footage at 23.976 fps that isn’t properly conformed to a DCI-legal rate (such as 24, 25, 30, 48, or 60 fps) causes judder, audio desync, or failed validation. Converting 23.976 fps to 24 fps needs the right workflow.
A proper conversion preserves picture timing and keeps audio in sync. Always confirm the required frame rate in the festival’s technical specification before encoding.
2. Audio channel mapping errors
Wrong channel order or channel count causes silence, reversed stereo, or QC failure. Dialogue can come from the wrong speaker, effects can vanish, and a channel can be left silent.
Typical culprits are missing centre-channel dialogue and incorrectly mapped surround or LFE channels. Check the final DCP itself rather than relying on the channel layout in your editing software.
3. Wrong aspect ratio, scaling, or container
Incorrect scaling into Flat (1998×1080, roughly 1.85:1) or Scope (2048×858, roughly 2.39:1) containers crops the picture or puts black bars in the wrong place. Don’t pick Flat or Scope because one sounds more appropriate: the choice should follow your actual picture dimensions and the festival or cinema specification.
4. Subtitle and closed caption errors
Timing drift, missing glyphs, and mismatches between closed captions and open subtitles are among the most common QC failures. Subtitles can also sit too low, overlap the picture incorrectly, disappear too quickly, or fall out of sync.
Requirements vary: some festivals want English subtitles even when the film isn’t aimed at an English-speaking market, while others specify open captions, closed captions, or separate version files. Check timing, safe areas, language, spelling, and readability before delivery.
5. Mixing Interop and SMPTE standards
These two DCP standards aren’t interchangeable, and mismatched subtitle schemas are the most common casualty. Don’t choose a standard based only on what your software offers. Check the festival’s current specification and ask the technical team if it’s unclear. Our guide to DCP vs DCDM vs ProRes explains SMPTE and Interop in more detail.
6. Broken or missing KDMs
A KDM tied to the wrong server or date window means a perfectly good DCP simply won’t play. Other common failures are an expired key and a key generated for the wrong version of the DCP. Our guide to what a KDM is covers how they work in full.
If the festival requests an encrypted DCP, get the correct server certificate information and test the key well before the screening date. If encryption isn’t required, an unencrypted DCP can make delivery simpler.
Need encrypted DCP and KDM support? Talk to us today.
7. Corrupted or incomplete file transfers
Large DCPs can silently truncate during transfer and still look complete in a file browser. A DCP isn’t one ordinary video file: it’s many assets and XML files working together, so a failed upload, interrupted copy, or damaged drive can break the whole package.
Validate the package after every transfer, and never assume a finished upload means an intact one. Checking file structure, hashes, UUIDs, and package integrity catches these problems before the festival receives your copy.
8. Invalid or malformed XML (CPL, PKL, ASSETMAP)
A single bad UUID or mismatched hash can make a cinema server reject the whole package. The CPL tells the cinema system how to assemble the composition, the PKL lists the package assets with their integrity information, and the ASSETMAP maps identifiers to files.
A hash mismatch can mean files were changed, replaced, or repackaged after validation. Errors in any of the three files can stop a server from ingesting or playing the package at all.
9. Multiple or ambiguous CPLs, and poor naming
Leftover test CPLs in a DCP folder can cause a server to play the wrong version. Vague names, duplicate packages, and unlabelled versions make it worse. The ISDCF naming convention carries useful technical information about a DCP and its intended presentation, so use clear names, clear out test versions, and tell the festival exactly which CPL to play.
10. Failing to follow the festival’s delivery spec
A technically perfect DCP can still be rejected for the wrong drive format (cinema servers generally read Linux-formatted drives), the wrong number of subtitle files, the wrong delivery method, or a missed deadline. Festival rules can cover encryption, subtitles, frame rate, resolution, naming, drive formatting, upload methods, and deadlines, and some festivals reserve the right to refuse or withdraw films that don’t meet them.
Treat the delivery spec as part of the mastering specification, not an administrative detail.
How to QC your DCP before sending it to a festival
Good quality control happens before the package leaves your hands. Download the latest festival specification, compare it with your DCP, and work through this checklist:
- confirm the required DCP standard (SMPTE or Interop) and resolution
- check frame rate and aspect ratio, including the Flat or Scope container
- verify audio channels, channel order, and every version
- check colour conversion and colour space
- review subtitles and closed captions for timing, language, and safe areas
- validate the CPL, PKL, ASSETMAP, and other XML, including UUIDs and hashes
- remove test CPLs, and check naming and metadata
- test any KDM against the correct server certificate and date window
- confirm the transfer is complete and the package is intact
- check the drive format, delivery method, and deadline against the festival spec
- run a playback test before the deadline.
Where you can, test in a real cinema. Desktop playback is useful for early checks, but it can’t reproduce every projector, server, and sound-system combination a festival uses. At DCP-Solutions, we test every DCP on playback software and in the screening room.
Why professional DCP mastering helps
We follow each festival’s spec to the letter, and test every package before it goes out. Professional DCP mastering brings encoding, packaging, and quality control into one workflow, so picture sizing, colour conversion, audio mapping, subtitles, metadata, package structure, and key requirements are all checked before delivery. We do all that and more before we hit submit.
Pricing depends on running time and complexity. DCP-Solutions currently lists 2K unencrypted DCPs from £70 for under 15 minutes to £290 for 150–180 minutes, and subtitles, 4K, encryption, extra versions, and physical delivery can add to that. You can also see how long DCP mastering takes when planning around a deadline.
Secure your festival screening: contact DCP-Solutions today.
Final thoughts
A DCP rejection can feel like a small technical problem, but it becomes a major one when the screening slot is fixed and there’s no time left to troubleshoot. Most rejections aren’t about the film. They’re about a mismatch somewhere in the technical chain, or a delivery detail that wasn’t triple-checked.
If you’d like to understand the basics first, start with what a DCP is. Then get your package checked while there’s still time to fix it.
Get your DCP checked before festival rejection strikes.
Frequently Asked Questions
What is the most common DCP error?
Frame-rate conversion, audio channel mapping, subtitles, and delivery-spec mismatches are among the issues we fix most often. In almost every case the cause is a mismatch somewhere in the technical chain rather than a problem with the film itself.
How do I check a DCP before sending it to a festival?
Compare the DCP against the festival’s latest specification, validate the XML files and package integrity, verify audio, subtitles, and frame rate, test any KDM, and run a playback test, ideally in a real cinema.
Can a DCP play correctly and still be rejected?
Yes. A technically valid DCP can still be rejected for the wrong drive format, the wrong number of subtitle files, an unsupported delivery method, or a missed deadline.
Should I use Interop or SMPTE for a festival DCP?
Follow the festival’s specification. SMPTE is the modern default, while Interop is the legacy standard that still appears at some venues. If the spec doesn’t say, ask the festival’s technical team.
Do festivals require an encrypted DCP and a KDM?
Some do and others don’t. If encryption is required, you’ll need the correct server certificate information and a tested KDM. If it isn’t, an unencrypted DCP can simplify delivery.
Does a 23.976 fps film need converting for a DCP?
Usually, yes. 23.976 fps footage generally needs to be conformed to an approved rate such as 24 fps, using a workflow that keeps picture and sound in sync, before the DCP is created.