View Bug Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002395 | DCP-o-matic | Bugs | public | 2022-12-19 20:14 | 2023-09-01 21:52 |
| Reporter | carl | Assigned To | carl | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 2.16.36 | ||||
| Summary | 0002395: Invalid COC component number | ||||
| Description | This was reported (https://dcpomatic.com/forum/viewtopic.php?p=9761#p9761) on a Colorfront Transkoder-made DCP. I can't find anywhere that says this component number can only be 0 - presumably it also makes some sense to have it for components 1 and 2 as well. Probably should remove this check or try checking for 0, 1 or 2 for this number. | ||||
| Tags | No tags attached. | ||||
| Branch | |||||
| Estimated weeks required | |||||
| Estimated work required | Undecided | ||||
|
|
Asked for the DCP or if I can send a test version which includes the "bad" number in the error. |
|
|
Can't get the DCP but can send a test version, building for Windows and mac from |
|
|
The original reporter says the number in their DCP is 1. |
|
|
c3b364d5574e02ee55bce950e2056e3df2faccff |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-12-19 20:14 | carl | New Bug | |
| 2022-12-19 20:14 | carl | Assigned To | => carl |
| 2022-12-19 20:14 | carl | Status | new => confirmed |
| 2022-12-19 20:15 | carl | Note Added: 0005382 | |
| 2022-12-20 23:20 | carl | Estimated work required | => Undecided |
| 2022-12-20 23:22 | carl | Note Added: 0005384 | |
| 2022-12-21 11:25 | carl | Note Added: 0005389 | |
| 2022-12-21 11:29 | carl | Status | confirmed => resolved |
| 2022-12-21 11:29 | carl | Resolution | open => fixed |
| 2022-12-21 11:29 | carl | Note Added: 0005390 | |
| 2023-09-01 21:52 | carl | Status | resolved => closed |
