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

[Xebika]

It worked fine.

[Khanattila]

v0.6.1 release: https://github.com/Khanattila/KNLMeansCL/releases.

It corrects an error that I had introduced in the previous version.

[tormento]

Originally Posted by Khanattila

v0.6.1 release

Even this version doesn't work for me with DGDecNV. It works for every other SW/HW decoder plugin.

Same green screen in preview with message "CUDA ERROR!".

[MysteryX]

This version gives me this error:
KNLMeansCL: AviSynthCreate Error (clBuildProgram!)

[detmek]

Originally Posted by MysteryX

This version gives me this error:
KNLMeansCL: AviSynthCreate Error (clBuildProgram!)

Same here. I use it with StaxRip x64 and Avisynth+. Same error with 0.6.0. Builds up to 0.5.9 work just fine.

[MysteryX]

I'm using AviSynth 2.6

Also, KNLMeans is giving me better results than FF3DFilter on most videos, but why is it giving me such bad output on this video? The lines in the background end up being very jerky (I know, the source video is bad quality), but FF3DFilter is doing a MUCH better job in this particular case. In most other videos with similarly bad quality, however, KNLMeans gives a better output.

Here's the video
https://mega.nz/#!CNICBS5S!56wGjk8gt...k4ms8mPXFr0nkY

KNLMeansCL(D=2, A=1, h=3, device_type="GPU")

[Sparktank]

Win7 (x64) SP1
GTX 750 ti
GeForce 355.82 (newest; although I don't think much changed as far as video processing goes, mostly just new games)

KNLMeansCL v0.6.1

SetMemoryMax(512)
LoadPlugin("C:\AVS\dgdecnv2049\DGDecodeNV.dll")
DGSource("E:\Demux\Scream\Scream.dgi", crop_b=140, crop_t=132)
#KNLMeansCL(D=2, A=1, h=3, device_type="GPU", info=true)

"jerky lines in the background"

I don't see "jerky lines" in the sample video.
I grabbed a demux of the poorly mastered BD for Scream, since it's noisy and messy.
(Canadian BD Region A, identical to USA BD)

(all images are "large thumbnail", click to follow to original size (1920x816)
Here's original Frame #7282:
Focus: the white door frame behind Drew


Here's with the settings used by MysteryX:
KNLMeansCL(D=2, A=1, h=3, device_type="GPU", info=true)
Focus: the white door frame behind Drew


Looks it denoises a lot of the main flat areas, but any edges are nearly the same.
When you scan forward, you can see this jerkiness it produces to due to unfiltered edges.
Some frames, the edges are cleaned out right.
And a large portion of (proceeding) frames, the noise varies, giving it a jerky look when played back.
At those setings.

Here's same settings, an earlier frame where the door frame is entirely denoised and clean edges.
Frame #7275:


Frame #7276 is pretty clean too.
From there, it starts to degrade back to a noisy edge.

BUT
I changed parameters and found this:

Frame #7313
KNLMeansCL(D=3, A=0, h=3, device_type="GPU", info=true)

Jerky-ish lines.

Are those the kind of jerky lines you got?
I couldn't get those lines on the sample video with previous settings.
I haven't checked with new settings to see if jerky lines appear.

[feisty2]

Originally Posted by Sparktank

Win7 (x64) SP1
GTX 750 ti
GeForce 355.82 (newest; although I don't think much changed as far as video processing goes, mostly just new games)

KNLMeansCL v0.6.1

SetMemoryMax(512)
LoadPlugin("C:\AVS\dgdecnv2049\DGDecodeNV.dll")
DGSource("E:\Demux\Scream\Scream.dgi", crop_b=140, crop_t=132)
#KNLMeansCL(D=2, A=1, h=3, device_type="GPU", info=true)

"jerky lines in the background"

I don't see "jerky lines" in the sample video.
I grabbed a demux of the poorly mastered BD for Scream, since it's noisy and messy.
(Canadian BD Region A, identical to USA BD)

(all images are "large thumbnail", click to follow to original size (1920x816)
Here's original Frame #7282:
Focus: the white door frame behind Drew


Here's with the settings used by MysteryX:
KNLMeansCL(D=2, A=1, h=3, device_type="GPU", info=true)
Focus: the white door frame behind Drew


Looks it denoises a lot of the main flat areas, but any edges are nearly the same.
When you scan forward, you can see this jerkiness it produces to due to unfiltered edges.
Some frames, the edges are cleaned out right.
And a large portion of (proceeding) frames, the noise varies, giving it a jerky look when played back.
At those setings.

Here's same settings, an earlier frame where the door frame is entirely denoised and clean edges.
Frame #7275:


Frame #7276 is pretty clean too.
From there, it starts to degrade back to a noisy edge.

BUT
I changed parameters and found this:

Frame #7313
KNLMeansCL(D=3, A=0, h=3, device_type="GPU", info=true)

Jerky-ish lines.

Are those the kind of jerky lines you got?
I couldn't get those lines on the sample video with previous settings.
I haven't checked with new settings to see if jerky lines appear.

NLMeans degrades to something like "Motion Flow" (pixel wise motion compensation) by setting A=0 (spatial processing disabled)
and the jerky lines are just common motion flow artifacts
solution: enable spatial processing, pick an A value greater than 0

[MysteryX]

I might as well post images of the video having bad results.

Original


KNLMeansCL(D=2, A=2, h=3, device_type="GPU")


fft3dfilter(sigma=3, bt=5, bw=48, bh=48, ow=24, oh=24, sharpen=0.15)

[Khanattila]

Originally Posted by MysteryX

This version gives me this error:
KNLMeansCL: AviSynthCreate Error (clBuildProgram!)

Originally Posted by detmek

Same here. I use it with StaxRip x64 and Avisynth+. Same error with 0.6.0. Builds up to 0.5.9 work just fine.

Please report KNLMeansCL.txt.

Each driver has its own OpenCL compiler. I can not test all possible cases.

[Khanattila]

Originally Posted by feisty2

NLMeans degrades to something like "Motion Flow" (pixel wise motion compensation) by setting A=0 (spatial processing disabled)
and the jerky lines are just common motion flow artifacts
solution: enable spatial processing, pick an A value greater than 0

[Khanattila]

Originally Posted by MysteryX

I'm using AviSynth 2.6

Also, KNLMeans is giving me better results than FF3DFilter on most videos, but why is it giving me such bad output on this video? The lines in the background end up being very jerky (I know, the source video is bad quality), but FF3DFilter is doing a MUCH better job in this particular case. In most other videos with similarly bad quality, however, KNLMeans gives a better output.

Here's the video
https://mega.nz/#!CNICBS5S!56wGjk8gt...k4ms8mPXFr0nkY

KNLMeansCL(D=2, A=1, h=3, device_type="GPU")

Originally Posted by MysteryX

I might as well post images of the video having bad results.

Original


KNLMeansCL(D=2, A=2, h=3, device_type="GPU")


fft3dfilter(sigma=3, bt=5, bw=48, bh=48, ow=24, oh=24, sharpen=0.15)

KNLMeansCL works with similar patches. If similar patches are noise, output will have more noise.

[YAFU]

Hello.
With this script by feisty2:
http://forum.doom9.org/showpost.php?...&postcount=234

vsedit shows me the following message:

Failed to evaluate the script:
Python exception: knlm.KNLMeansCL: VapourSynthCreate error (clBuildProgram)!
Traceback (most recent call last):
  File "vapoursynth.pyx", line 1469, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:23703)
  File "/media/TEMPORAL/scrypt.vpy", line 60, in <module>
    spt = core.std.CropRel (core.knlm.KNLMeansCL(padding(clp,24,24,24,24), 0, 24, 4, h=3.2),24,24,24,24)
  File "vapoursynth.pyx", line 1368, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:22272)
vapoursynth.Error: knlm.KNLMeansCL: VapourSynthCreate error (clBuildProgram)!

I use Kubuntu 64 bits. I installed KNLMeansCL from github. I needed to install the "opencl-headres" package to compile in Kubuntu.
My graphics card is a GTX 960, using NVIDIA 355.11 driver. "nvidia_uvm" seems loaded into the kernel. nVidia OpenCL in Blender 3D seems to be working properly.

What could be causing the problem?

EDIT:
I have found that a file "KNLMeansCL.txt" is generated in the same folder as the script:
http://pastebin.com/4Cvep6w8

Another question. I have two devices that can use OpenCL, Nvidia and Intel. How to indicate in the script which device KNLMeansCL should use?

[Khanattila]

Originally Posted by YAFU

Hello.
With this script by feisty2:
http://forum.doom9.org/showpost.php?...&postcount=234

vsedit shows me the following message:

Failed to evaluate the script:
Python exception: knlm.KNLMeansCL: VapourSynthCreate error (clBuildProgram)!
Traceback (most recent call last):
  File "vapoursynth.pyx", line 1469, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:23703)
  File "/media/TEMPORAL/scrypt.vpy", line 60, in <module>
    spt = core.std.CropRel (core.knlm.KNLMeansCL(padding(clp,24,24,24,24), 0, 24, 4, h=3.2),24,24,24,24)
  File "vapoursynth.pyx", line 1368, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:22272)
vapoursynth.Error: knlm.KNLMeansCL: VapourSynthCreate error (clBuildProgram)!

I use Kubuntu 64 bits. I installed KNLMeansCL from github. I needed to install the "opencl-headres" package to compile in Kubuntu.
My graphics card is a GTX 960, using NVIDIA 355.11 driver. "nvidia_uvm" seems loaded into the kernel. nVidia OpenCL in Blender 3D seems to be working properly.

What could be causing the problem?

EDIT:
I have found that a file "KNLMeansCL.txt" is generated in the same folder as the script:
http://pastebin.com/4Cvep6w8

Another question. I have two devices that can use OpenCL, Nvidia and Intel. How to indicate in the script which device KNLMeansCL should use?

The plugin use the first device available of type device_type. You can check it with info = true.
Or you can manually set the default opencl device in your system environment.

EDIT. v0.6.2 is required.
Tomorrow I correct everything. Others have had problems.

[YAFU]

Ok, I'll be tuned waiting to v0.6.2
Thank you.

[Khanattila]

https://github.com/Khanattila/KNLMea...ses/tag/v0.6.2

This release should fix all problems.

[YAFU]

Hi.
I updated from git (git pull), compiled and installed (Kubuntu Linux 64 bits, nvidia 355.11 driver)

Still having similar error in vsedit, and this is the log:
http://pastebin.com/eiWtS3ws

I uninstalled intel OpenCL driver, so nvidia is the only OpenCL device.

[sl1pkn07]

i think is problem by vsedit (have a similar problem)

try:

vspipe -y script.vpy -i -

or

vspipe -y script.vpy - | mpv -

[YAFU]

Hey, with these commands my graphics card started making small weird treble sounds (they were no sounds of the fan). I stopped with Ctrl + C. What does that mean? Are there risks to break my card?

[sl1pkn07]

should not. i think

http://wstaw.org/m/2015/09/04/Screen...904_204833.png


maybe is a Coil Whine (?)