pauzel wrote:
dawkinscm wrote:
pauzel wrote:

VD only supports half res over under, not full res. I am not sure if frame interpolation plays well with the anisotropic distortion from half res, also SVP has no half res over under 3D mode. But maybe it still works fine, have not looked into it too much.

Again. Not true.

Maybe actually read what I write before calling it BS? I did not say anything about MPC-BE not supporting full res over under, I said VD is not supporting it. Anyhow, nobody forces you to use my change, and frankly I will refrain from providing any more of my code changes if as a response I get a bunch of passive agressive nitpicks.

What I said which is that "it's a good idea to have full SBS support" followed by a smile emoticon of support for your idea.  This was a mistake on my part because I used VD with full over/under for years and didn't see a difference in resolution in my visor. I put my evidence in front of you and you pointed out the error. You should have left it at that. Anyway I'm out. Have fun.

pauzel wrote:
dawkinscm wrote:
pauzel wrote:

In case it is useful for sb, I added (let Codex/GPT 5.5 add) full res SBS view mode to MPC-BE: https://github.com/pauzel/MPC-BE/pull/1/changes. Seems to work fine. I also can provide my build of the installer if sb needs it. I needed it since Virtual Desktop for VR does not support other formats provided by MPC-BE.

Not true. VD supports over/under which is how I was using MPC-BE with VD for years. I've moved on, but it's a good idea to have full SBS support smile

VD only supports half res over under, not full res. I am not sure if frame interpolation plays well with the anisotropic distortion from half res, also SVP has no half res over under 3D mode. But maybe it still works fine, have not looked into it too much.

Again. Not true.

pauzel wrote:

In case it is useful for sb, I added (let Codex/GPT 5.5 add) full res SBS view mode to MPC-BE: https://github.com/pauzel/MPC-BE/pull/1/changes. Seems to work fine. I also can provide my build of the installer if sb needs it. I needed it since Virtual Desktop for VR does not support other formats provided by MPC-BE.

Not true. VD supports over/under which is how I was using MPC-BE with VD for years. I've moved on, but it's a good idea to have full SBS support smile

I'm still learning about SVP settings and effects. Quite a few settings and overrides can increase the ghosting/halo effect around people. I had to re-add some previous overrides and my current settings are now a mix of old and new. That's because I had to almost totally re-do them to keep smooth motion.  For those who can see the halo and who also like to play smile The following can increase the ghosting effect:

SVP Shader: Simple, Complicated. I'm still using "Standard".
Search Radius: Small <-- This was my default. Now using Average.
Decrease Step Grid <-- Global refinement was my default. Now disabled.
smooth.mask.area override set higher than default.

So unless you see ghosting and it annoys you (like it does me), then it's just another marginal gain. The basic settings work well enough and it's probably not worth the effort.

Drakko01 wrote:
Chainik wrote:
Ironclad wrote:

Does Vapoursynth R74 break compatibility?

at least it isn't a simple drop-in replacement

Why not? i am testing R75RC1 right now.

Because there are apparently breaking changes to the API with R74 (this needs to be verified). Maybe SVP isn't affected but there doesn't seem to be any real major advantages to upgrading either.

Just an FYI. Running SVP using the above settings doubles the power usage and adds an extra 10% GPU overhead (max) and 30% extra CPU usage. This is with a high end Nvidia GPU and an efficient AMD (or latest gen Intel) CPU. So if you are anywhere near your CPU/GPU limits then this will put you over. Surprisingly, the overrides only account for about 2% of the usage overhead but they do add an extra 5-10w of the power draw.

Some of you said that my SVP settings worked well at 60fps without the overrides. Well they also work well at 120fps too which makes sense. So for most people I would stick with those and no overrides. But if your GPU and CPU can handle it, then the following changes to my original posted settings get even better results with no overrides. But of course YMMV.

Motion Vectors Grid: 8px /* Overkill. 12px - 16px  is probably better for most systems */
Decrease grid step: Local Refinement
Artifacts Masking: Personal preference.


But for those with strong Nvidia GPUs, these next "two" overrides do increase smoothness on a very large screen. But they can also overwhelm SVP and cost at least an extra 20 (GPU) Watts for what are effectively only marginal gains.
---------------------------------
    levels.pel                                    = 4;  /* Overkill */
    analyse.refine[0].search.satd    = true;  /* Definitely Overkill But works well without the previous additional overrides */
---------------------------------

With the right Artifacts Masking (I still use mask overrides), any of the settings above will hopefully get you the same RIFE smooth motion and motion clarity without the nasty RIFE artifacts.

Chainik wrote:
dawkinscm wrote:

