-
Notifications
You must be signed in to change notification settings - Fork 39
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
some questions #5
Comments
The motion in the left hand is too big for an interpolation scheme to work. Have you tried RIFE or SoftSplat on these input images. I believe they will also have similar issues ? |
Yes, RIFE and softSplat also have similar issues. Now I want to interpolate the ultra-low frame rate 1080P video with a frame rate of less than 10. These videos are characterized by very large movements. Do you have any good ideas? |
I think you would have to train on such dataset and see how the inferencing goes. @sniklaus (SoftSplat author), @JihyongOh, @hzwer (RIFE author) can comment more on how to solve this. |
The main challenge in video frame interpolation is dealing with large inter-frame motion (motion magnitude in terms of pixels). This motion can be challenging (read: have a large magnitude) for various reasons: high-res footage, fast motion, low frame rate as input, and others (note, just because the frame rate in the input is low doesn't mean much, if the motion is little as well then it is still perfectly doable to interpolate low frame rate footage). Having said this, you (@KevenLee) may just be reaching the limit of what current state-of-the-art video frame interpolation can do due to too large inter-frame motion. |
Just for completeness, you can find the result of SoftSplat on the provided images below. result.mp4 |
|
Thanks for your wonderful jobs!
I have some questions:
"python main.py --gpu 0 --phase 'test_custom' --exp_num 1 --dataset 'X4K1000FPS' --module_scale_factor 4 --S_tst 5 --multiple 2 --custom_path ./test_img_dir/test4"
input image1
input image2
result
The text was updated successfully, but these errors were encountered: