| Age | Commit message (Collapse) | Author |
|---|
|
|
|
DoM bug #2868 reports that Resolve made a DCP with the PKL namespace
http://www.smpte-ra.org/schemas/2067-2/2016/PKL
This seems wrong (google suggests that this is the namespace for IMF
PKLs) but let's accept it and log an error instead of throwing an
exception.
|
|
The previous solution required the correct define to be present when
including libdcp, which seems a bit awkward.
|
|
|
|
This reverts commit 6d1a7e90ec3244b8e532e03c5209d5e8448f422e.
It is used in DCP-o-matic, contrary to the comment.
|
|
|
|
It was added "for completeness" apparently but it would now cause
complications in keeping it compatible with various boost versions, so
just remove it as YAGNI.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It seems that these should only be present if the timecode rate is 101
or above, and in that case all timecodes should have 3 editable rate digits,
but someone sent a DCP from what seems to be EasyDCP Creator and it has
one timecode of 00:05:01:000.
|
|
|
|
|
|
|
|
|
|
|
|
A reporter on the forum is making their own DCPs that don't include
an essence type at some point which trips this check as it was before.
|
|
|
|
|
|
|
|
|
|
(DoM #2716).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(DoM #2698).
|
|
#2698).
|
|
|
|
|
|
|
|
MXF::set_key() sets it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
