an3223 / dotfiles Goto Github PK

When using the shader of nlmeans to test its noise reduction effect in some videos, I noticed that it produces severe texture smearing behavior, which did not occur in its filter version.
test file: sample.zip

nlmeans.glsl

vf_nlmeans

state:

• blurring
• color conversion
• freezing (d3d11)
  👉 workaround #6 (comment)

b971e89

guided_lgc : wrong color conversion

nlmeans : would make mpv freezing when using gpu-api=d3d11

I am currently using this script which cycles through lavfi's denoise filters, how does nlmeans compare?

Similar to how the script above cycles filters by continuously pressing one key, what line would I put in my input.conf to cycle between the default, medium and heavy nlmeans shaders?

Since this commit: mpv-player/mpv@a92466c

Figured you might be interested because of your auto-save-state.lua script.

More shaders have been added, could you please share more info about the nlmeans shaders' variants?

Are the nlmeans shaders geared towards live action media?

If they are, would you be interested in making denoisers specifically for anime, something like the Anime4k shaders but better?

8c7b696

It only tries to blur some color but doesn't change anything else.

You seems to forget to handle the size after chroma bind?

I know they are "Very experimental and buggy"
Open an issue to record its behav may be better.

I only tested the shaders in hq folder. d682103

Sometimes the artifacts were dots instead of blocks.

The one possible reason is that the lack of scene's changing's detection algorithm ?
It's obvious those wrong pixels come from the last frame.(Also some next fram's pixels come into the last one.)

Hi, I tried setting SF to various values but apparently nothing happens, scale still kicks in, do I need to intervene somehow else?

//

If it works with chroma, can it be made aware of color space so it automatically doubles the scaling vs luma for most 4:2:2 formats? Cause KrigBilateral is broken in gpu-next and nlmeans can replace it this way (even without the bilateral luma-influenced scaling)

//

Also, offtopic, can RF=guided disable itself if the frame rate is high (cause it does take a performance hit then)?

LE2: Patch donut seems to work a bit in temporal, don't remove it yet :-)