View Bug Details

IDProjectCategoryView StatusLast Update
0000502DCP-o-maticFeaturespublic2015-08-27 16:56
Reporterandrew.levine Assigned Tocarl  
PrioritynormalSeverityfeatureReproducibilityN/A
Status acknowledgedResolutionopen 
PlatformMac OSOS XOS Version10.9
Product Version1.76.0 
Summary0000502: Accurate runtime prediction
Description

My monster of a film took very long to encode, which would be (more ;-) OK if the prediction were more accurate. It appears that the remaining time is calculated only by the currently achieved fps, not by looking at the progress in relation to time spent. maybe this is something that can be more closely calculated.

TagsNo tags attached.
Branch
Estimated weeks required
Estimated work requiredTiny

Activities

andrew.levine

2015-02-22 08:58

reporter   ~0000509

Sorry, severity should be "feature".

andrew.levine

2015-02-22 09:13

reporter   ~0000510

The progress report could read: "now: xx fps | avg: yy fps"

So, fpr each processing instance (when ingesting one movie) DCP-o-matic would have to store: beginning and end time and frames computed. Maybe also the render config: machines available for processing, with their respective stats. But I'd give the latter a lower priority as this aspect is definitely more susceptible to fluctuations.

carl

2015-02-22 23:36

administrator   ~0000514

You're right, the current calculation is frames_remaining / current_fps (see remaining_time() in src/lib/transcode_job.cc)

Bug History

Date Modified Username Field Change
2015-02-22 07:34 andrew.levine New Bug
2015-02-22 08:58 andrew.levine Note Added: 0000509
2015-02-22 09:13 andrew.levine Note Added: 0000510
2015-02-22 23:36 carl Note Added: 0000514
2015-02-22 23:36 carl Assigned To => carl
2015-02-22 23:36 carl Status new => acknowledged
2015-06-12 11:50 carl Severity major => minor
2015-06-12 12:13 carl Severity minor => tweak
2015-06-12 12:20 carl Severity tweak => feature
2015-06-12 14:01 carl Estimated work required => Tiny
2015-08-27 16:56 carl Target Version => 2.x