The second issue might not be an issue in that SVP reports 1920x1080 for even though the file itself is actually 3840x2160.

why it tells "+3D SBS"? is it really 3d sbs? then why 3840*2160? or the file name contains "sbs" tag? or you turned this manually, then why?

Yes. I meant 3840x1080 (not sure why I typed 2160). So SVP is only telling me about half of the frame?

narkohol wrote:

Is there any kind of configuration that works well for cases like this one?

https://www.youtube.com/watch?v=emZZexE … UGZXhpdCA4

It's all white tiles with straight black lines everywhere. It was the only time I had to fully disable any FI, because it was a constant hell of artifacts with anything I tried...

I can't get SVP to recognise that it's playing in mpv lol so I can't test it. I even removed the time clip limit by setting it to zero. Also expecting zero help from certain devs smile

dawkinscm wrote:

... and maybe @Chainik can help.

Or not.

ITN wrote:
dawkinscm wrote:

Good or bad genuine feedback is useful and always welcome so thanks for the update smile

I have 98003d & RTX 5090, regular svp is no issue hardware wise with those overrides. Your settings seem very good for most content, might need to do a separate rife profile for harder animation. Stuck with 60hz as that is the only one my 4k dlp does well. But thanks for sharing the settings.

With that hardware you should have almost no issues with any content. I watched Super Mario up-scaled to 4K and the only difference is that I watch at 120Hz, not 60Hz. There is something I've noticed that might explain all of this and maybe @Chainik can help.

Well actually two things. First since I moved away from RIFE and started using SVP when I hover over the SVP icon in the system tray, it says "Paused" even while it's playing and clearly affecting the content. This probably ties into why the SVP Index graph shows N/A. If I reset everything the SVP Index graph starts working again for a few minutes then stops. So maybe it's the monitoring that is "paused"? The second issue might not be an issue in that SVP reports 1920x1080 for even though the file itself is actually 3840x2160. I've attached an image showing the two issues.

Chainik wrote:

just tried latest TensorRT 10.16 libs, and ... they're like 10% slower than good old 10.8 bundled with SVP, on both 4070 and 2060 cards hmm

also tried TRT-RTX backend, which doesn't require 2+ GB of libs and with much faster engine build process
and it really works, even 10% _faster_ on 4070 (but 20% slower on 2060)
BUT it takes 15+ seconds for start-up, or after every timeline seek

Does TRT-RTX make any difference to RIFE quality and artifacts? I assume the answer is no because it is more to do with the engine and how it is trained. But it would be nice to have conformation from someone who has actually used it.

ITN wrote:

@dawkinscm

Your settings worked very well with 60hz on film content, tried with those overrides. Unfortunately with cg animation at least they were full of artifacts. I tested with the Super Mario movie, original SVP always has issues with this one. Rife handles that one very well.

I'm glad it works well for you. Strange about Super Mario Movie as I have no issues. But that's in 120fps which as I said is paradoxically easier to smooth than 60fps. I was going to look into 60fps smooth motion but then someone essentially told me not to bother so I didn't smile

BTW, just a reminder that the CPU, GPU and SVP are 3 separate choke points and from the feedback I have seen so far, these settings (minus the overkills) are relatively safe and work well within those boundaries. I bring this up because I have made two small changes to my settings since I last posted. The main one is a reduction in the mv_gridsize, but I also turn Wide Search back on.  With overrides at 4k (3840x2160) resolution and 120fps, even these minor changes might stress some CPUs, kill many GPUs and are close to the SVP processing limit depending on the scene. If you want to experiment then my advice is to remove the overrides if you are using them (or at least the "overkills") ant try out different combinations of GUI settings. You might be surprised at the difference even small changes can make.

Good or bad genuine feedback is useful and always welcome so thanks for the update smile

14

(5 replies, posted in Using SVP)

abraxas wrote:
dawkinscm wrote:

I don't get it lol I've posted many, many times that my settings are not for RIFE and I'm not at all interesting in using RIFE which is why I hadn't thought about the overrides.

I was just trying to help... your settings are great if you (and me) want to skip RIFE. But the contents of overrides.js prevented me from switching to a different profile. At least that’s what happened to me. This isn’t a criticism of you or your settings—JUST A NOTE ON what might be the cause if changing the settings in SVP suddenly doesn’t result in any change in playback.

I’ll do the same as you from now on—no more helping out in this matter. It’s better that way:D

Easy there fella. I did not think that you were criticising my settings and you did help. Maybe you missed my update, but I followed your helpful suggestion and was able to hopefully help a little too smile

15

(5 replies, posted in Using SVP)

abraxas wrote:
dawkinscm wrote:

