MFilmer wrote: ↑Tue Sep 19, 2023 5:17 pm
EDIT: Your SMPTE Bv2.1 does not have any warnings in easydcp. What are your settings? Cant find any difference...
It must be an easydcp bug of the latest versions ( 4.1.6 & 4.1.4)
For me some SMPTE DCPS created by Clipster frezees versions 4.1.6 and 4.1.4
Version 4.1.2 has no problem with the same dcps
I don't understand why my previous message is not displayed. probably a bug.
I replied to MFILMER on September 19
Post by StephW999 » Tue Sep 19, 2023 8:22 pm
MFilmer wrote: ↑Tue Sep 19, 2023 7:17 pm EDIT: Your SMPTE Bv2.1 does not have any warnings in easydcp. What are your settings? Cant find any difference...
Same for me - some of the latest posts in some threads are only indicated in list overview, but when I open the thread, only the previous post is shown as last.
I raised this as a bug with EasyDCP not realising at first it was specific to DCPs created in recent versions of DCP-o-Matic. For me this was EasyDCP Player 4.1.6 (and the M1 Beta 4.1.96). Dropping back to 4.1.4 avoided the problem.
When opening Easy DCP Player with certain DCPs it gets stuck for 10 mins or so on:
Verifying XML schema of CPL
They would eventually open if you have the patience to wait that long.
Now 4.1.7 has been released I'll give that a go and report back.
The Verifying XML schema of CPL hang seems to have been fixed Easy DCP Player 4.1.7
My test DCP created in DCP-o-Matic 2.16.65 failed the full verification in Easy DCP. But only with the two things, DC-o-Matic warned me about in the hints!
Invalid audio properties. 6 channels (Expected 16). 24 bits per sample (Expected 24). Sample rate of 48000 (Expected: 48000).
When a Composition Playlist's ContentKind value is set to "feature", both marker labels FFEC (First Frame of End Credits) and FFMC (First Frame of Moving Credits) shall be present.
For our own EasyDCP verifications of DCPs we receive I tend to untick SMPTE 429-2 and SMPTE RDD 52 and just use the Fraunhofer IIS test specification which is good enough for our needs and would pass this DCP.
One more question: In the newest dcpomatic version it is not possible to create an "old" SMPTE 429-2 DCP, correct? Only SMPTE RDD 52 is possible, right? Is there any reason why there is no choice in dcpomatic?
You mean without the CompositionMetadata? I guess I hoped that we wouldn't need a choice like that, when it would be hard for users to know how to set it.
Would such an option be useful for you? Any particular reason?