DaCaPo

Verification

Verify After Export

Verify After Export starts DCP verification automatically after DaCaPo completes an export.

This creates a consistent mastering workflow in which the package is exported, checked, reviewed, and only then approved for delivery.

What you’ll learn

  • Why verification should be part of every final export.
  • How to enable Verify After Export.
  • What happens when the export finishes.
  • How to review the automatic verification results.
  • When to correct and export again.
  • How verification affects total export time.

Why use Verify After Export?

A successful export means DaCaPo completed the package-writing process. It does not remove the need to check the finished DCP.

Verify After Export connects the two stages into one controlled workflow:

  1. Prepare and review the Timeline.
  2. Export the DCP.
  3. Verify the completed package automatically.
  4. Review the results.
  5. Approve or correct the delivery.

Automating the verification step reduces the risk of forgetting it during a busy delivery.

Verify After Export is useful for individual DCP exports and Multi-CPL Package exports.

Before you begin

Verify After Export does not replace Timeline validation before export. Resolve blocking errors and review warnings before creating the package.

Confirm:

  • The correct Timeline or Package is selected.
  • The destination has enough free space.
  • All source media is online.
  • The OV/VF choice is correct.
  • Encryption is configured as intended.
  • The generated package name is correct.
Step 1

Enable Verify After Export

Open the DCP export settings and enable Verify After Export.

Leave the option enabled for final masters unless there is a specific reason to perform verification separately.

Verify after export option in DaCaPo
Step 2

Start the export

Start the export after reviewing the package settings.

DaCaPo creates the package metadata and writes or reuses the required picture, audio, subtitle, caption, and auxiliary assets.

Do not disconnect the destination or source storage while the export is running.

Step 3

Automatic verification starts

After the DCP export completes successfully, DaCaPo begins verification of the newly created package.

The verification analyses the package that was actually written to the destination, not only the Timeline that was used as the source.

Depending on the selected options, DaCaPo can check package structure, XML metadata, asset references, hashes, MXF files, subtitles, audio, encryption information, markers, and JPEG2000 picture data.

For an explanation of the individual checks, see Verify a DCP Folder.
Step 4

Review the results

When verification is complete, review all reported errors, warnings, recommendations, and informational results.

Errors

Correct errors before delivery. They can indicate broken references, missing assets, invalid metadata, hash mismatches, or other conditions that can prevent reliable playback.

Warnings

Warnings may not block delivery, but they should be understood and accepted deliberately.

Do not treat a zero-error result as the only approval criterion. Review the warnings and perform playback QC as well.

Correct the problem and export again

If verification reports a problem caused by the Timeline or export settings, return to the project, make the correction, and export again.

Do not modify XML or MXF files manually inside the finished DCP unless the workflow specifically requires it and the complete package is regenerated correctly.

Verify the corrected export again before delivery.

Performance and completion time

Verify After Export increases the total time before a package is ready for delivery because DaCaPo must read the completed DCP after writing it.

Hash calculation requires reading complete assets. Exhaustive JPEG2000 checking additionally decodes every picture frame.

The total time depends on:

  • DCP duration.
  • Picture resolution and frame rate.
  • Storage read speed.
  • Whether assets are local, external, or network-based.
  • Whether exhaustive JPEG2000 checking is enabled.
The additional time is normally small compared with the cost of a failed cinema delivery or a repeated transfer.

Recommended mastering workflow

  1. Review and validate the Timeline.
  2. Export to the final delivery destination.
  3. Run Verify After Export.
  4. Review all results.
  5. Perform playback QC.
  6. Create KDMs when required.
  7. Deliver the DCP and keep the verification report.

If the DCP is copied to another drive after verification, verify the copied delivery as well.

Common problems

Verification does not start

Confirm that Verify After Export was enabled and that the DCP export completed successfully.

The export succeeded but verification failed

Review the reported issue. The finished package may contain a metadata, asset, hash, or storage problem even though the write operation completed.

Verification takes longer than expected

Hash checks and JPEG2000 decoding are storage- and processor-intensive. Check the verification options and destination performance.

The package was copied after verification

Verify the copy that will actually be delivered.

The DCP passes but playback QC reveals a problem

Correct the creative or presentation problem, export again, and repeat verification.

Related guides

Manual reference: Export Timeline; Export Package; Verify After Export; Verification Results; Issues.

Reviewed against: DaCaPo User Manual 0.9.2, July 2026.