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

Exactly Especially since I can see minor but perceptible differences between v4.15 and v4.15v2 that I don't remember seeing in other models.

I would be surprised if I ever said that Rife v2 has better picture quality, but if I did say that then was incorrect. But there definitely was a time when v2 was better/quicker at FF/REW a video, but that is no longer the case. 

I said the difference was "minor" but "perceptible" and I'm watching on a very large VR Cinema screen so I'm going to see things that others don't. That's why I wouldn't use anything below Rife v4.9.  Over the development time of Rife from v4.6 to v4.15 I've seen artefacts improve to the point where they either disappear or have been reduced.  Vertical fast movement artefacts are still an issue but v4.15/v2 handles those the best.

Would be good if the above is added as an update for those that need it @Chainik

And please update MPV to the latest stable v0.38.0 from 2 weeks ago.

Thank you.

Oh wow, that sucks, why would they push that out as a "stable" release. Crazy.

Funny, I can't actually find any ncnn vs dml benchmarks for rife. I'm inferring from the relative performance compared to cuda and trt.
https://github.com/n00mkrad/flowframes/ … chmarks.md
Benchmark 2 https://github.com/AmusementClub/vs-mlr … /v14.test4

I might just do some benchmarks myself in VSEditor.

That's why I used v2 for so long. Half the GPU usage, half the noise. But I no longer need v2 now that I'm downscaling.

> I can't actually find any ncnn vs dml benchmarks for rife.

TRT is 2 times faster than ncnn
DML is _10_ times slower than TRT

Hello folks, For me, films are often interrupted and a Dos window appears. At the beginning it's completely ok, but I don't want it in the middle of the film. can this be stopped?

yes, it's the only reason we use v2
from my benchmark, v2 gives a huge fps boost

I want to use Frame Gen in some games that's why I turn it on.

also
HAGS ON gives you better FPS on light tasks, but it's worse on heavy tasks. (in the end, turning it off is still better for RIFE)

Ryzen 5900x + 4080 SUPER

if you want to benchmark with mpv, add the configs to the bottom of your mpv.conf file.

profile = benchmark # add # to disable benchmark
[benchmark]
osd-msg1 = "FPS: ${estimated-display-fps}"
opengl-swapinterval = 0 # {lock☒}
opengl-dwmflush = no # {lock☒}
vulkan-swap-mode = immediate # When using --gpu-context=winvk, if the number of frames is equal to the refresh rate, try changing to mailbox
d3d11-sync-interval = 0 # {lock☒}
d3d11-flip = no # {lock☒} The swapping effect of flip may clamp the extreme frame rate FPS_max=number of front and rear buffers x refresh rate

hidpi-window-scale = no # {lock☒} Disable DPI scaling first and then the specified magnification will be accurate
window-scale = 1.5 # Manually specify the source zoom ratio (limited by --auto-fit=<value>)
sub = no # {lock☒}
audio = no # {lock☒}
keep-open = always # {lock☒}
# display-fps-override = 24 # Match source framerate as much as possible
video-sync = display-desync # {lock☒}
interpolation = no # {lock☒}

I was hoping someone would make a change for below 10% because this is what I was using to fix the vertical fast motion issues I saw but the choppiness it introduced elsewhere wasn't worth it.. 8% works well on fixing those issues, but maybe not quite as smooth on one or two other scene changes above 10%. Still testing. 6% is too choppy no matter what.  Blending/repeat doesn't seem to make much difference.

Update: Did my ultimate test (introduction to Hugo) and below 10% is way too choppy even at 8%. If a similar SC algorithm fix could be applied to 10 or even 12% that would work. But maybe that's not possible because of how it works?

Thanks. I've tried various combinations including setting SC=100 (turn off?). 6% is a no go. The issues I saw initially with NVOF motion vectors are amplified by the intro to Hugo which is a torture test for SC. The dumb frame comparison is the only algorithm that works for Hugo and works the best all round.

Bottom line:
- 6% no go any algo.
- SC below 10% with the dumb algo fixes the vertical fast motion artefacts at the expense of smoothness.
- NVOF algo fixes vertical motion artefacts but causes problems elsewhere. Hugo just makes those problems more obvious.
- SVP algo doesn't seem to help much.
- Dumb algo works best overall. Smooth with Hugo and everything with exception of "some" vertical fast motion scenes.

I do used fixed 60 fps though, not "To Screen".