About Dolby Atmos in Dcpomatic

[edgecode]

I run it one more time and this time DoP fused ATMOS together. It still plays but validation fails for reel duration mismatch

[edgecode]

Rerun it again after double-checking all reel breaks. This time DoP created the correct number of reels of matching duration. The "non-zero audio samples" error is still present. I understand EasyDCP validation failure isn't the death sentence, however this is for a distributor and will have to pass a third-party QC.

Should

Code: Select all

<meta:MainSoundConfiguration>51/L,R,C,LFE,Ls,Rs,-,-,-,-,-,-,-,-,-,-</meta:MainSoundConfiguration>

be

Code: Select all

<meta:MainSoundConfiguration>51/L,R,C,LFE,Ls,Rs,-,-,-,-,-,-,-,FSKSync,-,-</meta:MainSoundConfiguration>

?

[carl]

I think you're right. I will fix that.

[Carsten]

It might be useful to check into the Mainsound configuration and Metadata, also for ATMOS/IAB + 5.1 or 7.1, Hi/VI-N. There may be some bits to tweak. Carl, let me know if you need to some real world examples of ATMOS/IAB + 5.1/7.1 files.

[carl]

Thanks Carsten, if you can confirm the MainSoundConfiguration tags for those DCPs that would be a great start.

[carl]

These builds should create better CPL metadata with ATMOS:

https://dcpomatic.com/build/atmos/67b997fb83

It would be interesting to know if the EasyDCP verification passes a DCP made with that version.

[edgecode]

Exactly the same error with the new build.

[edgecode]

By the way, the audio matrix only shows 6 inputs and 13 outputs. Is it how it is supposed to be?

[carl]

By the way, the audio matrix only shows 6 inputs and 13 outputs. Is it how it is supposed to be?

That sounds right. The PCM audio is quite separate from the ATMOS, as for DoM the ATMOS is really just a bitstream that we pass through unaltered.

Exactly the same error with the new build.

Does the CPL MainSoundConfiguration tag look different with your new DCP?

[edgecode]

Does the CPL MainSoundConfiguration tag look different with your new DCP?

Yes, it does say FSKSync in the right position. However it might have been a stupid suggestion on my part because it says somewhere in white papers the tag should be limited to fewer characters than this.