Search options (Page 10 of 18)

As I said, trt 10.0 is "one to avoid" because it cuts performance by around 30% while possibly doubling GPU usage.

They key phrase there is "may" have better performance. Yes I've tried this a couple of times. It's supposed to try to find more potential heuristics from what I understand but I didn't notice any real difference. But I can't remember if I have tried with my increased workspace so I might try again.

Two bits of news. A while ago I said that increasing the frame rate can help with certain fast movement artefacts. Well initial testing suggests that since v4.15 lite is actually "lite",  I'm now able to run SVP at 72fps and it is helping with certain specific types of fast movement artefacts. It's dropping exactly 12 frames a second which makes sense but the helpful effect is not being lost. I still need to do more testing but this looks promising.

Also, Tensorrt v10.0.0 is available. I couldn't believe how bad the benchmarks look but the notes confirm that this is definitely one to avoid.

Rife v4.15 lite has been released and I think it will become the new SVP standard. v4.15 lite handles fast motion artefacts much better than 4.16 lite and is very close to v4.15 but with much better performance

Quality: Rife v4.15 > v4.15 lite > v4.16 lite
GPU usage: Rife v4.15 > Rife 4.15 lite = Rife 4.16 lite

I think your final point makes the most sense, so I did some testing using the same scenes I always test with. Quality wise they are very similar although 4.16 lite might have a slight edge. Rife 4.16 lite also uses about 2% less GPU resources than 4.9. So yeah it looks like 4.16 lite might be worth the upgrade

Rife 4.16 lite is available to download. But if you are already using 4.9 then don't bother because it's more or less the same.

Update: OK did a little bit of testing and it might be worth upgrading to Rife 4.16 lite. The quality is seems to be at least as good as Rife 4.9 while using a little less GPU.

v2 is easier on GPU. Don't bother with Ensemble.

I've been downloading these file for months with not alerts and no one else is reporting this. Which AV are you using?

Maybe with the 4060 you are now trying and watching new things because it is a more powerful card? Are you sure that you are using the exact same settings with the two cards?

Oh right, good to know. After all this time still learning new things. Thanks

So after more testing I pretty much have a fixed mpv/SVP configuration for VR. Although knowing me, it won't stop me from tinkering. None of this is strictly necessary because SVP works pretty well out of the box.

For SVP I use Rife 4.13v2 with 12% SCT at 60fps fixed. I'm also using a later version of vsmlrt which has some extra code for playback buffering but this is not compatible with the default SVP helper scripts so I modified it to work.

For mpv the difference betwen using hwdec and not using it is about 1-2% in favor of not using it. YMMV. I also use interpolation with some motion blur. Overall motion was smooth enough before, but fast motion is now almost perfectly fluid so I am very happy with the results. Looking at the SVP manual, is it still the case that SVP runs after decoding but before rendering meaning that mpv is interpolating the output of SVP?

Yes it is.

Most configs for mpv on the Internet are out of date at best. But people will copy them verbatim without understanding. Blackfyre's config is his own and in previous comments I noted some unnecessary settings. This is another one, but I only started using "video-sync" myself in the last few days so I'm still learning.

As for the "display-resample" option, I don't need it to be on, but for me it seems to work well in smoothing out some of the remaining micro-stutters even without interpolation=on. But I watch stuff on a large VR screen so I will see micro-stutters that many wont. Because of that, my SVP setup including scripts will be different to most. Everyone's situation is different.