New RIFE filter - 3x faster AI interpolation possible in SVP!!! (Page 6 of 85)

ok, I fixed it. Full instruction

<... skipped ...>

3.8 model gives me 24 fps and this one 41

EZ to install guide
1. Stop svp and delete C:\Program Files (x86)\SVP 4
2. Download and unpack https://www.playbook.com/s/vadash/wcVXb … Ky5jaQMkLs

Blackfyre
any tips?

check the log!

Many thanks for the tests! A huge improvement in the RIFE algorithm can be seen!

These are for comparison the results on a GeForce RTX 3090 graphics card done by: lwk7454:

https://www.svp-team.com/forum/viewtopi … 526#p79526

We can see how similar results the 3.8 model gave for GeForce RTX 3090 and GeForce RTX 3070 Ti graphics cards:

28.1 FPS vs. 24 FPS

and how huge the difference is with the 4.0 model: 40.9 FPS!!!!!

dlr5668, could you please specify the CUDA load for these tests. This is very important data to determine if the new model makes better use of the graphics cards capabilities or if there is still room for optimization, as I described here: https://github.com/hzwer/arXiv2020-RIFE/issues/217

By the way, thanks for checking that FP32 performance is close to FP16. However, if you would provide precise data for which precision this is, that would be additional information that I could paste in the link provided above.

It would be good if you could present data in the same range as lwk7454, it would be consistent with what I presented here https://github.com/hzwer/arXiv2020-RIFE/issues/217 and maybe the RIFE developer will come up with something extra to achieve 50FPS for 1080p, which would be satisfactory for real time interpolation!

I tried x3 with

        smooth = RIFE(input_m, 3)
        smooth = smooth.resize.Point(format=input_um.format.id, matrix_s="709")
        smooth = core.svp2.SmoothFps_RIFE(smooth,smoothfps_params,src=input_um,fps=src_fps*3)

but SVP crashed. Probably need to change it in some place else

> Could you find a moment of time and add a new parameter to the RIFE configuration in SVP

yeah... but you do understand that x3 (or hypothetical x2.5) will be 2 times slower, and x4 will be 3 times slower, right?

Check out my post here: https://www.svp-team.com/forum/viewtopi … 493#p79493 and especially lwk7454's reply here: https://www.svp-team.com/forum/viewtopi … 497#p79497

Am I seeing correctly? Even 42.5fps manages to be achieved?

> but not x2.5

this line (https://github.com/HolyWu/vs-rife/blob/ … t__.py#L85)
"(n % multi) / multi" is a float value meaning the exact position [0;1] between source frames

so it's easy to make a x2.5-sequence like frame0, 0.4, 0.8, 1.2, 1.6, frame2, ...
still it will be 4 generated frames for every 2 source ones => two times slower than frame doubling

Too bad I don't have a RIFE compatible graphics card yet, but I'll play around with theoretical calculations based on the dlr5668 result:

1920x1080 @23.976

42.5 fps: https://www.svp-team.com/forum/viewtopi … 699#p79699

so

21.25 new interpolated frames per sec.

90 minutes movie has
=90*60*23.976=129470.4 frames

re-encoding will take:

x5 (for 120Hz TV or monitor)
=4*129470.4/21.5=24088 seconds or 6h42m

x10 (for 240Hz TV or monitor)
=9*129470.4/21.5=54197 seconds or 15h4m

I also reuploaded image. Almost good to distribute with svp installer like regular RIFE You can remove all .lib and *train* files from pytorch + apply NTFS compress to reduce unpacked

Not worth it. Just switch TV to 50/100 Hz. Wish we could include step with

# "ReClock" replacement
video-sync=display-resample
video-sync-max-video-change=10

so it speedup 23.976 * 2 to 50 fps. Maybe Chainik will help ?