-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
Cancelled - Output folder does not contain frames #2
Comments
Please reproduce this and then send all logs from FlowframesData/logs/. |
I moved files to D:\tools\FlowframesAppV14\FlowframesData\pkgs\rife-cuda as the log said. sessionlog Output folder does not contain frames - An error must have occured during interpolation! |
I got the popup with the same error message, but my log file includes below lines which I think might be useful.
|
BTW, one piece of video in 20FPS triggerred this problem but another one in 25FPS didn't. They are both 720p and encoded by x265, file size about 20MB. |
Make sure you try to reboot first, maybe something is blocking the CUDA memory. |
RIFE dev suggests that the non-parallel edition may address it.
|
I can't use the official code because it does not support image sequences. |
A minor suggestion from me is to include critical error message produced by 3rd party libs, at least a prompt with log path. The concern is, I think the problem I met has different root cause than the original poster's, however, we got exactly same popup. It will also improve communication for issues (if any) in the future, I think. |
RIFE supports image format input now. |
Error handling is improving in every version, especially v17, which will print better Pytorch/CUDA errors. |
v18 will use the latest code by hzwer which should be more stable. |
Closing for now. |
When I choose RIFE, this message pops up.
The text was updated successfully, but these errors were encountered: