Possible cosmetic bug: Video export speed given as 1/x ?
Posted: Thu Jun 01, 2017 9:40 pm
Situation:
When overlaying a video, a notification informs about the relative progress, frames processed as well as heap memory and "speed".
For example: "[...] speed x3,5"
Expectation:
I understand speed as a moving window over the last second, given by the fraction of the current overlay speed performance, measured in fps, over the raw video's fps.
Similar definitions could be found to consider the total process speed instead of a moving window covering the last second gone by.
That so, I would expect speed ratings above 1 to indicate faster processing than the video's fps/realtime - the video should be processed in less time than it would take to play it at recording speed.
Behaviour:
When looking at the time taken for some count of frames to be processed, it seems to me that speed is given reciprocally according to above definition: Sub-realtime processing shows as speed ratings above 1.
Proposal:
Inverse speed rating.
Or delete thread as trivial / not a business case / OBD interp is much more important.
Cheers,
Philipp
When overlaying a video, a notification informs about the relative progress, frames processed as well as heap memory and "speed".
For example: "[...] speed x3,5"
Expectation:
I understand speed as a moving window over the last second, given by the fraction of the current overlay speed performance, measured in fps, over the raw video's fps.
Similar definitions could be found to consider the total process speed instead of a moving window covering the last second gone by.
That so, I would expect speed ratings above 1 to indicate faster processing than the video's fps/realtime - the video should be processed in less time than it would take to play it at recording speed.
Behaviour:
When looking at the time taken for some count of frames to be processed, it seems to me that speed is given reciprocally according to above definition: Sub-realtime processing shows as speed ratings above 1.
Proposal:
Inverse speed rating.
Or delete thread as trivial / not a business case / OBD interp is much more important.
Cheers,
Philipp