View Issue Details

IDProjectCategoryView StatusLast Update
0001605DCP-o-matic[All Projects] Bugspublic2019-09-13 19:30
ReporterCarsten Assigned To 
Status newResolutionopen 
PlatformMacOSOS XOS Version10.12
Product Version2.14.x 
Target Version2.16.0Fixed in Version 
Summary0001605: Start computing 'fps' during conversion based on trimmed time, not full content length

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 ;-)

TagsNo tags attached.
Estimated weeks required
Estimated work requiredUndecided


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-09-13 19:30 Carsten New Issue