Search options (Page 7 of 19)

I've found that the key to the best picture quality is basic picture calibration. Get the brightness, contrast, saturation and gamma right and 90% of the work is done. You need a calibration disc like Spears & Munsil for this. Like @Blackfyre, my MPV config has evolved over time and is now much simpler. MPV has been around for years and its defaults are set after dev testing, discussion and years of user feedback, some of which I have read.

I set SVP downscale to Bilinear to remove any obvious sharpening done by SVP. Lanczos is a great default but even with the mildest MPV scaling algorithm I sometimes see bad effects like ringing when used with SVP sharpening. This is NOT a problem with SVP, just a consequence of double sharpening so I want full control over sharpening post downscale.

I use Lanczossharp which is the default scaler. For movies on a large screen it's not actually that sharp, but it might be the most natural of the sharp scalers. For additional sharpening I use Contrast Adaptive Sharpening because it gives more fine tune control. But you can get a similar affect with a lot less hassle using the Adaptive Sharpening shader and others. Maybe also SSIMDownscaler.

First here's the appology I owe you. I must have been reading with old, assuming eyes

As for the shaders, just like Rife, a lot of this applies to Anime and results are based on machine generated scores. I've had almost every shader in my config at one point or another including the 3 above. Krig is technically it is better than default but visually speaking the difference myself and others have found is negligible. Since I read that it can generate also errors I stopped using it.  SSSimDownscaler might be great for Anime but when used with video content it's too sharp even for me, but especially when tested with calibration tools. FSRCNNX is a GPU killer for anything above 1080p. I've been using it to upscale low res poor quality content but i recently removed it because like the other AI based upscalers it made little visual difference. That's why I initially said that it's personal taste and machine generated scores.

Nowadays I mostly use in-built scalers.

Thanks for this. There's nothing in your config that makes a difference for SVP and we've already had the discussion about config lines that essentially do nothing or are even contradictory. But if you are happy with the picture then I suppose it doesn't matter However I am interested in the error-diffusion you chose so I will try that out. Thanks

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.