[Rejected] Estimated file size during encoding

[ChibiSqueeze]

Please describe what you would like to see added to HandBrake:
Display the estimated file size during encoding.
Why would you like to see this added:
To get an idea how big the end file size is for CRF encoding, bitrate encoding etc. MeGUI has this feature and is quite accurate.
What version of HandBrake are you currently running:
0.10.5
What operating system and version and you currently running (e.g. OSX 10.11, Windows 7, Ubuntu 14):
Windows 7

[s55]

MeGUI has this feature and is quite accurate.

Sorry, it just isn't even close to being accurate enough for us to include it.

[mduell]

In particular HB's video length detection/estimation is inaccurate (thus the removal of target size) and this would be off by at least the same margin.

[JohnAStebbins]

MeGUI has this feature and is quite accurate.

I'm sure it's quite accurate for a certain class of well behaved file types. But there are files that do not have a header that defines the duration, or worse report an incorrect duration. There are enough of these in the wild that supporting this feature was a constant headache. By making people calculate the required bitrate themselves, they learn *why* the size isn't what they expected when the duration is wrong and can self-correct.

[Deleted User 13735]

Bitrate (Mbps) X Time (Seconds) X .125 = File Size (MB)

Since the net bitrate is unpredictable in CRF, one has the option to 'test and tweak' multiple encodes, or to select VBR, assuming the duration is being reported correctly. CRF is not recommended for streaming, especially over the internet, for that very reason.

Constraining or targeting output file size has little legitimate implementation in 2016, owing to uber-cheap storage solutions. The MeGUI bitrate calculator and target size doesn't look materially different than any other, and if the accuracy pleases you, please continue using it.