Search options (Page 17 of 24)

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.

Not exactly. If you have a 3060ti you probably shouldn't upgrade to the 4060ti for SVP because they have similar performance. The 3060ti has a wider memory bus, but the 4060ti is using the latest generation Tensor cores, SMPs and Cuda cores which makes a difference. For example, an RTX 4080 is equivalent to the previous gen 3090ti so is much faster than a 3080. But the 4080 has less actual Tensor cores than a 3080.

Interesting. I guess we were all wrong lol But I did ask for a clarification and all I got was answers from everyone except @Chainik hence my assumption. But at least now we know what's actually happening. It is still all good

Two things.
First is @Chainik saying that I no longer need to use copy? The manual still says use "copy-back".
Second, I thought @Blackfyre said that there was no difference between d3d11va and copy and I didn't see those differences in pictures. To me that made sense because it the mechanism should have nothing to do with color. But I see there is a massive difference in the two pictures which I must have somehow missed. But a possible explanation for the difference would be that it is being affected by SVP which brings me back to my first point.
So still confused.

What happens to your performance when you use copy? I assume it goes down?

Not gpu-next. That has nothing to do with this.

Unless a dev comes on and tells me that the way SVP has always works has now changed, then whether you recognise it or not, using d3d11va and not d3d11va-copy means that SVP is not working properly.

You're kind of mixing up colour with banding but I get what you mean. I did say that hwdec can affect banding depending on the card and parameters used. What happens if you set hwdec=no? If you still have the same banding then the issue is definitely not the card or hwdec but is probably your display and its setup. If the banding disappears then you need to check your card settings.

One of the reasons mpc-be came out was because HC was a dead project. But I forgot that it has been restarted. I've updated my original post.

The reason you get better performance with d3d11va over d3d11va-copy is because with d3d11va SVP can't properly process the frames. d3d11va-copy copies frams to system ram where SVP has full access to them. So unless SVP has changed and somehow has direct access to GPU memory, you need to use copy. But you probably already know this and you were just joking.

No. One of the reasons I switched from mpc to mpv is that it works better with SVP at any resolution.

I've asked the ffdshow question myself a long time ago. I don't remember getting an answer so I just set it to false. With mpv there could be a number of reasons for frame drops including a bug in the stats page, the hwdec you are using or something else. Also make sure that the SVP index is not lower than 1.0 because if it is then you may have to use a less compute heavy version of Rife. You are just going to have to troubleshoot it. If it's not affecting what you are seeing on screen then maybe don't worry about it too much until you see a problem

The purpose of the "lite" versions were never fully clear to me except for Rife 4.14 "lite" which is different to every model that came before it. But there is no  answer to your question, you just have to try them and see which one works best for you. As of right now, if you don't have a high end card then don't bother with anything above Rife 4.9. Rife 4.13 is computationally heavy even for a 4080. Rife 4.14 "lite" is not "lite" at all unless you have a card with high memory bandwidth like a 'maybe' a 3070ti and above.