-
Notifications
You must be signed in to change notification settings - Fork 0
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
ETA's are pretty inaccurate #19
Comments
Alternatively just simplify the current system and at least make it a little more transparent what happens. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
FFmpeg outputs the amount of seconds processed.
We also know the amount of total seconds.
We assume amount processing speed for a single conversion is constant. (though this could cause significant an error).
Each file should have a calculated field called "Work"
It's the estimated amount of processing needed to complete.
The significant factors (that we can know before processing) could be:
Need some kind of system to collect all these variables and estimate the amount of work.
We can probably just learn as we go from the computer, which make "hardware support" constant.
Also probably these variables are not completely independent.
A formula could be:
work = output_decoder * input_decoder * width * height * (frames/sec * duration)
where input_decoder and output_decoder are some number.
The text was updated successfully, but these errors were encountered: