Search options (Page 6 of 18)

I was going to say that this was probably a language misunderstanding but I felt you might be insulted by me saying that. But you still don't understand so that's clearly the issue. The key words "sharp" and  "jarring" used together like this is always bad. SVP and NVOF have "jarring" cuts means they have bad scene cuts.

When something is "jarring" it is bad which is why "I didn't like what i saw". I can't even begin to understand where you are coming from when what you are saying is contrary to what I have said, but more importantly it is also contrary to what we are seeing. One minute you are saying that I'm seeing garbage frames with IC. Then when it's clear that myself and others are not seeing the same thing, now you are saying something else.

So let's just get back to the point I have been making since the start. There is an issue with SVP and NVOF and @flowreen91 has kindly demonstrated it. We all want SVP to be better so if it can be fixed then great. If not then we will continue to use IC.

To summarise my previous comments: I did not see the Rife "garbage" frame shown in Rife.jpg for IC but I am seeing it for SVP and NVOF.

They do all look almost identical. But the issue is that I am seeing the opposite to @Chainik. I see f1 and f2 with IC and Rife.jpg with SVP and NFOF. He says he sees Rife.jpg with IC.

He throws the cloak at 9:32 which catches her at 9:33 then the scene change happens. It's a sharp cut but I never noticed it before until I used SVP and NVOF.

All 3 "see the scene change" but two of them makes the scene change look like a jump cut. There's a difference between reacting to the scene change and over-reacting to it. We are grateful for SVP and so we are only trying to help you make SVP even better. But in this particular instance you seem determined to not even try to understand what we are saying.

So I think this is actually an SVP fix for image scaling rather than a Nvidia/Microsoft fix. I mentioned previously that I had issues with Dr Strange 2 but that's because it was 3D SBS and for whatever reason SVP did not handle it correctly. But since the latest updates, it is handled in the same way as files of the same resolution in other 3D and non 3D formats.  Correct scaling is responsible for the improvement I see with my GPU, not Nvidia/Microsoft.

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.