Search options (Page 1 of 24)

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.

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

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.

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.

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

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.

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

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

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.

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.

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 */
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;

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.

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.