mpv shaders : terrible arifacts with temporal variants of nlmeans

[hooke007]

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.)

[Trinity3e]

How about with the lq ones?

[hooke007]

Similar blocks.

[AN3223]

Can you see if 31d545f helps? It appears to resolve it on my system, but the issue was always intermittent for me so it's difficult to be sure.

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.)

This is handled implicitly BTW.

[hooke007]

It helps but not enough...hq

[AN3223]

It helps but not enough...

What resolution is the source video?

[hooke007]

[AN3223]

Do you only see artifacts around motion now?

[hooke007]

No, I could even see them on those static color-testing clip.

[AN3223]

Is the clip 4K?

[hooke007]

Yes but 1080p also showed many dots.

[AN3223]

Ah, not sure then...

[hooke007]

It seem to be another vulkan bug (Nvidia). All variants work well with gpu-context=win (WGL)

edit: Confirmed gpu-context=winvk for AMD is safe.

[hooke007]

The workaround for windows Nvidia users:

• Use gpu-context=win instead;
• Or if using gpu-context=d3d11 , edit the value of RI RFI to be 0. (ref mpv shaders : blurring 、wrong color conversion and freezing #6 (comment))