Help fixing errors

Anything and everything to do with DCP-o-matic.
jessemonday
Posts: 1
Joined: Tue Oct 06, 2026 1:35 pm

Help fixing errors

Post by jessemonday »

I exported my DCP through Resolve. I transcoded the DCP with DCPomatic but I'm still getting these errors in the verifier. I can't find a straight answer to fix these anywhere.


* <MainSoundConfiguration> has an invalid value: MainSoundConfiguration has 0 channels but sound assets have 6
* There should be a FFOC (first frame of content) marker.
* There should be a LFOC (last frame of content) marker.
* The CPL 4680d8ff-f159-4b8f-8eb3-ac4346349e7f has no <VersionNumber> in its <CompositionMetadataAsset>.
* The CPL 4680d8ff-f159-4b8f-8eb3-ac4346349e7f has no <ExtensionMetadata> in its <CompositionMetadataAsset>.
carl
Site Admin
Posts: 3024
Joined: Thu Nov 14, 2013 2:53 pm

Re: Help fixing errors

Post by carl »

Hi, I would expect a transcode with DCP-o-matic to fix at least some of those errors. Can you describe what you did in DCP-o-matic? Sending the XML files from the DCP with the errors to carl@dcpomatic.com would also be helpful.
Carsten
Posts: 3127
Joined: Tue Apr 15, 2014 9:11 pm
Location: Germany

Re: Help fixing errors

Post by Carsten »

Maybe you just saved the project in DCP-o-matic and expcted these issues to be fixed in the preexisting DCP?
But they are not 'applied' to the DCP by saving the project, you definitely need to create a new DCP for your changes to take effect.
You don't need to transcode though (re-encoding J2K). If you don't change image parameters (like color conversion, resolution, or explicitly check 're-encode all', what you see will be a rather quick rewrapping - the existing video and audio will just be reused, but rewrapped into new and hopefully compliant file structures.
Last edited by Carsten on Sat Oct 10, 2026 12:13 pm, edited 2 times in total.
StephW999
Posts: 90
Joined: Mon May 17, 2021 1:15 pm

Re: Help fixing errors

Post by StephW999 »

Indeed. Carsten is certainly right
Also, your DCP was created with Resolve, which outputs a SMPTE "A" package, not "Bv.21".
The errors DoM indicates are warnings. It's not a problem at all.