Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Size targeting or estimated output size display #4640

Closed
tinacious opened this issue Nov 2, 2022 · 4 comments
Closed

[Feature] Size targeting or estimated output size display #4640

tinacious opened this issue Nov 2, 2022 · 4 comments

Comments

@tinacious
Copy link

Description of the feature or enhancement you'd like to see in HandBrake

Hello! Amazing app, I love it.

I am requesting a feature to be able to either:

  1. View the projected output size once a preset/configuration is chosen so we know the size before beginning to encode; or:
  2. Have the ability to target a specific output size

I find I record videos for upload to Github, which has a 10 MB limit. I did a bit of trial and error with a few encodings to get it to be under the size while still maintaining quality. It would be really convenient to be able to say "Hey Handbrake, please make my video up to 10 MB and do your best with the quality."

I'm definitely no expert with regards to video encoding so I'm not sure how feasible something like this would be.

Thanks for your consideration, let me know if you need anymore info.

What Operating System are you running?

macOS

What version of HandBrake are you running?

1.4.1

Where did you download HandBrake from?

I don't recall

Activity Log, Crash Log or any other details

No response

@sr55
Copy link
Contributor

sr55 commented Nov 2, 2022

You can't reliablally project file size without encoding first. Even with a bitrate the error margin can be high enough to make the feature useless.
Target File size was removed from HandBrake many years ago as there are just too many situations where it isn't accurate enough and there were never ending complaints about it.

@sr55 sr55 closed this as completed Nov 2, 2022
@tinacious
Copy link
Author

Thanks for the explanation @sr55, that is good to know.

@cq535454518
Copy link

Why not try to design it as an optional option? And mark "For reference only" when opening. In this way, even if I need to compress videos within 10m, I can also select a configuration of about 5m to 7m through preview. Even if it has errors, there is a rough estimate. In this way, you do not need to endlessly complete compression, and then check its size.

@GavinRay97
Copy link

I came here to make this same feature request

@sr55

You can't reliablally project file size without encoding first. Even with a bitrate the error margin can be high enough to make the feature useless.

This is naivety, as I don't have an understanding of how encoding works, but there's a mobile app I've used which allows you to set a target size and will optimize params to fit the requirement. It seems to work decently well from my experience with it:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants