What you’ll check
- Whether the selected folder contains a complete DCP package.
- Whether referenced assets are present and available.
- Whether an encrypted DCP has a usable key.
- Whether verification reports package or asset problems.
Start here
Try loading the DCP again and note any error message DaCaPo displays.
The message can help identify whether the problem is related to package structure, missing media, encryption, or another validation issue.
Check the package files
Confirm that you are selecting the actual DCP folder and that the package files have not been moved, renamed, or deleted.
A DCP normally relies on package metadata such as the ASSETMAP, PKL, CPL, and the referenced essence files. If required files are unavailable, the package may not load correctly.
Check for missing assets
A CPL can reference picture, audio, subtitle, caption, Atmos, or other assets. Confirm that all required files are still present at the expected location.
For a Version File, also confirm that the related Original Version is available when the VF depends on assets from the OV.
Encrypted DCPs
When loading an encrypted DCP, DaCaPo first checks whether a suitable decryption key can be found automatically.
If no usable key is found, DaCaPo asks you to select a compatible key file. If you cancel that request, the Timeline is not loaded.
Supported key sources include DCPKey, KDM, DKDM, Digest XML, and other compatible key files.
Verify the DCP folder
If the reason is not obvious, run File > Verify DCP Folder... on the package.
Verification can identify structural, metadata, asset-reference, file, hash, media, encryption, and compliance problems.
Try loading again
After correcting the reported problem, load the DCP again.
If verification still reports a failure, resolve that issue before using the package for playback, editing, or delivery.