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

jdg4dfv7

you don't need anything to use 4.16+ models, just put it into the models folder

if you don't know exactly _why_ you need updated TensorRT and/or vsmlrt.py files then you don't need them

Kaiji

please upload the source clip

@flowreen91
@Chainik
Thanks for providing a tip.

4) Switching to Tensor RT 15.x, it works swapping "vstrt.dll and the folder vsmlrt-cuda" only.
I noticed a bump of graphic card total power consumption (undervolted rtx 4090), about 5 - 10 % (differs in resolution, framerate, upscaling etc.)

5) If swapping the newer "vsmlrt.py" also from the TensorRT 15 file also, nothing works anymore; that means any machine learning based RIFE model and SVP's own interpolation. See image attached "error swapping vsmlrt_py".
Any way to fix from my side, you SVP developers side, or simply not swap the file?

6)
@flowreen91
Made the line change ("True"), nothing works.
See image attached.

Thanks in advance!

> please write down here, for laymen to understand, what's the best opion to use

the default one! (which is "SVP motion vectors")

> So this - "vsmlrt.py - Added support for RIFE v4.17 models." - can be completely ignored

yes, it can be completely ignored

The default one works well with everything except the intro to Hugo where it stutters considerably.

I found other cases when svp motion vectors using blend struggles with a complex scene, for example in Doctor Strange Multiverse of madness, after defender Strange is killed by the Ribboned Creature.

I think the previous comments are proof that this is setup dependant. SVP MV works best for @Chainik and works well overall but also has clear micro stutters. Some of the stutters are not so "micro". NVOF has always had clear stutters for me but works well for some. All except NVOF are siimlar, including Disable. But for me Image Comparison seems to work best with no obvious microstutters.

I got so excited lol

Then I tested, and the blinking was still there, I assume this is not fixed for RIFE? But only for motion vector or NVOF methods? @Chainik

I tried with both my custom mpv config, and then I removed my config file to test with default, and both had heavy blinking with Dolby Vision exclusive files.

I will like to ear others members results after this update.I still think that image comparison work the best , but i kinda like in some scenes NVOF motion vectors, the improve its subtle but its there.

apparently, DV blinking _was_ fixed, but it seems that now, with a processing logic changed for "motion vectors scene change", the blinking is back, but for a different reason and it's a different kind of blinking now...

still the latest "0.38" changes were necessary, but not enough

In all my tests of problem scenes, SVP algorithm at it's best can be better than Image Comparison, but at it's worst can give artefacts similar to NVOF. Image Comparison seems to be the best compromise giving the cleanest output with the least artefacts.

Prior to this latest update, the SVP algorithm might provide the best objective test results for false positives etc, just like a scaling algorithm might have the best objective PSNR and SSIM image quality scores. But in both cases, the resulting output when viewed by a human being can be less preferable to a lower scoring algorithm. It has it's faults, but Image Comparison just performs better overall for every problem scene I have.

*Edit. This conclusion is prior to the more recent SVP update so I have updated comment. Actual test updates will follow.

By the nature of your response, I'm guessing by your comment that SVP motion is your baby and because of that maybe you are missing the point. I want SVP motion to be better.  All I'm trying to do here is provide feedback to help you make it so.

Anyway, I tested using an MPV build from this week with the latest SVP update. Maybe it's the latest mpv build or the MPV changes you made,  but SVP motion has improved since the previous update. But since I'm almost certainly watching on the largest screen here, I can see stutters and micro-stutters thats most may not. SVP motion has at least a couple of clear and repeatable stutters for certain scenes that IC does not. Other than that, IC at 15% and SVP motion are practically identical. YMMV.