| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I can't remember seeing this logged for ages and it appears to cost
nearly a second on the rgb_xyz benchmark on AMD Ryzen 7 5700U.
|
|
from the rgb -> xyz loop.
|
|
|
|
|
|
|
|
|
|
Adapted from a patch from Aaron Boxer for grok support.
|
|
|
|
This causes some test ID churn.
|
|
|
|
|
|
I didn't yet find a reference which tells me what they are, but there
have been multiple reports of DCPs that have this channel ID and so
(before) could not be added to a DoM project.
|
|
|
|
Ubuntu 16.04).
|
