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

[Asmodian]

Originally Posted by Khanattila

>>>> NLMeans2_v0.3.0.zip <<<<

ChangeLog

• v0.3.0 (2014-11-16)
  * Works with Y8.
  * Prevent possible memory leak.
  * More selective resource load.

Hate these weekends without football!

It turns out we like them.

[Khanattila]

Edit.

[yup]

Khanattila!

for update.
I test Your plugin on different PC.
It is work fine for Windows XP 32 with NVIDIA GeForce 8800 GTS 512 and Windows 7 64 with Intel HD, but have problem with Windows 7 64 with GTX 560
Script

AVISource("chapter13.avi")
AssumeTFF()
ConvertToYV12(interlaced=true)
SeparateFields()
NLMeansCL2(device_type="GPU")
Weave()

I get error

Avisynth open failure:
NLMeansCL2: Houston, we've had a problem!
 [clCreateContext (CL_INVALID_DEVICE)]
(C:\Video\Source\stenyaev\tesnlmcl.avs, line 5)

Data for GPU

OpenCL 1.1 CUDA 6.5.12 FULL_PROFILE
1: GeForce GTX 560

If change device type to CPU, I get error

Avisynth open failure:
NLMeansCL2: Houston, we've had a problem!
 [create_image2d (CL_GENERIC_ERROR)]
(C:\Video\Source\stenyaev\tesnlmcl.avs, line 5)

Malcolm version work without problem, also work cl version nnedi3 written by SEt. MSVC 2013 installed.
Also when I try on other computer with avisynth+ and open avs in Virtualdub I get error about insert disk for installation, after cancel avs opened. When I replace to Avisynth 2.6 MT all became fine.
yup.

[Khanattila]

Ok, let me explain.
This plugin use the default OpenCL context of your system because I have not yet implemented a system scan.
If for example the system uses NVIDIA CUDA as default OpenCL context is not possible to set device_type = "CPU".
Because NVIDIA CUDA do not support any CPU.

It is possible that the system default is wrong.

[yup]

Khanattila!
I am also try device_type="GPU" and get error.
May be try change Nvidia driver?
And why work previous Malcolm version?
Tomorrow I try some recreation my system and report.
yup.

[Khanattila]

Originally Posted by yup

Khanattila!
I am also try device_type="GPU" and get error.
May be try change Nvidia driver?
And why work previous Malcolm version?
Tomorrow I try some recreation my system and report.
yup.

Please, use GPU Caps Viewer
(validation link)

[yup]

Khanattila!
Report from GPU Caps Viewer

===================================[ OpenCL Capabilities ]
- Num OpenCL platforms: 2
- CL_PLATFORM_NAME: Intel(R) OpenCL
- CL_PLATFORM_VENDOR: Intel(R) Corporation
- CL_PLATFORM_VERSION: OpenCL 1.1
- CL_PLATFORM_PROFILE: FULL_PROFILE
- Num devices: 1

- CL_DEVICE_NAME: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
- CL_DEVICE_VENDOR: Intel(R) Corporation
- CL_DRIVER_VERSION: 1.1
- CL_DEVICE_PROFILE: FULL_PROFILE
- CL_DEVICE_VERSION: OpenCL 1.1 (Build 31360.31441)
- CL_DEVICE_TYPE: CPU
- CL_DEVICE_VENDOR_ID: 0x8086
- CL_DEVICE_MAX_COMPUTE_UNITS: 8
- CL_DEVICE_MAX_CLOCK_FREQUENCY: 3400MHz
- CL_DEVICE_ADDRESS_BITS: 32
- CL_DEVICE_MAX_MEM_ALLOC_SIZE: 524256KB
- CL_DEVICE_GLOBAL_MEM_SIZE: 2047MB
- CL_DEVICE_MAX_PARAMETER_SIZE: 3840
- CL_DEVICE_GLOBAL_MEM_CACHELINE_SIZE: 64 Bytes
- CL_DEVICE_GLOBAL_MEM_CACHE_SIZE: 256KB
- CL_DEVICE_ERROR_CORRECTION_SUPPORT: NO
- CL_DEVICE_LOCAL_MEM_TYPE: Global
- CL_DEVICE_LOCAL_MEM_SIZE: 32KB
- CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 128KB
- CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3
- CL_DEVICE_MAX_WORK_ITEM_SIZES: [1024 ; 1024 ; 1024]
- CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
- CL_EXEC_NATIVE_KERNEL: 14404036
- CL_DEVICE_IMAGE_SUPPORT: YES
- CL_DEVICE_MAX_READ_IMAGE_ARGS: 480
- CL_DEVICE_MAX_WRITE_IMAGE_ARGS: 480
- CL_DEVICE_IMAGE2D_MAX_WIDTH: 8192
- CL_DEVICE_IMAGE2D_MAX_HEIGHT: 8192
- CL_DEVICE_IMAGE3D_MAX_WIDTH: 2048
- CL_DEVICE_IMAGE3D_MAX_HEIGHT: 2048
- CL_DEVICE_IMAGE3D_MAX_DEPTH: 2048
- CL_DEVICE_MAX_SAMPLERS: 480
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_CHAR: 16
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_SHORT: 8
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_INT: 4
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_LONG: 2
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_FLOAT: 4
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_DOUBLE: 2
- CL_DEVICE_EXTENSIONS: 11
- Extensions:
- cl_khr_fp64
- cl_khr_icd
- cl_khr_global_int32_base_atomics
- cl_khr_global_int32_extended_atomics
- cl_khr_local_int32_base_atomics
- cl_khr_local_int32_extended_atomics
- cl_khr_byte_addressable_store
- cl_intel_printf
- cl_ext_device_fission
- cl_intel_exec_by_local_thread
- cl_khr_gl_sharing
- CL_PLATFORM_NAME: NVIDIA CUDA
- CL_PLATFORM_VENDOR: NVIDIA Corporation
- CL_PLATFORM_VERSION: OpenCL 1.1 CUDA 6.5.12
- CL_PLATFORM_PROFILE: FULL_PROFILE
- Num devices: 1

- CL_DEVICE_NAME: GeForce GTX 560
- CL_DEVICE_VENDOR: NVIDIA Corporation
- CL_DRIVER_VERSION: 340.52
- CL_DEVICE_PROFILE: FULL_PROFILE
- CL_DEVICE_VERSION: OpenCL 1.1 CUDA
- CL_DEVICE_TYPE: GPU
- CL_DEVICE_VENDOR_ID: 0x10DE
- CL_DEVICE_MAX_COMPUTE_UNITS: 7
- CL_DEVICE_MAX_CLOCK_FREQUENCY: 1620MHz
- CL_NV_DEVICE_COMPUTE_CAPABILITY_MAJOR: 2
- CL_NV_DEVICE_COMPUTE_CAPABILITY_MINOR: 1
- CL_NV_DEVICE_REGISTERS_PER_BLOCK: 32768
- CL_NV_DEVICE_WARP_SIZE: 32
- CL_NV_DEVICE_GPU_OVERLAP: 1
- CL_NV_DEVICE_KERNEL_EXEC_TIMEOUT: 1
- CL_NV_DEVICE_INTEGRATED_MEMORY: 0
- CL_DEVICE_ADDRESS_BITS: 32
- CL_DEVICE_MAX_MEM_ALLOC_SIZE: 262144KB
- CL_DEVICE_GLOBAL_MEM_SIZE: 1024MB
- CL_DEVICE_MAX_PARAMETER_SIZE: 4352
- CL_DEVICE_GLOBAL_MEM_CACHELINE_SIZE: 128 Bytes
- CL_DEVICE_GLOBAL_MEM_CACHE_SIZE: 112KB
- CL_DEVICE_ERROR_CORRECTION_SUPPORT: NO
- CL_DEVICE_LOCAL_MEM_TYPE: Local (scratchpad)
- CL_DEVICE_LOCAL_MEM_SIZE: 47KB
- CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 64KB
- CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3
- CL_DEVICE_MAX_WORK_ITEM_SIZES: [1024 ; 1024 ; 64]
- CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
- CL_EXEC_NATIVE_KERNEL: 14404032
- CL_DEVICE_IMAGE_SUPPORT: YES
- CL_DEVICE_MAX_READ_IMAGE_ARGS: 128
- CL_DEVICE_MAX_WRITE_IMAGE_ARGS: 8
- CL_DEVICE_IMAGE2D_MAX_WIDTH: 32768
- CL_DEVICE_IMAGE2D_MAX_HEIGHT: 32768
- CL_DEVICE_IMAGE3D_MAX_WIDTH: 2048
- CL_DEVICE_IMAGE3D_MAX_HEIGHT: 2048
- CL_DEVICE_IMAGE3D_MAX_DEPTH: 2048
- CL_DEVICE_MAX_SAMPLERS: 16
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_CHAR: 1
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_SHORT: 1
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_INT: 1
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_LONG: 1
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_FLOAT: 1
- CL_DEVICE_PREFERRED_VECTOR_WIDTH_DOUBLE: 1
- CL_DEVICE_EXTENSIONS: 15
- Extensions:
- cl_khr_byte_addressable_store
- cl_khr_icd
- cl_khr_gl_sharing
- cl_nv_d3d9_sharing
- cl_nv_d3d10_sharing
- cl_khr_d3d10_sharing
- cl_nv_d3d11_sharing
- cl_nv_compiler_options
- cl_nv_device_attribute_query
- cl_nv_pragma_unroll
- cl_khr_global_int32_base_atomics
- cl_khr_global_int32_extended_atomics
- cl_khr_local_int32_base_atomics
- cl_khr_local_int32_extended_atomics
- cl_khr_fp64

I have last driver availible from Nvidia.
yup.

[Khanattila]

That's what I tried to explain.

- Num OpenCL platforms: 2
- CL_PLATFORM_NAME: Intel(R) OpenCL
- CL_PLATFORM_VENDOR: Intel(R) Corporation
- CL_PLATFORM_VERSION: OpenCL 1.1
- CL_PLATFORM_PROFILE: FULL_PROFILE

You have two OpenCL platforms, and default is Intel.
Because NLMeansCL2 is still in development, it use only the default context.
If you remove the intel OpenCL driver it should work.

[yup]

Khanattila!
I remove Intel OpenCL SDK and now all work.
yup.

[Khanattila]

Originally Posted by yup

Khanattila!
I remove Intel OpenCL SDK and now all work.
yup.

Glad you managed to solve it.

[HOB]

Hello
I wonder if this plugin will work in MeGUI? I was able to get NLMeansCL to work in MeGUI the minor problems I encountered I was able to overcome. I downloaded this plugin and copied it to the standard MeGUI folder for this kind of plugin but MeGUI doesn't seem to recognize it properly...OR...perhaps I didn't install it correctly? Will it work or shall I just continue to check in here to see if you've made it compatible with MeGUI?
Thanks

[Reel.Deel]

Originally Posted by HOB

I downloaded this plugin and copied it to the standard MeGUI folder for this kind of plugin but MeGUI doesn't seem to recognize it properly...

Do you have the appropriate requirements?

AviSynth 2.6 Alpha 5
Visual C++ Redistributable Package for Visual Studio 2013 (x86)

I don't use MeGUI so I can't check.

[StainlessS]

RD, can I ask then, what do you use for h264, just curious.

[Reel.Deel]

x264.exe (I use tMod), I sometimes load the .avs directly, or use Avs2YUV to pipe to x264 (mainly for 10-bit video). Anyways this it OT so I'll stop.

----

@Khanattila
When this filter becomes stable do you mind if I add to the AviSynth wiki?

[HOB]

Hello Reel.Deel
Yes I do have AviSynth 2.6 Alpha 5 installed.

[Reel.Deel]

@HOB
How about the 2013 runtime? Also, any error message?

[HOB]

Reel.Deel
Yes and here is the message:

[Khanattila]

Originally Posted by HOB

Hello
I wonder if this plugin will work in MeGUI? I was able to get NLMeansCL to work in MeGUI the minor problems I encountered I was able to overcome. I downloaded this plugin and copied it to the standard MeGUI folder for this kind of plugin but MeGUI doesn't seem to recognize it properly...OR...perhaps I didn't install it correctly? Will it work or shall I just continue to check in here to see if you've made it compatible with MeGUI?
Thanks

A safe way is to install AviSynth and do not use the included AviSynth.
Just copy the plugin in "C:\Program Files (x86)\AviSynth 2.5\plugins" (example).
MeGui can call all of them.

[HOB]

Khanattila
Sorry to be a dunce but I'm not having any luck and I don't want to waste anymore or your time, I'll just tune into this site every once in a while to see if any one has gotten this plugin working with MeGUI and hope they post instructions on HOW EXACTLY they managed it.
Thanks

[Reel.Deel]

@HOB

error=0x7e? Hmm doesn't this error mean that a component is missing? Are you sure you have the 32-bit (x86) 2013 Redistributable Package?

Edit: try loading NLMeansCL2.dll with Dependency Walker to be sure that nothing is missing.