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

WolframRhodium

6th February 2017, 00:13

the Bisquare weighting function (wmode=2) does that "pruning" thing exactly, reject a pixel within the search window if the inter-patch correlation (weight) goes below certain threshold, windowed weighting function.

I realize I said stupid words before...thx

Khanattila

6th February 2017, 11:49

Hi Sir,

The filter ver 1.0 make my GPU (GTX 650Ti) crash with default filter setting :confused::confused:

I'm using avs+ r2397
Here's my script:

This type of error is different.
What system are you using?

tuanden0

7th February 2017, 04:58

This type of error is different.
What system are you using?

I'm using windows 7 x64, avs+ x86 and AvsPmod to edit avs script :confused:

my GPU crashed everytime I try to preview my avs script and if I encode without preview avs, my PC crashed too :confused::confused:

burfadel

7th February 2017, 13:19

For me, wmode=3 causes the encode to typically crash at some point. wmode=2 seems stable, and wmode=0 (default?) has worked flawlessly. Just thought I'd try it out but the crashes put an end to doing a full encode :S!

Khanattila

7th February 2017, 19:05

For me, wmode=3 causes the encode to typically crash at some point. wmode=2 seems stable, and wmode=0 (default?) has worked flawlessly. Just thought I'd try it out but the crashes put an end to doing a full encode :S!

Thanks for your report, I will check if there is any problem.

Khanattila

7th February 2017, 19:08

I realize I said stupid words before...thx

However, what you say it is interesting.
I know if I do a previous estimate of the noise, the filter give better results.
But of course, it is slower.

Khanattila

7th February 2017, 19:09

I'm using windows 7 x64, avs+ x86 and AvsPmod to edit avs script :confused:

my GPU crashed everytime I try to preview my avs script and if I encode without preview avs, my PC crashed too :confused::confused:

I will check this.

burfadel

7th February 2017, 22:33

Thanks for your report, I will check if there is any problem.

wmode=2 is stable, has been running encodes since I made the post, so it seems only wmode=3 is problematic (at least for me).

burfadel

8th February 2017, 13:03

My mistake :) wmode=2 does also seem buggy, just not as noticeable as wmode=3.

Khanattila

9th February 2017, 19:38

https://github.com/Khanattila/KNLMeansCL/releases/tag/v1.0.1

KNLMeansCL v1.0.1
* Fixed wrong output with 'wmode' different to 0 in some circumstances.
* Fixed second clip 'rclip' in VapourSynth.

KNLMeansCL v1.0.0
* Improved performance with CPU.
* Improved performance with AMD GCN Architecture.
* Reduced CPU overhead in some system.
* Reduced memory usage in some system.
* Advanced OpenCL parameters for fine tuning.
* Replaced 'cmode' with 'channels' and added the options to only process the chroma.
* Two new modified bisquare weighting functions.
* Increased the maximum 's' value to 8.
* Updated to VapourSynth R36.
* Removed Cauchy weighting function.
* Fixed second clip 'rclip' in some circumstances.

If this time is rock solid I can move on.

hydra3333

10th February 2017, 00:36

Thank you. The 1.0.1 zip contains only one dll ... any chance of one for x32 and one for x64 ? :)

Khanattila

10th February 2017, 00:55

Thank you. The 1.0.1 zip contains only one dll ... any chance of one for x32 and one for x64 ? :)

:eek:, fixed

tuanden0

11th February 2017, 04:27

No crash anymore, :thanks: Khanattila

burfadel

11th February 2017, 05:09

No crash with wmode=3 here now either! Thanks :)

MysteryX

14th February 2017, 17:08

Khanattila

14th February 2017, 19:41

MysteryX

14th February 2017, 23:03

Khanattila

14th February 2017, 23:10

Good for you

feisty2

15th February 2017, 19:38

I found the results(with the same parameters) between v0.7.7 and v1.0.1 are noticeably different, v1.0.1 left more residual noise than v0.7.7
like something algorithmic has changed?
I prefer the result of v0.7.7

MysteryX

16th February 2017, 00:52

I confirm a notable difference between versions.

v6.11
https://s20.postimg.org/cjr1i30gp/Knl_Means_Old.png (https://postimg.org/image/cjr1i30gp/)

v1.0.1
https://s20.postimg.org/3ng9e59uh/Knl_Means_New.png (https://postimg.org/image/3ng9e59uh/)

feisty2

16th February 2017, 06:58

to have similar results, "h" in v1.0.1 should be around 1.6 ~ 1.8 x "h" in v0.7.7
@Khanattila
is there an explanation for what's happening here?
did you switch from SSE to SAD?

Khanattila

16th February 2017, 11:07

Mathematics is the same, there will be a bug somewhere.

feisty2

16th February 2017, 11:29

@Khanattila
That doesn't sound good...
Are you planning on fixing it?

Khanattila

16th February 2017, 11:38

@Khanattila
That doesn't sound good...
Are you planning on fixing it?

I already found the problem...
You can consider it a side effect of the new channels mode.
The result is correct, I might add an internal multiplier to maintain compatibility with the older versions.

PS. It is more correct the new version instead of the old.

feisty2

16th February 2017, 12:33

I did my tests on GRAYS clips...
So that channel thing, will affect GRAY stuff as well?

Khanattila

16th February 2017, 12:36

I did my tests on GRAYS clips...
So that channel thing, will affect GRAY stuff as well?

All modes are affected.
As a temporary fix using ~1,732 (square root of 3) as a multiplier for h.

burfadel

16th February 2017, 14:59

All modes are affected.
As a temporary fix using ~1,732 (square root of 3) as a multiplier for h.

Just be aware that a comma is also a thousand separator in half the world. Basically, to many people out there, you said to set h to one thousand seven hundred thirty two (1732) :).

Yes it's Wikipedia, but it's good enough:
https://en.wikipedia.org/w/index.php?title=Decimal_mark

Basically it's the exact opposite, where you use commas' as a decimal separator as in your usage, a decimal is used, and where we would use a comma, you use a decimal as a thousands separator.

Makes it confusing when there are multiple different systems (more than just these) around the world. The correct form in Australia for 1,732 is 1 732, although a comma is typically used. Not to confuse things with the comma at the end there for a sentence break! Many people would also write 1 732 as 1,732, but if the number were much larger as in 92,345,764 they would use spaces. The spaces are used as part of the SI system I believe to avoid confusion between the various systems used around the world.

Khanattila

16th February 2017, 16:32

Just be aware that a comma is also a thousand separator in half the world. Basically, to many people out there, you said to set h to one thousand seven hundred thirty two (1732) :).

Yes it's Wikipedia, but it's good enough:
https://en.wikipedia.org/w/index.php?title=Decimal_mark

Basically it's the exact opposite, where you use commas' as a decimal separator as in your usage, a decimal is used, and where we would use a comma, you use a decimal as a thousands separator.

Makes it confusing when there are multiple different systems (more than just these) around the world. The correct form in Australia for 1,732 is 1 732, although a comma is typically used. Not to confuse things with the comma at the end there for a sentence break! Many people would also write 1 732 as 1,732, but if the number were much larger as in 92,345,764 they would use spaces. The spaces are used as part of the SI system I believe to avoid confusion between the various systems used around the world.

I thank you, but really, I know the difference.
I live in the limbo in which I program using '.' and in the lives of everyday I use ','. :p

MysteryX

16th February 2017, 16:55

I thank you, but really, I know the difference.
I live in the limbo in which I program using '.' and in the lives of everyday I use ','. :p
Modern programming languages have no issue with that (as long as you set the right parameters for formatting) but this used to be a major source of frustration with old programming languages. A program would run 100% fine, then on another computer, it would totally crash on every comma.

KingLir

21st February 2017, 10:52

I am getting the following error when running on macOS with latest versions (vapoursynth R36 and KNLMeansCL built from master - commit 08755c5). Anyone got an idea how to fix ?

Script evaluation failed:
Python exception: knlm.KNLMeansCL: build programm error!
Please report Log-KNLMeansCL.txt.
Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1712, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:34991)
File "VIVTC_with_TComb_script.vpy", line 11, in <module>
clip = core.knlm.KNLMeansCL(clip=clip)
File "src/cython/vapoursynth.pyx", line 1604, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:33131)
vapoursynth.Error: knlm.KNLMeansCL: build programm error!

script:

import vapoursynth as vs
core = vs.get_core()
core.max_cache_size = 12000

clip = core.ffms2.Source(source=filename)
clip = core.knlm.KNLMeansCL(clip=clip)

Khanattila

21st February 2017, 10:59

I am getting the following error when running on macOS. Anyone got an idea how to fix ?

Script evaluation failed:
Python exception: knlm.KNLMeansCL: build programm error!
Please report Log-KNLMeansCL.txt.
Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1712, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:34991)
File "VIVTC_with_TComb_script.vpy", line 11, in <module>
clip = core.knlm.KNLMeansCL(clip=clip)
File "src/cython/vapoursynth.pyx", line 1604, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:33131)
vapoursynth.Error: knlm.KNLMeansCL: build programm error!

script:
clip = core.knlm.KNLMeansCL(clip=clip)

> Please report Log-KNLMeansCL.txt

KingLir

21st February 2017, 11:27

> Please report Log-KNLMeansCL.txt

Sure, but where can I find it on macOS ? I searched and haven't found it.

Khanattila

21st February 2017, 16:58

Sure, but where can I find it on macOS ? I searched and haven't found it.

It is in the script folder.

KingLir

21st February 2017, 19:32

It is in the script folder.

Thanks, sorry I missed it.
Here:

OpenCL Platform
------------------------------------------------------------
CL_PLATFORM_VENDOR: Apple
CL_PLATFORM_NAME: Apple
CL_PLATFORM_VERSION: OpenCL 1.2 (Jan 4 2017 22:35:59)
CL_PLATFORM_PROFILE: FULL_PROFILE

OpenCL Device
------------------------------------------------------------
CL_DEVICE_VENDOR: AMD
CL_DEVICE_NAME: AMD Radeon R9 M395X Compute Engine
CL_DRIVER_VERSION: 1.2 (Jan 10 2017 22:25:08)
CL_DEVICE_VERSION: OpenCL 1.2
CL_DEVICE_PROFILE: FULL_PROFILE
CL_DEVICE_IMAGE_SUPPORT: 1
CL_DEVICE_IMAGE2D_MAX_WIDTH: 16384
CL_DEVICE_IMAGE2D_MAX_HEIGHT: 16384
CL_DEVICE_IMAGE_MAX_ARRAY_SIZE: 2048

Program Build
------------------------------------------------------------
CL_PROGRAM_BUILD_OPTIONS:
CL_PROGRAM_BUILD_LOG:

RETURN: 0

KingLir

22nd February 2017, 14:40

Any ideas ?

Khanattila

24th February 2017, 18:25

Any ideas ?

v1.0.2, definitely

Khanattila

24th February 2017, 19:01

@ KingLir
https://github.com/Khanattila/KNLMeansCL/archive/master.zip
Can you test this version and report log?

KingLir

26th February 2017, 17:22

@ KingLir
https://github.com/Khanattila/KNLMeansCL/archive/master.zip
Can you test this version and report log?

Thanks and sorry for the late reply.

Here is the new output:

Script evaluation failed:
Python exception: knlm.KNLMeansCL: build programm error!
Please report Log-KNLMeansCL.txt.
Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1712, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:34991)
File "VIVTC_with_TComb_script.vpy", line 16, in <module>
clip = core.knlm.KNLMeansCL(clip=clip)
File "src/cython/vapoursynth.pyx", line 1604, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:33131)
vapoursynth.Error: knlm.KNLMeansCL: build programm error!

And the new log:

OpenCL Platform
------------------------------------------------------------
CL_PLATFORM_VENDOR: Apple
CL_PLATFORM_NAME: Apple
CL_PLATFORM_VERSION: OpenCL 1.2 (Jan 4 2017 22:35:59)
CL_PLATFORM_PROFILE: FULL_PROFILE

OpenCL Device
------------------------------------------------------------
CL_DEVICE_VENDOR: AMD
CL_DEVICE_NAME: AMD Radeon R9 M395X Compute Engine
CL_DRIVER_VERSION: 1.2 (Jan 10 2017 22:25:08)
CL_DEVICE_VERSION: OpenCL 1.2
CL_DEVICE_PROFILE: FULL_PROFILE
CL_DEVICE_IMAGE_SUPPORT: 1
CL_DEVICE_IMAGE2D_MAX_WIDTH: 16384
CL_DEVICE_IMAGE2D_MAX_HEIGHT: 16384
CL_DEVICE_IMAGE_MAX_ARRAY_SIZE: 2048

Program Build
------------------------------------------------------------
CL_PROGRAM_BUILD_ERROR: CL_INVALID_BUILD_OPTIONS
CL_PROGRAM_BUILD_OPTIONS:
CL_PROGRAM_BUILD_LOG:

RETURN: 0

Khanattila

28th February 2017, 17:07

Thanks and sorry for the late reply.

Here is the new output:

Script evaluation failed:
Python exception: knlm.KNLMeansCL: build programm error!
Please report Log-KNLMeansCL.txt.
Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1712, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:34991)
File "VIVTC_with_TComb_script.vpy", line 16, in <module>
clip = core.knlm.KNLMeansCL(clip=clip)
File "src/cython/vapoursynth.pyx", line 1604, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:33131)
vapoursynth.Error: knlm.KNLMeansCL: build programm error!

And the new log:

OpenCL Platform
------------------------------------------------------------
CL_PLATFORM_VENDOR: Apple
CL_PLATFORM_NAME: Apple
CL_PLATFORM_VERSION: OpenCL 1.2 (Jan 4 2017 22:35:59)
CL_PLATFORM_PROFILE: FULL_PROFILE

OpenCL Device
------------------------------------------------------------
CL_DEVICE_VENDOR: AMD
CL_DEVICE_NAME: AMD Radeon R9 M395X Compute Engine
CL_DRIVER_VERSION: 1.2 (Jan 10 2017 22:25:08)
CL_DEVICE_VERSION: OpenCL 1.2
CL_DEVICE_PROFILE: FULL_PROFILE
CL_DEVICE_IMAGE_SUPPORT: 1
CL_DEVICE_IMAGE2D_MAX_WIDTH: 16384
CL_DEVICE_IMAGE2D_MAX_HEIGHT: 16384
CL_DEVICE_IMAGE_MAX_ARRAY_SIZE: 2048

Program Build
------------------------------------------------------------
CL_PROGRAM_BUILD_ERROR: CL_INVALID_BUILD_OPTIONS
CL_PROGRAM_BUILD_OPTIONS:
CL_PROGRAM_BUILD_LOG:

RETURN: 0
Apple... why not follow the standard?

Khanattila

28th February 2017, 18:04

@ KingLir
https://github.com/Khanattila/KNLMeansCL/archive/master.zip
now, it should work for you.

KingLir

28th February 2017, 19:59

@ KingLir
now, it should work for you.

Thanks! Now I am getting:

Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1712, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:34991)
File "VIVTC_with_TComb_script.vpy", line 16, in <module>
clip = core.knlm.KNLMeansCL(clip=clip)
File "src/cython/vapoursynth.pyx", line 1604, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:33131)
vapoursynth.Error: knlm.KNLMeansCL: build programm error!

And the new log:

OpenCL Platform
------------------------------------------------------------
CL_PLATFORM_VENDOR: Apple
CL_PLATFORM_NAME: Apple
CL_PLATFORM_VERSION: OpenCL 1.2 (Jan 4 2017 22:35:59)
CL_PLATFORM_PROFILE: FULL_PROFILE

OpenCL Device
------------------------------------------------------------
CL_DEVICE_VENDOR: AMD
CL_DEVICE_NAME: AMD Radeon R9 M395X Compute Engine
CL_DRIVER_VERSION: 1.2 (Jan 10 2017 22:25:08)
CL_DEVICE_VERSION: OpenCL 1.2
CL_DEVICE_PROFILE: FULL_PROFILE
CL_DEVICE_IMAGE_SUPPORT: 1
CL_DEVICE_IMAGE2D_MAX_WIDTH: 16384
CL_DEVICE_IMAGE2D_MAX_HEIGHT: 16384
CL_DEVICE_IMAGE_MAX_ARRAY_SIZE: 2048

Program Build
------------------------------------------------------------
CL_PROGRAM_BUILD_ERROR: CL_BUILD_PROGRAM_FAILURE
CL_PROGRAM_BUILD_OPTIONS: -cl-denorms-are-zero
-cl-fast-relaxed-math
-Werror
-D NLM_CLIP_TYPE_UNORM
-D NLM_CLIP_REF_LUMA
-D NLM_WMODE_WELSCH
-D VI_DIM_X=720
-D VI_DIM_Y=480
-D HRZ_RESULT=1
-D VRT_RESULT=1
-D HRZ_BLOCK_X=32
-D HRZ_BLOCK_Y=8
-D VRT_BLOCK_X=32
-D VRT_BLOCK_Y=8
-D NLM_D=1
-D NLM_S=4
-D NLM_H=1.200000f
-D NLM_WREF=1.000000f
CL_PROGRAM_BUILD_LOG:
<program source>:227:9: error: unused variable 'p'
int4 p = (int4) (x, y, t, 0);
^
<program source>:281:9: error: unused variable 's'
int2 s = (int2) (x, y);
^

RETURN: 0

Khanattila

28th February 2017, 20:50

Thanks for your report.
Still a few small changes and it should work.

KingLir

1st March 2017, 20:16

Thanks for your report.
Still a few small changes and it should work.

Thanks, can't wait :)
Is it something specific with my GPU ?

Khanattila

2nd March 2017, 17:43

Thanks, can't wait :)
Is it something specific with my GPU ?

No really, your GPU has nothing to do about it.

https://github.com/Khanattila/KNLMeansCL/releases/tag/v1.0.2

KNLMeansCL v1.0.2
* Tuned 'h' strength for backward compatibility.
* Fixed VapourSynth OSX version.

KNLMeansCL v1.0.1
* Fixed wrong output with 'wmode' different to 0 in some circumstances.
* Fixed second clip 'rclip' in VapourSynth.

KNLMeansCL v1.0.0
* Improved performance with CPU.
* Improved performance with AMD GCN Architecture.
* Reduced CPU overhead in some system.
* Reduced memory usage in some system.
* Advanced OpenCL parameters for fine tuning.
* Replaced 'cmode' with 'channels' and added the options to only process the chroma.
* Two new modified bisquare weighting functions.
* Increased the maximum 's' value to 8.
* Updated to VapourSynth R36.
* Removed Cauchy weighting function.
* Fixed second clip 'rclip' in some circumstances.

http://www.svethardware.cz/benchmarky-1700x-a-specialni-chladice-pro-95w-ryzen/43920/img/body-18.41DA.jpg

KingLir

2nd March 2017, 18:21

KNLMeansCL v1.0.2
* Tuned 'h' strength for backward compatibility.
* Fixed VapourSynth OSX version.

Thanks! It runs now, but the output is plagued with strange flickering and artifacts.

Before:
https://mega.nz/#!ggxF0bxA!IksjCkXKATd1VOS3ps4NrgV91p1k6YdQIRYcyvIyowY

After:
https://mega.nz/#!00JVgbDJ!J0wOYWTOBbtt3wMuTXQ3Hl0O-7wFh3wAqkZqvuUuRcA

Khanattila

2nd March 2017, 19:09

Thanks! It runs now, but the output is plagued with strange flickering and artifacts.

Before:
https://mega.nz/#!ggxF0bxA!IksjCkXKATd1VOS3ps4NrgV91p1k6YdQIRYcyvIyowY

After:
https://mega.nz/#!00JVgbDJ!J0wOYWTOBbtt3wMuTXQ3Hl0O-7wFh3wAqkZqvuUuRcA

http://www.parolacce.org/wp-content/uploads/2015/06/shutterstock_140158075-250x175.jpg

I do not have a Mac, so I'll make several attempts.

https://github.com/Khanattila/KNLMeansCL/archive/osx.zip

KingLir

2nd March 2017, 19:24

I do not have a Mac, so I'll make several attempts.

OK. New build doesn't run:

OpenCL Platform
------------------------------------------------------------
CL_PLATFORM_VENDOR: Apple
CL_PLATFORM_NAME: Apple
CL_PLATFORM_VERSION: OpenCL 1.2 (Jan 4 2017 22:35:59)
CL_PLATFORM_PROFILE: FULL_PROFILE

OpenCL Device
------------------------------------------------------------
CL_DEVICE_VENDOR: AMD
CL_DEVICE_NAME: AMD Radeon R9 M395X Compute Engine
CL_DRIVER_VERSION: 1.2 (Jan 10 2017 22:25:08)
CL_DEVICE_VERSION: OpenCL 1.2
CL_DEVICE_PROFILE: FULL_PROFILE
CL_DEVICE_IMAGE_SUPPORT: 1
CL_DEVICE_IMAGE2D_MAX_WIDTH: 16384
CL_DEVICE_IMAGE2D_MAX_HEIGHT: 16384
CL_DEVICE_IMAGE_MAX_ARRAY_SIZE: 2048

Program Build
------------------------------------------------------------
CL_PROGRAM_BUILD_ERROR: CL_BUILD_PROGRAM_FAILURE
CL_PROGRAM_BUILD_OPTIONS: -cl-single-precision-constant
-cl-denorms-are-zero
-cl-fast-relaxed-math
-Werror
-D NLM_CLIP_TYPE_UNORM
-D NLM_CLIP_REF_LUMA
-D NLM_WMODE_WELSCH
-D VI_DIM_X=720
-D VI_DIM_Y=480
-D HRZ_RESULT=1
-D VRT_RESULT=1
-D HRZ_BLOCK_X=32
-D HRZ_BLOCK_Y=8
-D VRT_BLOCK_X=32
-D VRT_BLOCK_Y=8
-D NLM_D=1
-D NLM_S=4
-D NLM_H=1.200000
-D NLM_WREF=1.000000
CL_PROGRAM_BUILD_LOG:
Error returned by cvms_element_build_from_source

RETURN: 0

Khanattila

2nd March 2017, 19:34

OK. New build doesn't run:

OpenCL Platform
------------------------------------------------------------
CL_PLATFORM_VENDOR: Apple
CL_PLATFORM_NAME: Apple
CL_PLATFORM_VERSION: OpenCL 1.2 (Jan 4 2017 22:35:59)
CL_PLATFORM_PROFILE: FULL_PROFILE

OpenCL Device
------------------------------------------------------------
CL_DEVICE_VENDOR: AMD
CL_DEVICE_NAME: AMD Radeon R9 M395X Compute Engine
CL_DRIVER_VERSION: 1.2 (Jan 10 2017 22:25:08)
CL_DEVICE_VERSION: OpenCL 1.2
CL_DEVICE_PROFILE: FULL_PROFILE
CL_DEVICE_IMAGE_SUPPORT: 1
CL_DEVICE_IMAGE2D_MAX_WIDTH: 16384
CL_DEVICE_IMAGE2D_MAX_HEIGHT: 16384
CL_DEVICE_IMAGE_MAX_ARRAY_SIZE: 2048

Program Build
------------------------------------------------------------
CL_PROGRAM_BUILD_ERROR: CL_BUILD_PROGRAM_FAILURE
CL_PROGRAM_BUILD_OPTIONS: -cl-single-precision-constant
-cl-denorms-are-zero
-cl-fast-relaxed-math
-Werror
-D NLM_CLIP_TYPE_UNORM
-D NLM_CLIP_REF_LUMA
-D NLM_WMODE_WELSCH
-D VI_DIM_X=720
-D VI_DIM_Y=480
-D HRZ_RESULT=1
-D VRT_RESULT=1
-D HRZ_BLOCK_X=32
-D HRZ_BLOCK_Y=8
-D VRT_BLOCK_X=32
-D VRT_BLOCK_Y=8
-D NLM_D=1
-D NLM_S=4
-D NLM_H=1.200000
-D NLM_WREF=1.000000
CL_PROGRAM_BUILD_LOG:
Error returned by cvms_element_build_from_source

RETURN: 0
The old version 0.7.7 works well for you?

KingLir

2nd March 2017, 19:59

The old version 0.7.7 works well for you?

Haven't tried until now:

(clCreateImage(d.mem_in[0]): CL_IMAGE_FORMAT_NOT_SUPPORTED)
Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1712, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:34991)
File "VIVTC_with_TComb_script.vpy", line 22, in <module>
clip = core.knlm.KNLMeansCL(clip=clip)
File "src/cython/vapoursynth.pyx", line 1604, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:33131)
vapoursynth.Error: knlm.KNLMeansCL: fatal error!
(clCreateImage(d.mem_in[0]): CL_IMAGE_FORMAT_NOT_SUPPORTED)

Khanattila

3rd March 2017, 16:54

Haven't tried until now:

(clCreateImage(d.mem_in[0]): CL_IMAGE_FORMAT_NOT_SUPPORTED)
Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1712, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:34991)
File "VIVTC_with_TComb_script.vpy", line 22, in <module>
clip = core.knlm.KNLMeansCL(clip=clip)
File "src/cython/vapoursynth.pyx", line 1604, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:33131)
vapoursynth.Error: knlm.KNLMeansCL: fatal error!
(clCreateImage(d.mem_in[0]): CL_IMAGE_FORMAT_NOT_SUPPORTED)
Another job for you
https://github.com/Khanattila/KNLMeansCL/archive/osx.zip