Average number of FPS is based on conversion start

Archive of historical bug reports.
Please use the GitHub link above to report issues.
Forum rules
Please be aware we are now using GitHub for issue tracking and feature requests.
- This section of the forum is now closed to new topics.

Post Reply
Thain Esh Kelch
Posts: 10
Joined: Wed Jul 20, 2011 8:46 pm

Average number of FPS is based on conversion start

Post by Thain Esh Kelch »

Please describe the problem in as much detail as possible:
A minor bug. When converting a file, Handbrake reports the number of frames per second (FPS) being processed currently, and the overall average FPS since start, at the bottom of the window.

The average FPS is calculated based on the start of the file conversion, and it does not take any pauses in conversion into account, leading Handbrake to display a meaningless average FPS number.

For an uninterrupted conversion, if you spend 10 seconds processing 1 FPS every second, your average will be displayed as 1 FPS.
For an interrupted conversion, if you pause your conversion after 5 seconds, and let it sit idle for 5 seconds and restart it, your average will be displayed as 0,5 FPS, even though the actual average FPS conversion is still 1 FPS as in the prior example.

If you've had the conversion idle for an extended periode, say over night while not using the computer, the average FPS displayed becomes so low that is it pointless IMHO (Say, 0,02 FPS for instance).

What are the steps to reproduce this problem:
Start a file conversion. Pause the conversion for any time periode. Start the conversion again, and the displayed average FPS will be wrong.

What version of HandBrake you are running:

What operating system and version and you running (e.g. OSX 10.11, Windows 7, Ubuntu 14):
OSX 10.11.4

Post Reply