From my quick test I can see that 4.22 fixed the edge artifacts and scene transitions seem better compared to 4.18, but interference patterns are a bit more obvious. I'll watch an entire episode of Dr. Who later to see if there are other problems sticking out.

dawkinscm wrote:
Xenocyde wrote:
flowreen91 wrote:

The devs fixed the smoothness issue:
https://github.com/hzwer/Practical-RIFE … 2275333756

I haven't noticed any smoothness problems since I don't watch anime. I only tested with my usual football scenes
and 4.21 still has the same edge artifacts as 4.20 in those scenes.

BTW, 4.22 is out. Maybe they fixed it with this one. Testing now.

4.22 is the fix he's talking about. It's a little better than 4.21 but overall it has the same artefacts.

Ah thought it was a 4.21 update, they don't actually mention 4.22 in the comments.

flowreen91 wrote:
Xenocyde wrote:

Can confirm the edge artifacts are still there in 4.21.

The devs fixed the smoothness issue:
https://github.com/hzwer/Practical-RIFE … 2275333756

I haven't noticed any smoothness problems since I don't watch anime. I only tested with my usual football scenes
and 4.21 still has the same edge artifacts as 4.20 in those scenes.

BTW, 4.22 is out. Maybe they fixed it with this one. Testing now.

dawkinscm wrote:
flowreen91 wrote:
flowreen91 wrote:

I agree, somehow v19 and v20 managed to break something and now they stretch the images instead of smoothly moving them vertically:
https://github.com/hzwer/Practical-RIFE … 2253162650

They fixed it in v21:
https://github.com/AmusementClub/vs-mlr … e_v4.21.7z

Nope. The dev says it's the same as v4.20.

Can confirm the edge artifacts are still there in 4.21.

Finally figured out what to do with HFR sources. My Doctor Who Season 10 is 50 fps by default and if I enable RIFE, my 60 Hz TV is not displaying 100 Hz or 125 Hz properly, so it's barely better than with RIFE turned off especially noticeable with panning shots. There is a simple fix for this, but it somehow did not occur to me until now: "remove every other frame" must be turned on. And of course fixed 60 FPS. That's it, that simple.

dawkinscm wrote:

Rife v4.20 has been released. I didn't do a large amount of testing but I did check the few remaining artefacts I know of and there doesn't seem to be a clear  difference to v4.15/v4.18 on my system.

I can see a slight improvement for some interference pattern artifacts, but 4.20 introduces other artifacts especially on the edges of the video in fast moving scenes.

I just had SVP trigger in "ignore HFR sources" profile, but I'm not really sure why this happened. I'm watching S10 of the new Doctor Who series and all episodes appear to be encoded at 25 fps according to MPV. However, starting with Episode 6, SVP is triggering the ignore HFR sources profile after saying it is playing at 50 fps. How does SVP identify some videos as HFR and some as non-HFR if all are 25 fps? Also, if I raise the video frame rate threshold from 47 to 60 on the ignore HFR sources profile, the RIFE profile gets triggered with fixed 60 fps, but some videos exhibit strange microstuttering as if they are not truly running at 60 fps, probably because of the threshold conversion. Any way to fix this?

Blackfyre wrote:
oriento wrote:

New version
4.19 (Add SportsSlomo) - 2024.07.12

Tested v2, worse than 4.16v2 (which is the main one I use). So back to 4.16v2 for me.

Tested normal and V2, they seem worse overall than 4.16 and 4.18.

Blackfyre wrote:

scale=ewa_lanczos
cscale=ewa_lanczos
dscale=ewa_lanczos
tscale=ewa_lanczos

dither-depth=10
dither=error-diffusion
error-diffusion=burkes

glsl-shader="C:\Users\USERNAME\AppData\Roaming\mpv\Shaders\FSRCNNX_x2_8-0-4-1.glsl"
glsl-shader="C:\Users\USERNAME\AppData\Roaming\mpv\Shaders\KrigBilateral.glsl"
glsl-shader="C:\Users\USERNAME\AppData\Roaming\mpv\Shaders\SSimDownscaler.glsl"

What are these for exactly?

dawkinscm wrote:
Chainik wrote:

dawkinscm
> One minute you are saying that I'm seeing garbage frames with IC.

you said you have "very sharp cut" with MVs, while it's not that sharp with IC
meaning you saw frame repeating with MVs and some kind of "soft" mixing with IC
dunno how I supposed to understand this in opposite way

I was going to say that this was probably a language misunderstanding but I felt you might be insulted by me saying that. But you still don't understand so that's clearly the issue. The key words "sharp" and  "jarring" used together like this is always bad. SVP and NVOF have "jarring" cuts means they have bad scene cuts.

I think what Chainik is trying to say is it seems counterintuitive to have sharp and jarring cuts with "garbage" AI blended scenes on SPV and NVOF, while IC has no sharp and jarring cuts with no "garbage" blending.

I tested a bit with 4.18 and IC 99%, as well as 25% and it seems like 25% has less microstuttering for me, although the scene changes present a bit harsher at times. Have to test with more content.

Guys, do I need to disable hwdec=auto-copy in config? MPV got updated and it reset my config file.

Heh, I wanted to report about my tests with the latest SVP update, but now I see Rife V4.18 is out.

I'll check the new Rife version and report on that too, but I can confirm that, with 4.15, SVP MV improved to the point it is almost the same as NVOF and IC. I can still see a bit more microstutter with SVP MV and maybe a few more artifacts.

I'll have to give IC 99% a try, have been using 100%. Also, with the latest MPV update, I can't remember if hwdec=auto-copy needs to be disabled in conf... please advise.

