View Bug Details

IDProjectCategoryView StatusLast Update
0001509DCP-o-maticFeaturespublic2023-09-01 21:52
Reportercarl Assigned Tocarl  
PriorityhighSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0001509: Allow specification of video levels in inputs
Description

See e.g. video-levels-hack branch

Tagsworkflow
Branch
Estimated weeks required
Estimated work requiredSmall

Activities

carl

2019-05-24 23:29

administrator   ~0003356

Some work done in master at 92784c9c2

carl

2019-05-24 23:45

administrator   ~0003357

I guess we need to add our own code to do range changes for RGB.

Carsten

2019-05-26 14:21

manager   ~0003360

We recently played an ad for european election, and I noticed it showed little contrast, greyish blacks, little saturation overall. I checked it in Video Monitor, and the lowest in-picture black was around 512. It was 16:9 in a flat container, and only the pillarbox bars left and right went down to zero. In general, commercial DCPs/trailer all reach down to nearly zero. This was an obvious example of mismatched limited vs. full range handling.

That DCP was done with OpenDCP 0.30. OpenDCP needs source material to be converted to image sequences before conversion can take place. And there is an immanent issue with limited range video vs. full range image file formats, so I guess that's where the mapping went wrong in this case. I haven't seen it happening so far within DCP-o-matic, however, it may of course be possible that some people create content with non-suitable settings.
I remember that Resolve allows to specifiy video vs. data levels for nearly all output formats, so, that would be an option to create test content to see if DCP-o-matic handles this right.

  • Carsten

Bug History

Date Modified Username Field Change
2019-03-26 00:17 carl New Bug
2019-05-01 10:42 carl Estimated work required Unknown => Small
2019-05-24 23:29 carl Note Added: 0003356
2019-05-24 23:45 carl Note Added: 0003357
2019-05-24 23:45 carl Assigned To => carl
2019-05-24 23:45 carl Status new => acknowledged
2019-05-26 14:21 Carsten Note Added: 0003360
2019-11-27 19:51 carl Tag Attached: workflow
2019-11-27 19:52 carl Category Bugs => Features
2021-05-23 00:02 carl Target Version 2.16.0 =>
2022-07-04 11:58 carl Status acknowledged => resolved
2022-07-04 11:58 carl Resolution open => fixed
2023-09-01 21:52 carl Status resolved => closed