View Bug Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001509||DCP-o-matic||[All Projects] Bugs||public||2019-03-26 00:17||2019-05-26 13:21|
|Priority||high||Severity||major||Reproducibility||have not tried|
|Target Version||2.16.0||Fixed in Version|
|Summary||0001509: Allow specification of video levels in inputs|
See e.g. video-levels-hack branch
|Tags||No tags attached.|
|Estimated work required||Small|
Some work done in master at 92784c9c2
I guess we need to add our own code to do range changes for RGB.
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.
|2019-03-26 00:17||carl||New Bug|
|2019-05-01 09:42||carl||Estimated work required||Unknown => Small|
|2019-05-24 22:29||carl||Note Added: 0003356|
|2019-05-24 22:45||carl||Note Added: 0003357|
|2019-05-24 22:45||carl||Assigned To||=> carl|
|2019-05-24 22:45||carl||Status||new => acknowledged|
|2019-05-26 13:21||Carsten||Note Added: 0003360|