Skip to content

Oversight/Bug: Picking a filesize larger then intended causes upped bitrate (--web) #42

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

Open
theo-croft opened this issue Apr 21, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@theo-croft
Copy link

Normally this does not seem that bad though this becomes a BIT of a problem when you end up with a 13 second 90mb file (total bitrate of 54177 kbps) which can often lead to buffering on non speedy internet. or cause excess data consumption

Steps to reproduce:

  1. set target size over original file size
  2. (optional) shorten inital video length

It appears if there is additonal space that can be filled, the encoder tries to up the bitrate, the solution would be to either not require a target file size, or input the same target file size as the video.

@zfleeman
Copy link
Owner

Good catch. I'll probably just throw an error if the target is greater than the input file size.

@zfleeman zfleeman added the bug Something isn't working label Apr 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants