KNLMeansCL: OpenCL NLMeans de-noising algorithm [2018-01-29]

[Khanattila]

--> pinterf's fork

--> https://github.com/Khanattila/KNLMea...ses/tag/v1.1.1

KNLMeansCL v1.1.1
* Added more check of rclip.
* Fixed build programm error in some circumstances. 
* Fixed Avisynth YUV444P10 video format.
* Fixed Vapoursynth RGB30 video format.
* Fixed clip processing with higher resolution than 4K.

KNLMeansCL is an optimized OpenCL implementation of the Non-local means de-noising algorithm. The NLMeans filter, originally proposed by Buades et al., is a very popular filter for the removal of white Gaussian noise, due to its simplicity and excellent performance. The strength of this algorithm is to exploit the repetitive character of the image in order to de-noise the image unlike conventional de-noising algorithms, which typically operate in a local neighbourhood.

For end user KNLMeansCL is a plugin for AviSynth, AviSynth+ and for VapourSynth. Windows, OS X and Linux are supported. Read more on the Wiki.

KNLMeansCL is available under the GNU GPL v3 license.

FAQ
Q) I can't make DGNV and KNLmeansCL work together in avs script.
A) Post #664.

[Groucho2004]

Works right out of the box (well, apart from the obligatory MS*120.dlls) unlike the original NLMeansCL which I never got to work properly. Seems very fast as well, even on my lowly GT240 card.

Awesome!

[Groucho2004]

Originally Posted by Khanattila

NLMeansCL(clip src, int A, int Ay, int S, int Sy, int B, int By, float aa, float h, bool sse, string device_type, int y, int u, int v, bool info)

That should read "NLMeansCL2".

[Khanattila]

Originally Posted by Groucho2004

That should read "NLMeansCL2".

thanks

[Khanattila]

Edit.

[Reel.Deel]

Thanks Khanattila, very nice indeed. Briefly tested it on my GTX780 and it's pretty fast. What source filter did you use for the benchmark? Also, any interest in showing some love to Y8?

[Mounir]

Still no support of YUY2 ? What about temporal denoising ??

[Reel.Deel]

Originally Posted by Mounir

Still no support of YUY2?

Use the planar equivalent YV16 instead.

[TheFluff]

why would you ever want yuy2 support

[Khanattila]

Originally Posted by Reel.Deel

Thanks Khanattila, very nice indeed. Briefly tested it on my GTX780 and it's pretty fast. What source filter did you use for the benchmark? Also, any interest in showing some love to Y8?

Y8 support? It's easy, I will add in the next release.
For benchmark... I use AVSMeter.
To get a clean result, you should subtract the time of ffms2 & co.

Example:
ffms2 + Dither_convert_8_to_16() -> 326.4 FPS -> 3.0637 ms for frame.
ffms2 + Dither + NLMeansCL2() -> 60.46 FPS -> 16.5399 ms for frame

So NLMeansCL2() take 13.4762 ms for frame -> 74.2 FPS

[feisty2]

gorgeous
add temporal mode maybe?

[Bloax]

Testing on an ancient 9800 GT I didn't expect much, but it turns out that it still works!
Unless you set U=3,V=3 or the input isn't YV24. (although it works fine with YV12 if the UV channels aren't set to be processed) :v
or if you set the A value too high (a >= 10)

[Khanattila]

Edit.

[Bloax]

I can confirm that A >= 10 (output isn't buggy garbage even at a=21) works now, as does chroma processing.

[Keiyakusha]

Wow, one of my favorite filters reborn without these annoying dependencies! Haven't tried it but still nice!

As for temporal, I remember Malcolm gave up on it cause it didn't produced decent results and his recommendation was something like "Just use MVTools". That's why temporal thingy in his plugin is buggy, was never completed and v0.4 branch abandoned.

[feisty2]

az works nicely on tritical's original version, is it very hard to port it from cpp to opencl? sorry, i got little programming knowledge, dunno much about it

[Khanattila]

Originally Posted by Mounir

Still no support of YUY2 ?

YUY2 is packed.
NLMeansCL2() with YUY2 support have the same performance of YUY2Clip.ConvertToYV16().NLMeansCL2()

[Reel.Deel]

Originally Posted by Khanattila

Y8 support? It's easy, I will add in the next release.

Y8 support would be great

Originally Posted by Khanattila

YUY2 is packed.
NLMeansCL2() with YUY2 support have the same performance of ConvertToYUY2().NLMeansCL2()

Shouldn't it be ConvertToYV16().NLMeansCL2()?

Edit:
Might be worth mentioning that NLMeansCL2 already supports YV16/YV24.

[Khanattila]

Originally Posted by Reel.Deel

Y8 support would be great



Shouldn't it be ConvertToYV16().NLMeansCL2()?

Edit:
Might be worth mentioning that NLMeansCL2 already supports YV16/YV24.

yes in both cases

[Khanattila]

Edit.