I haven't used RIFE for a while. When I tried to use it today it didn't crash, but it didn't work either. It wouldn't do anything. I kept trying and eventually SVP stopped listening video playback from mpv player. I reset all the settings to default and it started working again but RIFE still doesn't work. Driver: 595.97. Nvidia 50 series card.

I had the same problem yesterday after adding your settings to overrides.js. Try commenting them out (probably not all need to be commented out; I didn't evaluate this) - it might work, as it worked for me smile

I'm thinking... can I check the current profile in overrides.js? Then the settings/overrides could be made conditional.

I don't get it lol I've posted many, many times that my settings are not for RIFE and I'm not at all interesting in using RIFE which is why I hadn't thought about the overrides.


dwoods0381 wrote:

I keep getting crashes since I update nvidia driver when using rife models. Using Automatic settings at the moment, but i would like to fix using rife ai models. Anyone else have this problem, or any ideas to fix?

But since I was trying to help a brother out so I temporarily removed the overrides and RIFE works fine with driver version 595.79. No crashes.

16

(5 replies, posted in Using SVP)

I haven't used RIFE for a while. When I tried to use it today it didn't crash, but it didn't work either. It wouldn't do anything. I kept trying and eventually SVP stopped listening video playback from mpv player. I reset all the settings to default and it started working again but RIFE still doesn't work. Driver: 595.97. Nvidia 50 series card.

berpo wrote:
dawkinscm wrote:
abraxas wrote:

I'd also love to see the overrides, because the settings you just posted are already working extremely well here (120 frames per second, and the 4070 GPU is 30-40% max). The few artifacts can certainly still be "masked."

I've had a few people PM me for them and I sent them with notes.  I'm very happy that the basic settings are working well for you and it's probably all you need. With my current settings including overrides the 1% frame pacing average is around 8.4ms over wifi.  The combination 4k content on a very large screen being streamed over wifi makes even the smallest jitters more obvious which is why I monitor even the 1% averages. For most people the overrides are very overkill and no one in their right mind is monitoring frame pacing for watching movies lol. But if there is some traction for me to post them then I will.

+1 vote for you to post them, or PM them to me if you'd rather. I originally bought SVP to play with RIFE but after experimenting and reading some more I came across your basic settings and was much happier with the results. I'm using a 9700X and a 3080 Ti and have some good headroom to do 120 fps, but I've also realized the importance of keeping frametimes from getting out of hand.

Thanks. Assuming you do have the headroom then I think 120fps is actually easier to make smooth than 60fps because it is a multiple of 24fps. Below are the overrides with notes.

Remember this is for my setup. 4K streamed over WiFi at 120fps on a "very" large screen. I've labelled the ones I think might not be needed for a standard TV.

==================================
levels.pel                                    = 4;  /* Overkill */
analyse.main.search.type             = 4;
analyse.main.search.coarse.width = 3840;   /* Definitely Overkill */

/* Definitely Overkill and no longer using because it "kills" SVP when mv_gridsize is reduced smile */
analyse.refine[0].search.satd    = true; 

/* Overrides "Artifacts Masking" setting */
smooth.mask.cov      = 300;
smooth.mask.area     = 300;

smooth.mask.area_sharp    = 1.3; /* Personal Preference */

/* TBH I would love some help on better understanding the settings below. But from what little I do understand these work really well for me */
analyse.main.penalty.lsad        = 16000;
analyse.refine[0].penalty.lsad   = 12000;
analyse.refine[0].penalty.lambda    = 20.0;
analyse.refine[0].penalty.pnew       = 100;

abraxas wrote:

I'd also love to see the overrides, because the settings you just posted are already working extremely well here (120 frames per second, and the 4070 GPU is 30-40% max). The few artifacts can certainly still be "masked."

I've had a few people PM me for them and I sent them with notes.  I'm very happy that the basic settings are working well for you and it's probably all you need. With my current settings including overrides the 1% frame pacing average is around 8.4ms over wifi.  The combination 4k content on a very large screen being streamed over wifi makes even the smallest jitters more obvious which is why I monitor even the 1% averages. For most people the overrides are very overkill and no one in their right mind is monitoring frame pacing for watching movies lol. But if there is some traction for me to post them then I will.

adrianaaolsen wrote:

For fast action scenes stability is usually more important than pushing every setting higher. A slightly lower mv_grid with moderate mv_refine can reduce artifacts like ghosting. Also, keeping mv_radius balanced helps avoid motion errors in quick cuts. It’s often better to tune for consistency rather than maximum sharpness.

I tried lowering mv_grid and it did made one of the few remaining artifacts I have almost invisible. But with certain scenes my CPU usage skyrocketed and frame rate went from 120fps to single digits because of my override settings. I guessed which one, removed it and everything is back at 120fps, even the more complicated scenes. Still can't get rid of the mild ghosting, but it only appears occasionally has maybe even improved a little since lowering mv_grid. Cheers for the suggestion.

Xenocyde wrote:
dawkinscm wrote:
Xenocyde wrote:

Welp, I'm stuck with 60 Hz for now, so your ideas are welcome. Maybe we can take this into the DMs.

Sorry I've just realized. You will need to enable Artifacts masking. My masking settings are in the overrides. I've DM'd them to you. Apologies again.

Woah OK. Will test these. Hope my RTX 4080 is enough for 1080@60hz with these.

I had a 4080 and from what I remember, these settings would have stretched it a bit. But I've highlighted the overrides I think are "overkill" smile

Xenocyde wrote:

Welp, I'm stuck with 60 Hz for now, so your ideas are welcome. Maybe we can take this into the DMs.

Sorry I've just realized. You will need to enable Artifacts masking. My masking settings are in the overrides. I've DM'd them to you. Apologies again.

Xenocyde wrote:

Welp, I'm stuck with 60 Hz for now, so your ideas are welcome. Maybe we can take this into the DMs.

Yes we can do that. Just be aware that because I'm watching on a very large screen, I not only see micro-stutters, I see (what I call) nano-stutters. So as I've said before, I think my overrides are overkill for most people. But anyway, below is a screenshot my basic SVP config without any overrides.  You will need a decent Nvidia GPU if used with the overrides. I will DM them to you if you wish.

Xenocyde wrote:
dawkinscm wrote:

I didn't say SVP "Automatic" is better. I said "SVP" is better. RIFE and "Automatic" are just configuration profiles with two levels of customisation. Level 1 customisation is creating a new profile by making a copy of an existing one then manually changing the individual settings. Level 2 customisation uses"overrides" to change the default values of  low-level internal SVP settings. When time is taken to test and set these attributes correctly, you end up with smooth RIFE-like motion with far fewer artifacts. This is what that makes SVP profiles more flexible than RIFE and why you "can" end up with better results than RIFE.

Much of the information needed is in the SVP manual, but some more esoteric information about the overrides is spread among this forum's posts.

Actually RIFE and Automatic use completely different interpolation methods. Anyway, I have a customized RIFE profile too, but wondering what exact settings you have modified on your profile.

Of course they use different interpolation methods. That's the whole point lol.

I stopped using RIFE a few months ago. As to my customized SVP profile, I posted them to a previous thread with other customized profiles, then I removed them after I was told they were useless by guess who lol. But looking back, my profiles weren't much better than the ones in that thread. Way too many overrides, when the SVP default settings are 'usually' best. I don't think I want to go down the posting my optimisations route again. Plus it's really only for 120Hz and maybe frequencies above that. Also, I think it's more difficult to achieve RIFE-like smoothness with 60Hz but I have some ideas smile

Xenocyde wrote:
dawkinscm wrote:
osudahiuhsdfg wrote:

Yes I did find RIFE to have too many problems in movies for sure, so sticking to standard algorithm seems like a good call! Still pissed I can't get RIFE to work though. I hope it's a weird glitch and not a bad GPU problem.

SVP is better than RIFE so I wouldn't worry about it.

Are you guys saying SVP Automatic is better than SVP RIFE or that the SVP implementation of RIFE is better than the stand-alone RIFE?

I didn't say SVP "Automatic" is better. I said "SVP" is better. RIFE and "Automatic" are just configuration profiles with two levels of customisation. Level 1 customisation is creating a new profile by making a copy of an existing one then manually changing the individual settings. Level 2 customisation uses"overrides" to change the default values of  low-level internal SVP settings. When time is taken to test and set these attributes correctly, you end up with smooth RIFE-like motion with far fewer artifacts. This is what that makes SVP profiles more flexible than RIFE and why you "can" end up with better results than RIFE.

Much of the information needed is in the SVP manual, but some more esoteric information about the overrides is spread among this forum's posts.

adrianaaolsen wrote:

For fast action scenes stability is usually more important than pushing every setting higher. A slightly lower mv_grid with moderate mv_refine can reduce artifacts like ghosting. Also, keeping mv_radius balanced helps avoid motion errors in quick cuts. It’s often better to tune for consistency rather than maximum sharpness.

For 120Hz the default 16x16 grid seems to work best for me. After reading your post I tried a few things out and you are right about mv_refine. But for my current settings I need Global step decrease for smooth motion so I do get some mild ghosting which if I was watching on a TV screen I probably wouldn't see.