View Bug Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001898 | DCP-o-matic | Bugs | public | 2021-01-14 15:16 | 2021-10-08 00:04 |
Reporter | carl | Assigned To | carl | ||
Priority | immediate | Severity | major | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Target Version | 2.16.0 | ||||
Summary | 0001898: Loading a project from a previous version will set all video content to "full range" | ||||
Description | This sounds wrong... | ||||
Tags | No tags attached. | ||||
Branch | |||||
Estimated weeks required | |||||
Estimated work required | |||||
|
...although maybe it's the least worst option; I think 2.14.x basically never changes range, so video range inputs are not converted to full range for DCP. Blindly marking all 2.14.x content as full range would at least preserve the same look as 2.14.x for viewer/DCP (though it would change exports, since that uses video range). |
|
I am persuaded by the "keep it just as wrong as it was in 2.14.x" argument. |
Date Modified | Username | Field | Change |
---|---|---|---|
2021-01-14 15:16 | carl | New Bug | |
2021-01-26 22:04 | carl | Note Added: 0004103 | |
2021-04-03 20:29 | carl | Assigned To | => carl |
2021-04-03 20:29 | carl | Status | new => resolved |
2021-04-03 20:29 | carl | Resolution | open => fixed |
2021-04-03 20:29 | carl | Note Added: 0004210 | |
2021-10-08 00:04 | carl | Status | resolved => closed |