Did some testing last night to see how the new scene change detection options perform. With blend adjacent frames activated, SVP motion vectors shows the most artifacts with occasional microstuttering. NVOF and Image Comparison with SCT 100% seem to yield very similar if not identical results and show less artifacts with very little to no microstuttering.

Installed the latest update and I noticed the Duplicate Frame Removal drop-down switched to Remove Every Other Frame. Shouldn't this stay on Don't Remove, even with Image Comparison + SCT 100% + Blend Adjacent Frames?

flowreen91 wrote:
Xenocyde wrote:

Unfortunately I can still see microstuttering

I noticed that if i exit specific background apps like TeamViewer, i suddenly get 20-30 extra fps with SVP.
I believe TeamViewer reads the memory and causes a bottleneck even when it's minimized in taskbar.

Xenocyde try to close your 200 Chrome tabs and other background apps and see if u find the specific app that causes that microstuttering. It's good to know.

I uninstalled TeamViewer and I don't use Chrome cuz it's a RAM hog crappy browser. Firefox isn't perfect, but it's far less taxing, and I don't have 200 tabs opened lol. Oh, MPC-BE is only using 32% GPU power at most in 1080p @ 60 fps, so it's at least 10% better than MPV.

Don't think background apps and processes can influence microstuttering in my case. I'll monitor background stuff too but I tend to believe that the problems are linked to encoding at unpopular fps like 25 fps or something wrong with the source.

I've done some more testing with MPC-BE. Unfortunately I can still see microstuttering, but it looks like this is linked to improperly encoded videos or weird sources. I watched the first three episodes from The Boys S4 and haven't really noticed any micostuttering. On the other hand, all the episodes from Doctor Who S9 are encoded at 25 fps and leaving x2.5 multiplier results into frame skips every few seconds. If I switch to fixed 60 fps, the skips turn into occasional microstutter (at least 3-4 per 46-minute episode).

Drakko01 wrote:
Xenocyde wrote:
Drakko01 wrote:

Why dont you try MPC HC+Madvr+Rife for the content and framerate you want , your gpu has room to spare.

Isn't VapourSynth better for RIFE? I'm just looking to get rid of the microstuttering.

I don't understand your question I use Vapoursynth  with mpchc and Rife without the problem.

Question is which renderer is better with RIFE for mitigating microstutters: VapourSynth or MadVR?

Drakko01 wrote:

Why dont you try MPC HC+Madvr+Rife for the content and framerate you want , your gpu has room to spare.

Isn't VapourSynth better for RIFE? I'm just looking to get rid of the microstuttering.

pensioner600 wrote:
Xenocyde wrote:

Will test MPC-BE for microstuttering.

If you plan to melt above 160 fps, then I recommend version 0.7.1.2172 of mpcVR. Here (and in the following messages) it’s clear why.  The developer does not fix this error and wants a high-frequency monitor))
https://mpc-be.org/forum/index.php?topi … 18#msg8818

Lol, I wish my TV could push that many fps. I'm stuck at 60 fps for the moment roll Might not even get an OLED this year either.

Drakko01 wrote:

Do you unselect avisynth , the other thing its under utilities, set environmet variables for VapourSynth

I removed avisynth altogether, only vapoursynth is enabled. But I think I screwed something up now. After reading your instructions I thought it would be a good idea to uninstall and reinstall vapoursynth via SVP. Then I did SVP menu -> Utilities -> Set environment variables for Vapoursynth and now MPC-BE triggers SPV RIFE but I only have generic 4.4 as model and the TRT drop-down is gone. Halp!

L.E.: Looks like it accidentally uninstalled MPV and TRT when uninstalling Vapoursynth. I installed TRT and MPV again but now MPV would not trigger SVP and MPC-BE displays a warning in attached image over the video image. Think I need to install new TRT.

L.L.E.: OK think I fixed it. Overwritten the vsmlrt-cuda folder and vstrt.dll with the 9.2 version and both MPC-BE and MPV trigger RIFE now. Will test MPC-BE for microstuttering.

flowreen91 wrote:
Xenocyde wrote:

how do I force MPC-BE to always start with RIFE?

Go to Options -> External Filters -> move VapourSynth Filter to top and set it as Prefer

I followed the installation steps from here, which shows Avisynth. If I select VaporSynth, the filter does not show up in the play-filter list and it does not trigger SVP at all. I remember something about registering it... I haven't used MPC in almost a year.

Drakko01 wrote:

I think the lack of G-sync/freesync support causing this.
try the options video -> frame synch -> "Sync video to display" in MPC, it may fix the problem

OK I enabled sync to display but do we leave the default 0.0012 for frequency adjustment? Also, how do I force MPC-BE to always start with RIFE? Right now it defaults to SPV Automatic every time I load a video. I've seen this before mentioned here, can't find it now.

Can't find any downloadable Fast Sync plugin for MPC. Any link for this?

dawkinscm wrote:
Xenocyde wrote:
dawkinscm wrote:

Really? What made you decide today was a good day to call me a liar?

I just want to get to the bottom of this. Was not my intent to call you a liar, I was asking for the exact options you have there because I think having Power management Mode on Normal might cause more microstutters, I'm currently testing with Prefer Maximum Power.

I made it explicitly clear that I used to make changes the NV3D but now everything is back on default. I always double check before I answer questions about my system. If I'm not sure then I usually say that I'm not sure.

OK, so Prefer maximum Power is not helping. Maybe this is not NVCP-related.

pensioner600 wrote:

Mpc-be+mpcVR. If there is a global FPS lock in nvcp, then this lock must be turned off separately on the player. I also install the ancient and forgotten fast sync on the player; it is in this scenario that it works best. Never any stuttering or skipped frames.

I had fps limit set to 60 but removed that and it does not help. I use MPV though. I'll try with MPC-BE + mpcVR and fast sync.