View Bug Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001605 | DCP-o-matic | Bugs | public | 2019-09-13 20:30 | 2023-12-22 22:32 |
| Reporter | Carsten | Assigned To | |||
| Priority | low | Severity | tweak | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Platform | Mac | OS | OS X | OS Version | 10.12 |
| Product Version | 2.14.x | ||||
| Summary | 0001605: Start computing 'fps' during conversion based on trimmed time, not full content length | ||||
| Description | A tiny bug: When encoding, DCP-o-matic will start indicating encoding fps only after some lead-time. For trimmed content, that 'lead time' (10%?) seems to be computed from the full content length, not trimmed/film length. So, when converting a 10min feature that is trimmed to 3min, fps computation starts very late. Obviously, nothing serious ;-) | ||||
| Tags | No tags attached. | ||||
| Branch | |||||
| Estimated weeks required | |||||
| Estimated work required | Undecided | ||||
