Search options (Page 3 of 21)

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

All I done was disable hardware-accelerated GPU scheduling. Restarted the PC, and it built after.

Didn't help though, none of 4.15 versions or 4.16 work at 4K without dropped frames on my RTX 3090

EDIT: This was a 'me issue', performance fixed.

You should be able to delete the old "Desktop" (your username should be there) from the manager and just install SVP on the new PC

So just scroll down and delete the old PC in the license manager, when you use the new PC that should become the new default.

RIFE + Dolby Vision do not work together from the last time I tested. Did something change?

Depending on the mpv configuration, you either get weird flickering, or inaccurate colours.

To be clear with this regard, I meant HDR10+ vs Dolby Vision. Whenever I have tested content, there is no difference between them, at least on my calibrated LG C2 and my configuration for MPV. They both look absolutely amazing.

HDR 10 is of course slightly inferior, but with HDR Compute Peak enabled for MPV, it performs pretty well too.

Yes, Dolby Vision still has flickering issues with RIFE. HDR 10 and 10+ both work fine for me. There is no visible difference between them when watching on my OLED display using MPV and my configuration setting. So don't worry about no DV support too much.

My RTX 3090 can barely do 2x video, so 48FPS at 100% GPU usage

So unless you're getting an RTX 4090, don't expect to do 4K at 60FPS or higher (not sure if the 4080 Super can or not, but you can ask in the RIFE thread).

Significantly better quality preservation, likes miles ahead of anything else. RIFE is a game changer.

---

The first time you run a different aspect ratio video with any GPU driver update it will take time to build RIFE Cache that takes a while to build, this only happens the first time you run a new aspect ratio though, after that videos play instantly with the same aspect ratio on the same driver versions.

Looks mostly good. I think it's similar to my settings before I started using RIFE, but honestly I don't remember them exactly as it has been a long time. RIFE through SVP, is a huge upgrade over traditional SVP, but if you watch 4K content at 4K, then I don't think the 2080 is strong enough, I have a 3090 and it's barely enough.

Consider changing Motion Vectors Grid to 28 or 32, the larger it is, the less visible artifacts from what I remember.

Motion vectors precision to One pixel, instead of half.

Artifact masking to 400 instead of 200 (strong is 200, strongest is 1000). Check the image below for how to do that, scroll down all the way until you find your TITLE name there, then go up to fi_masking and change it from 200 to custom value.

Strongest (1000) causes smoothness issues from what I remember, but between 400 and 700 was a great testing place for me.

Here's an image to show you all my settings, based on memory though, as I don't use them anymore.

You can visually see the difference in smoothness when GSync is working vs when it's not.

But also, you can check using the “Game Optimiser” settings with the LG Remote. When GSync is working, the frame rate corresponds with the refresh rate shown in the Game Optimiser, but when GSync is not working, it shows the highest refresh rate.

That's how I check it.

Regardless, the visual differences when HDR is enabled in Windows between d3d11va-copy and d3d11va occur whether running SVP or not as I wrote in the last post on the last page. So running at 24FPS default, which is outside the VRR range. When VRR is enabled, even when not triggered, it is causing crushed blacks and banding with d3d11va-copy. At least for me with the configuration I posted.

You can test these if you enable HDR under Display Settings in Windows Settings. Assuming you have GSync enabled in NVCP and the TV.

Test it with Ahsoka Episode 1 in HDR if you have that as the beginning sequence in space and the intro itself will show both. The logo's at the start will show banding with hwdec=d3d11va-copy below, and the dark scene after that has crushed blacks. But when you change to hwdec=d3d11va, both issues will resolve as VRR breaks.

End of above.

^ This comment should be interesting for @Chainik and the devs.

Without VRR everything works fine, no problems. With VRR I am pretty sure I tried them both the other day as well, and it was the same issues.

I'll test them again next time I update the driver and enable GSync/Freesync

^ SVP Developer btw haha ❤️

It's set to full and 10bit from NVCP, but I did not have:

video-output-levels=full

... in MPV config. I added it, but it did not fix the hwdec=d3d11va-copy problem with crushed blacks and banding.

Another thing to note, when in full screen banding is crushed, when I double-click to windowed mode, the black levels are not crushed. So, black levels are crushed only in full screen mode (which is the mode where VRR works).

EDIT:

with the above in mind, I disabled full-screen exclusive by removing:

ontop
fullscreen=yes
d3d11-exclusive-fs=yes

I enabled GSync in both Full-screen and Windowed mode from NVCP.

Opened a video, and when I double-click to enter full-screen (without exclusive mode), black levels still crush.

So it leads me to believe, it's something about VRR with this panel that I have that causes black levels to crush and banding to occur with d3d11va-copy.

The only reason d3d11va works properly, is because VRR is broken with that one.

The example above in the pictures is Ahsoka Episode 1 with HDR and VRR (Gsync) enabled. The start of the episode sequence is a good dark environment test.

On the LG C2 42"

I don't think this is an issue for VRR monitors or QD-OLED displays though, so I don't think it applies to most people.

It's just a me issue I guess trying to get VRR to work with the C2 + RIFE + SVP + MPV

Also to note d3d11va-copy work fine without HDR enabled, no banding or crushed blacks. With HDR enabled only d3d11va works correctly, but VRR breaks.

EDIT: