Search options (Page 5 of 17)

Ahh yes that's it, it turns off SC not Rife. It was late and I was tired lol. 15% works really well and I remember saying the before the update, 15% and above behaved the same for me. But SVP has been updated and I see that 25% behaves a little differently to 15%, so I will give 99% and 100% a try.

That's like what I was seeing in Alita at certain scene changes where she was skating.

Apologies this one was my mistake. Yes those scenes have always caused me issues but not with v4.15 or v4.18. I was in the middle of testing GPU vs CPU using v4.9 for comparison and forgot to change back to v4.15/18. With v4.15/18 those scenes work fine. However the reduction in GPU usage and moderate increase in CPU is still there. BTW There's another movie scene I recently added for testing which had artefacts even on v4.15, but with this recent SVP update they are gone.

Something interesting is happening. Before in order to reduce GPU usage for my 1920x2160p movies I had to reduce screen size using SVP, even though my screen was set to 1080p. I no longer need to do this. There was another related issue with a 3D SBS file that didn't work properly which now works fine.  This means that I have now regained control over the downscale rather than relying on Vapoursynth downscalers. I thought maybe that Rife wasn't working because there is a bug in SVP where it sometimes runs but is not actually interpolating. But the test scenes are smooth and my GPU is running under 40%. But CPU load doubles when in use so maybe more of the load has been handed off to it.

No! I prefer a smooth 60fps motion where an action is clear without jitter or stutters. That's why I paid for SVP, but apparently I was mistaken. Good to know.

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.

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

I know everything over 15/25% is similar. Actually I was the first one to point out that everything over 15% is similar But that's what I found worked best with version of MPV that comes with SVP. I've done more testing and found that my later version behaves as before which is a little different to MPV v0.36.
With 0.37 I find that 15% is the smoothest of should mean anything 15 and above but that's not the MPV that comes with SVP so I didn't update my results.

I test with a lot of different types of movement and  I've been using the same test scenes for maybe a year or more so I am very familiar with the artefacts being generated by Rife or in this case by SCT. I also watch on a very large screen so I am able to see every microstutter and even the smallest artefacts.

In the end all of this stuff is setup dependant and YMMV

Thanks for the update. I decided to completely reinstall everything to remove any changes I made. The results so far are that
- SVOP and Image Comparison and disabled give very similar results.
- NVOF might be a little worse overall but still similar.
- This is the same as before except that all of them feel a little less smooth than the previous setup with SC set to 100.
- Setting SC to 100 with this new software seems to be similar to the others as well. Although when I add back the MVP interpolation code that helps. I also put back the TensorRT9.2 files.

Let's see what others say.

The v4.17 lite version is an experiment and from what I see, it's worse than even v4.17.

I made it explicitly clear that I used to make changes the NV3D but now everything is back on default. I always double check before I answer questions about my system. If I'm not sure then I usually say that I'm not sure.