I'm not here for a topic of dicussing differences of opinion or this and that. The topic I wrote about is RIFE and how to visually (somewhat) properly doing the testing and finding which RIFE model is better for what type of content this-and-that. I'll stick with that
https://github.com/hzwer/ECCV2022-RIFE
https://arxiv.org/abs/2011.06294
https://paperswithcode.com/paper/rife-r … estimation
This shown ranking is a snippet from this website "MSU Video Frame Interpolation Benchmark" https://videoprocessing.ai/benchmarks/v … tion.html.
Anyone who is interested in different video estimation/interpolation ML models, should check it out.
The RIFE model (which is btw. a very outdated model from 2021 or so) is already scoring pretty well in the subjective score. When it comes to PSNR, SSIM, VMAF it obviously isn't that high scoring.
But it all is negated once looking at the FPS numbers; Chronos-SloMo-v2 is only achieving 4.x FPS.
The middleground (in effort and result) for us, doing a bit more than childsplay, would be:
1) Screen-record or capture (the video player) the video with a program
2) Put it in a video editing software and edit/cut it.
3) Do the same for the other model.
4) Align them perfect, frame-by-frame, and put both video files together.
What we do here mostly is childsplay when it comes to visually testing, and by no means the developers should listen to us.
@Drakko01
Okay, I done my childsplay-testing with this mentioned scene from this movie (making notice again that our testing here is incredibly flawed).
You mean that scene ~10 seconds scene where the camera pans 360 degree around the character with the robotic tentacles?
Yes, that's a good scene to test, with nice patterns and elaborate shapes!
Some tips first:
1) If you are doing the A-B repeat with slomo playback speed as mentioned, and/or changing between models, you have to play the A-B loop at least 2-3 times, for the scene to be fully buffered/processed. See my attached image "screen9"? With the mpc video renderer, press CTLR+J to show the graph and information.
As seen in the bottom right corner, the graph is not flat but spiking and the framerate not stable at 48, which means it's not fully buffered/procesed yet (it's a demanding 3840x1600 video even for the rtx 4090, as mentioned).
2) The flawed result is seen in the attached "screen10". Massive artifacts etc. which normally wouldn't be there, even at x0.25 playback speed.
When visually A-B comparing, screen-recoding, recording, make sure the graph is flat and the framerate fully stable.
Long story summarized, between v4.25 and v4.26, I sat down for couple of minutes:
For that 10 second clip, I can't tell a clear winner.
At most elaborate/complex elements, v4.26 is displaying these elements slightly clearer, with less noise/small blocking&artifacts on the patterns/the whole image during slow-medium sized movement (camera pan), as in the first 4 second on the red metal triangle things and other metal party of these tentacles.
Also I spot less bright haloing-artifacts between the tentacles in the foregound and the guys's background black darker coat. Also at the forest in the background
I also spot a bit less noise and patterns on the concrete whitish pillar and the river at the end.
Contrary v4.25 is for example visibly better in other aspect during the first 4 seconds and after that: There are less stutterish blocks (warping, medium sized) around the metal tentacles (around the whole body) and the red triangles and other metal parts.
Also I noticed v4.25 is somehwat more clearer during faster movements (camera pan).
If anything, I somewhat prefer v4.26 because as the pros outweighs the cons somewhat.
So basically: This is what I meant. Visible childsplay-testing as ours, we can maybe spot a very clear difference when it comes to older models as 4.15 versus now v4.25/26, but definitely not that much between 4.25 and 4.26 themselves. Our testing is way too childsplay for that and our conclusions differentiate too much due to our different testing.
In such small version jumps, some things get better, some worse.
That's why I mentioned plenty: Trust the developers. They are developing it, they do the math, the have the datam, they do proper scientifically testing etc. and there is hardly any point arguing against that. If they "recommend v4.26 for most scenes now", I will believe them, because my testing/conclusion (and everyone elses here) is much flawed, and theirs not.
Also: Please no more 3840x1600 video file testing. Way too demanding with such current model, even for such graphics card. Stutters way too much and need to long process/buffer. If you want me to test next, find some 1080p footage