-
Notifications
You must be signed in to change notification settings - Fork 31
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 can become excessively high and cause an overflow #146
Comments
Thanks for raising this. I haven't managed to reproduce this, but I can see where it may have happened in the upstream progress-bar code. |
I have managed to reproduce now & raised an issue upstream console-rs/indicatif#561 I'll also try to look into a fix there when I get a moment. |
I've also noticed on the newest commit that the ETA rises for a while until it becomes excessively high, then falls back down to a sensible value, and cycles until it's done. There's gotta be enough information to deduce that it shouldn't be a week until a two-hour encode is done. |
The overflow should be fixed now, the very high eta issues upstream remain, see |
#174 is probably the quickest way to fix ETAs, unless upstream ever get round to improving it. I think we can close this issue now the immediate actions have been taken. |
I was encoding a file with SVT-AV1's preset 1 when ab-av1 crashed:
The ETA started climbing and eventually reached the very high number above. I assume this is because preset 1 is very slow, not very well threaded, and though clip I was encoding is only 60 frames long, it has quite a lot of detail. I also had other encodes going at the time.
The input file was a CRF 0 x264 transcode of touchdown_pass_1080p_60f.y4m from the objective-1-fast dataset available from here.
Command to reproduce:
I'm on Linux Mint 21.1 running ab-av1 0.7.7.
The text was updated successfully, but these errors were encountered: