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

[Khanattila]

I'm a little confused
I have GF 550M, so I guess it's not supported on versions later 0.6.11
But when I run it on v0.7.6, I get error not about compatibility
Python exception: knlm.KNLMeansCL: fatal error!
(clBuildProgram: please report Log-KNLMeansCL.txt.)
Log-KNLMeansCL.txt (http://paste2.org/PIOVKvGI)
on v0.6.11 it's works fine
Win7 64bit

AIDA64 show this (http://paste2.org/jPaU4exV)
OpenCL Compliancy:
OpenCL 1.1 Yes (100%)
OpenCL 1.2 Yes (100%)
OpenCL 2.0 No (62%)

so... %)

NVDIA has never released an OpenCL 1.2 drivers for the 500 Series. Platform Version must be wrong.
Or it provided only some features and not everything you need.

[Khanattila]

I'm getting this error:

"Display driver stopped responding and has recovered Display driver NVIDIA Windows Kernal Mode Driver, Version 364.96 stopped responding and has successfully recovered"

This happens when I'm running madvr and at the same time running this filter during encoding via staxrip

Is there something we could do about this?


You have this error in exclusive mode?

[Magik Mark]

No. In window mode using mpc be. Video hasn't played at all. Video player shuts down on its own. I have to restart 2 or 3 times before it starts playing again


Sent from my iPhone using Tapatalk

[asarian]

Is DGSource (from the DG NV Tools) incompatible with KNLMeansCL or something?! DGSource suddenly gives me an error about not being able to create a video instance of sorts.

This is a real pain, and DGSource is the really frame-safe processor I know (which actually *is* frame safe, and not just claims so).

[Sparktank]

Is DGSource (from the DG NV Tools) incompatible with KNLMeansCL or something?! DGSource suddenly gives me an error about not being able to create a video instance of sorts.

It should be compatible.

Win7 (x64), GeForce GTX 750t TI, 364.72.
Using the latest slipstream of DGdecNV 2051:
DGDecodeNV 2051 [Mar 17, 2016]
I haven't received any email notifications of a new slipstream or update from a subscribed thread.

Still using AVS_260_MT, however.

avsinfo:
Avisynth version string: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
File version: 2.6.0.5
Avisynth Interface Version: 6
Muli-threading support: Yes
Linker/compiler version: 12.0
Avisynth DLL location: C:\Windows\SysWOW64\avisynth.dll
Avisynth DLL time stamp: 2015-02-19, 17:18:42
PluginDir2_5 (HKCU, x86): D:\AVS_Ver\AVS260_MT\plugins
PluginDir2_5 (HKLM, x86): D:\AVS_Ver\AVS260_MT\plugins

test on a bluray remux:
SetMemoryMax(512)
DGSource("E:\Temp\remux\ThePrestige\Prestige.dgi")
Crop(0, 130, -0, -132)
# v0.7.6 ## autoloaded from PluginDir
KNLMeansCL(info=true)
https://i.imgur.com/PSV4dbil.png (https://imgur.com/PSV4dbil)

[Magik Mark]

Is it possible to use CPU processing instead the GPU utilizing all of my 14 Cores - 28 Threads? Tried installing intel OpenCL driver. It could only go as high as 2-3 fps. I wish it could go as high as 25fps

[Bloax]

For that you'd probably want to use http://forum.doom9.org/showthread.php?p=1746705#post1746705 the existing non-GPU implementations of NLMeans.

[Khanattila]

Is it possible to use CPU processing instead the GPU utilizing all of my 14 Cores - 28 Threads? Tried installing intel OpenCL driver. It could only go as high as 2-3 fps. I wish it could go as high as 25fps

Non-local means de-noising algorithm is slow. If you want an example: http://forum.doom9.org/showpost.php?p=1739321&postcount=467

[asarian]

From my experience, DGSource is incompatible with KNLMeansCL only on Win10 when using the 32-bit plugins. The program (like AvsPmod, vspipe or whatever) just hangs and doesn't output anything at all. But it still works fine when using the 64-bit plugins. The issue seems to not exist on Win8 and all previous Windows version.

Thanks for your reply. Yes, I'm on Windows 10, and sadly my AviSynth is still 32-bit (need it for MCTemporalDenoise). With KNLMeansCL, though, I may just have to go to 64-bit AS, and just forget about MCTemporalDenoise altogether, as KNLMeansCL makes things go so much faster!

[asarian]

Is it possible to use CPU processing instead the GPU utilizing all of my 14 Cores - 28 Threads? Tried installing intel OpenCL driver. It could only go as high as 2-3 fps. I wish it could go as high as 25fps

I suppose you could set

device_type="CPU"

But what would be the point of using KNLMeansCL then?! Haven't tested it (running a major job right now), but I bet simply using something based on dfttest will be equally fast, if not faster, without the use of a GPU.

[feisty2]

I suppose you could set

device_type="CPU"

But what would be the point of using KNLMeansCL then?! Haven't tested it (running a major job right now), but I bet simply using something based on dfttest will be equally fast, if not faster, without the use of a GPU.

Except simple frequency denoiser without any additional block matching is not even on the same quality level of NLMeans..
Do remember that NLMeans is one of the highest quality denoisers, it's just not something that DFTTest could replace.

[mastrboy]

What would the KNLMeansCL equivalent of NLMeansCL(A=9,H=0.9) be?
I tried to compare the manuals, but the information regarding what all the parameters for NLMeansCL (http://forum.doom9.org/showthread.php?t=158925) do, is not that well documented. For example, parameter S and B are only described by what their default value is.

[asarian]

Except simple frequency denoiser without any additional block matching is not even on the same quality level of NLMeans...

Which is why I said based on dfttest (like inside MCTemporalDenoise or something).

MCTD, running entirely on CPU, is actually quite slow (can't seem to benefit much from multi-threading), so KNLMeansCL, running on CPU only, could probably give it a run for its money too, but part of its charm, for me, is the offloading to GPU, of course.

Do remember that NLMeans is one of the highest quality denoisers, it's just not something that DFTTest could replace.

Only found out about it recently, but KNLMeansCL really is unusually crisp, I must admit. I'm trying to make it my main denoiser now, for everything.

[Magik Mark]

Guys,

Can you share your parameters for light, moderate & strong settings?

Thanks

[Magik Mark]

I'm getting this error:

"Display driver stopped responding and has recovered Display driver NVIDIA Windows Kernal Mode Driver, Version 364.96 stopped responding and has successfully recovered"

This happens when I'm running madvr and at the same time running this filter during encoding via staxrip

Is there something we could do about this?

This error is also happening in Hybrid. You don't get an error message. Hybrids will just stop the encoding. You have to do it allover again. In staxrip, it is able to recover

[Khanattila]

What would the KNLMeansCL equivalent of NLMeansCL(A=9,H=0.9) be?
I tried to compare the manuals, but the information regarding what all the parameters for NLMeansCL (http://forum.doom9.org/showthread.php?t=158925) do, is not that well documented. For example, parameter S and B are only described by what their default value is.
Test KNLMeansCL(a=9, h=0.9).

KNLMeansCL don't have B, and on default s=4.

Az ==> d
Ax and Ay ==> a
Sx and Sy ==> s
Bx and By ==> removed (equivalent to Bx=By=0)

[tormento]

I was playing with x64 again and got same error I had previously.

AVS:
SetMemoryMax(8000)
SetFilterMTMode("DEFAULT_MT_MODE", 2)
SetFilterMTMode("DGSource", 3)
LoadPlugin("D:\eseguibili\media\DGDecNV\x64\DGDecodeNV.dll")
LoadPlugin("D:\Programmi\media\AviSynth+\plugins64\KNLMeansCL-0.7.6.dll")
DGSource("E:\in\1_42 John Wick\johnnv.dgi")
CompTest(1)
ChangeFPS(last,last,true)
KNLMeansCL(device_type="GPU")

Command line:
avs4x26x-x64.exe --x264-binary "x264_64.exe" --level 4.1 --crf 20 --keyint 240 --vbv-bufsize 78125 --vbv-maxrate 62500 --aq-mode 2 --sar 1:1 "E:\in\1_42 John Wick\johnnv.mkv" "E:\in\1_42 John Wick\johnnv.avs"

Error:
avs [error]: Cannot load file 'D:/Programmi/media/AviSynth+/plugins64/KNLMeansCL-0.7.6.dll'. Platform returned code 126:
Impossibile trovare il modulo specificato.

(E:\in\1_42 John Wick\johnnv.avs, line 5)

Any idea? It works removing KNL line.

[Zetti]

I was playing with x64 again and got same error I had previously.

AVS:
SetMemoryMax(8000)
SetFilterMTMode("DEFAULT_MT_MODE", 2)
SetFilterMTMode("DGSource", 3)
LoadPlugin("D:\eseguibili\media\DGDecNV\x64\DGDecodeNV.dll")
LoadPlugin("D:\Programmi\media\AviSynth+\plugins64\KNLMeansCL-0.7.6.dll")
DGSource("E:\in\1_42 John Wick\johnnv.dgi")
CompTest(1)
ChangeFPS(last,last,true)
KNLMeansCL(device_type="GPU")

Command line:
avs4x26x-x64.exe --x264-binary "x264_64.exe" --level 4.1 --crf 20 --keyint 240 --vbv-bufsize 78125 --vbv-maxrate 62500 --aq-mode 2 --sar 1:1 "E:\in\1_42 John Wick\johnnv.mkv" "E:\in\1_42 John Wick\johnnv.avs"

Error:
avs [error]: Cannot load file 'D:/Programmi/media/AviSynth+/plugins64/KNLMeansCL-0.7.6.dll'. Platform returned code 126:
Impossibile trovare il modulo specificato.

(E:\in\1_42 John Wick\johnnv.avs, line 5)

Any idea? It works removing KNL line.

I think you need to add device_id

int device_id The 'device_id'+1º device of type 'device_type' in the system.
Example: [device_type = "GPU", device_id = 1] return the second
GPU in the system.

Default: 0.

[asarian]

Why, my Italian sucks, but I think 'Impossibile trovare il modulo specificato' just means 'Cannot find the specified dll.' Adding device_id, at least, is not necessary at all. Check the path of said dll!

[tormento]

Why, my Italian sucks, but I think 'Impossibile trovare il modulo specificato' just means 'Cannot find the specified dll.' Adding device_id, at least, is not necessary at all. Check the path of said dll!
Path checked.

Similar command line / configuration win32 it works (obviously with DGDecIM).

[tormento]

Did you check the requirements in the first post of this thread? This error usually comes up when a MS redist package is missing.
Yep. As I said on win32 it works (with necessary modifications)

[tormento]

I think you need to add device_id
Same behaviour

[asarian]

Path checked.

Are you entirely sure?! My dll is just called KNLMeansCL.dll, as opposed to your:

D:\Programmi\media\AviSynth+\plugins64\KNLMeansCL-0.7.6.dll")

[asarian]

I also don't understand why he's using Loadplugin at all.

Yeah, that's another thing. :) If it's in the plugins64 folder, it should get autoloaded.

But the name worries me the most. Both 32- and 64-bit dll's, extracted from the official KNLMeansCL-0.7.6 package, are just called KNLMeansCL.dll; can't see any good reason why anyone would rename them (as newer version are *supposed* to overwrite the old, and shouldn't be kept in the same plugins64 dir, unless you went for willful breakage).

[tormento]

Can't see that mentioned in your post.
Months ago XD

[tormento]

Are you entirely sure?! My dll is just called KNLMeansCL.dll, as opposed to your:

D:\Programmi\media\AviSynth+\plugins64\KNLMeansCL-0.7.6.dll")

Yes I checked more than twice

[tormento]

Yeah, that's another thing. :) If it's in the plugins64 folder, it should get autoloaded.

But the name worries me the most. Both 32- and 64-bit dll's, extracted from the official KNLMeansCL-0.7.6 package, are just called KNLMeansCL.dll; can't see any good reason why anyone would rename them (as newer version are *supposed* to overwrite the old, and shouldn't be kept in the same plugins64 dir, unless you went for willful breakage).

I knows it's autoloaded. I forced to try to get rid of error.

I rename dll as I can check and remember every version of plugins I own. Not everyone has version inside dll.

[Sparktank]

I knows it's autoloaded. I forced to try to get rid of error.

I rename dll as I can check and remember every version of plugins I own. Not everyone has version inside dll.

Have you opened the .dgi file in a notepad and verified the filepaths are correct?
If you moved any of the asset files at all, the paths need to be updated in the .dgi index then in the .avs script.

[mastrboy]

Test KNLMeansCL(a=9, h=0.9).

KNLMeansCL don't have B, and on default s=4.

Az ==> d
Ax and Ay ==> a
Sx and Sy ==> s
Bx and By ==> removed (equivalent to Bx=By=0)

I tried that, and the fps went from ~80 with NLmeanscl to ~25 fps with KNLmeansCL (3,2x decrease in speed), also the histogram(luma) show quite a difference in output between the two.
That's why I posted since I assumed A for NLmeansCL is not the same as A for KNLmeansCL.

The performance and output difference where big enough to need further information about the difference between the two.

[Khanattila]

I tried that, and the fps went from ~80 with NLmeanscl to ~25 fps with KNLmeansCL (3,2x decrease in speed), also the histogram(luma) show quite a difference in output between the two.
That's why I posted since I assumed A for NLmeansCL is not the same as A for KNLmeansCL.

The performance and output difference where big enough to need further information about the difference between the two.

Bx and By (NLMeansCL) are trade-off performance/quality. KNLMeansCL don't have it.
That's why the results are different.

At equal quality, KNLMeansCL is faster than NLMeansCL.
However, each argument is documented. Read the doc (https://github.com/Khanattila/KNLMeansCL/blob/master/DOC.md).

[Magik Mark]

Khanattila,

I'm having problem converting these to NLmeans. Can you help? Thanks


KNLMeansCL(D = 1, A = 1, h = 2)
KNLMeansCL(D = 1, A = 1, h = 4)
KNLMeansCL(D = 1, A = 1, h = 8)

[tormento]

Run "avsmeter64 -avsinfo -log" and post the log file.

Avisynth version string: AviSynth+ 0.1 (r1849, MT-pfmod, x86_64)
File version: 0.1.0.0
Avisynth Interface Version: 6
Muli-threading support: Yes
Linker/compiler version: 14.0
Avisynth DLL location: C:\Windows\System32\AviSynth.dll
Avisynth DLL time stamp: 2016-04-22, 14:40:06
PluginDir+ (HKLM, x64): D:\Programmi\media\AviSynth+\plugins64+
PluginDir2_5 (HKLM, x64): D:\Programmi\media\AviSynth+\plugins64

Avisynth CPP 2.6 plugins:
D:\Programmi\media\AviSynth+\plugins64+\DirectShowSource.dll (n/a)
D:\Programmi\media\AviSynth+\plugins64+\ImageSeq.dll (n/a)
D:\Programmi\media\AviSynth+\plugins64+\Shibatch.dll (n/a)
D:\Programmi\media\AviSynth+\plugins64+\TimeStretch.dll (n/a)
D:\Programmi\media\AviSynth+\plugins64+\VDubFilter.dll (n/a)
D:\Programmi\media\AviSynth+\plugins64\AutoAdjust-2.00.dll (2.0.0.0)
D:\Programmi\media\AviSynth+\plugins64\KNLMeansCL-0.7.6.dll (n/a)
D:\Programmi\media\AviSynth+\plugins64\MVTools-2.7.0.22—pfmod.dll (2.7.0.22)
D:\Programmi\media\AviSynth+\plugins64\NNEDI3-0.9.4.20_AVX2.dll (0.9.4.20)
D:\Programmi\media\AviSynth+\plugins64\NNEDI3-0.9.4.20_AVX512.dll (0.9.4.20)
D:\Programmi\media\AviSynth+\plugins64\NNEDI3-0.9.4.20_SSE42.dll (0.9.4.20)
D:\Programmi\media\AviSynth+\plugins64\RgTools-0.92.1.dll (n/a)
D:\Programmi\media\AviSynth+\plugins64\SmoothAdjust-3.00.dll (3.0.0.0)

Avisynth CPP 2.5 plugins:
D:\Programmi\media\AviSynth+\plugins64\AddGrainC-1.7.1—cretindesalpes.dll (1.7.1.0)
D:\Programmi\media\AviSynth+\plugins64\AvsTP-1.0.3.dll (1.0.3.0)
D:\Programmi\media\AviSynth+\plugins64\DFTTest-1.9.4.dll (1.9.4.0)
D:\Programmi\media\AviSynth+\plugins64\Dither-1.27.2.dll (n/a)
D:\Programmi\media\AviSynth+\plugins64\FFT3DFilter-2.1.1_ICL11—Groucho2004.dll (2.1.1.0)
D:\Programmi\media\AviSynth+\plugins64\MaskTools-2.0a48.dll (2.0.48.0)
D:\Programmi\media\AviSynth+\plugins64\RemoveGrainHD-0.5.dll (0.5.0.0)

To clarify to everybody: a simple script, with no KNLMeans, works perfectly.

For example:

SetMemoryMax(8000)
SetFilterMTMode("DEFAULT_MT_MODE", 2)
SetFilterMTMode("DGSource", 3)
LoadPlugin("D:\eseguibili\media\DGDecNV\x64\DGDecodeNV.dll")
LoadPlugin("D:\Programmi\media\AviSynth+\plugins64\KNLMeansCL-0.7.6.dll")
DGSource("E:\in\1_42 John Wick\johnnv.dgi")
CompTest(1)
ChangeFPS(last,last,true)
SMDegrain (tr=4,PreFilter=2,thSAD=400,contrasharp=false,refinemotion=false,plane=4,chroma=true,lsb=true,mode=6)
Prefetch(8)

[E:\in\1_42 John Wick]"D:\eseguibili\media\MeGUI\tools\x264\avs4x26x-x64.exe" --x264-binary "D:\eseguibili\media\MeGUI\tools\x264\x264_64.exe"
--level 4.1 --crf 20 --keyint 240 --vbv-bufsize 78125 --vbv-maxrate 62500 --aq-mode 3 --sar 1:1 --output "E:\in\1_42 John Wick\johnnv.mkv"
"E:\in\1_42 John Wick\johnnv.avs"
avs [info]: AviSynth+ 0.1 (r1849, MT-pfmod, x86_64)
avs [info]: Video colorspace: YV12
avs [info]: Video resolution: 1920x800
avs [info]: Video framerate: 239999/10000
avs [info]: Video framecount: 1470
avs4x26x [info]: "D:\eseguibili\media\MeGUI\tools\x264\x264_64.exe" - --level 4.1 --crf 20 --keyint 240 --vbv-bufsize 78125 --vbv-maxrate 62500
--aq-mode 3 --sar 1:1 --output "E:\in\1_42 John Wick\johnnv.mkv" --frames 1470 --fps 239999/10000 --input-res 1920x800 --input-csp i420
raw [info]: 1920x800p 1:1 @ 239999/10000 fps (cfr)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
x264 [info]: profile High, level 4.1
x264 [info]: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 fade_compensate=0.00 psy_rd=1.00:0.00 mixed_ref=1
me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2
sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 fgo=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0
direct=1 weightb=1 open_gop=0 weightp=2 keyint=240 keyint_min=23 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=20.0000
qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 vbv_maxrate=62500 vbv_bufsize=78125 crf_max=0.0 nal_hrd=none filler=0 ip_ratio=1.40 aq=3:1.00
frames fps kb/s elapsed remain size est.size
[100.0%] 1470/1470 11.42 3113.58 0:02:08 0:00:00 22.73 MB 22.73 MB
x264 [info]: frame I:111 Avg QP:14.29 size: 76019
x264 [info]: frame P:455 Avg QP:18.11 size: 17635
x264 [info]: frame B:904 Avg QP:19.20 size: 8159
x264 [info]: consecutive B-frames: 16.4% 3.5% 3.9% 76.2%
x264 [info]: mb I I16..4: 22.3% 59.0% 18.7%
x264 [info]: mb P I16..4: 7.8% 12.1% 1.2% P16..4: 28.4% 7.3% 5.6% 0.0% 0.0% skip:37.7%
x264 [info]: mb B I16..4: 0.7% 1.5% 0.2% B16..8: 35.2% 2.9% 0.4% direct: 1.9% skip:57.1% L0:43.3% L1:53.1% BI: 3.6%
x264 [info]: 8x8 transform intra:58.4% inter:91.0%
x264 [info]: coded y,uvDC,uvAC intra: 45.6% 55.0% 28.6% inter: 10.8% 10.4% 0.5%
x264 [info]: i16 v,h,dc,p: 49% 20% 6% 26%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 27% 17% 24% 4% 6% 6% 5% 5% 5%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 39% 19% 15% 4% 7% 5% 5% 4% 3%
x264 [info]: i8c dc,h,v,p: 55% 18% 21% 7%
x264 [info]: Weighted P-Frames: Y:3.3% UV:3.1%
x264 [info]: ref P L0: 72.7% 7.6% 13.1% 6.1% 0.5%
x264 [info]: ref B L0: 89.9% 8.4% 1.7%
x264 [info]: ref B L1: 94.7% 5.3%
x264 [info]: kb/s:3113.47

encoded 1470 frames, 11.42 fps, 3113.58 kb/s, duration 0:02:08.69

[Khanattila]

I was playing with x64 again and got same error I had previously.

AVS:
SetMemoryMax(8000)
SetFilterMTMode("DEFAULT_MT_MODE", 2)
SetFilterMTMode("DGSource", 3)
LoadPlugin("D:\eseguibili\media\DGDecNV\x64\DGDecodeNV.dll")
LoadPlugin("D:\Programmi\media\AviSynth+\plugins64\KNLMeansCL-0.7.6.dll")
DGSource("E:\in\1_42 John Wick\johnnv.dgi")
CompTest(1)
ChangeFPS(last,last,true)
KNLMeansCL(device_type="GPU")

Command line:
avs4x26x-x64.exe --x264-binary "x264_64.exe" --level 4.1 --crf 20 --keyint 240 --vbv-bufsize 78125 --vbv-maxrate 62500 --aq-mode 2 --sar 1:1 "E:\in\1_42 John Wick\johnnv.mkv" "E:\in\1_42 John Wick\johnnv.avs"

Error:
avs [error]: Cannot load file 'D:/Programmi/media/AviSynth+/plugins64/KNLMeansCL-0.7.6.dll'. Platform returned code 126:
Impossibile trovare il modulo specificato.

(E:\in\1_42 John Wick\johnnv.avs, line 5)

Any idea? It works removing KNL line.
Please check it with Dependency Walker.
Imho OpenCL.dll is broken.

[Khanattila]

Khanattila,

I'm having problem converting these to NLmeans. Can you help? Thanks


KNLMeansCL(D = 1, A = 1, h = 2)
KNLMeansCL(D = 1, A = 1, h = 4)
KNLMeansCL(D = 1, A = 1, h = 8)

Really, I do not understand what is so difficult.

[Sparktank]

:confused:

My mistake. Running on 4 hours of sleep lately.

[tormento]

Doesn't SMDegrain use KNLMeansCL as well? Also what's up with all these nnedi3 DLLs? You should only have one.
Yes... I leaved them as archive only. I will rename.

[tormento]

Please check it with Dependency Walker.
Imho OpenCL.dll is broken.
Tried and a enormous quantity of yellow question marks appeared.

How can I get a sense about that?

Do you think it is wise to replace opencl.dll found on Windows 10 system with yours? I have a Nvidia 760 card and that OpenCL.dll is the Nvidia version of Khronos 1.2.11.0

[tormento]

Save the Dep Walker analysis as .dwi and post it somewhere.

Here (https://www.solidfiles.com/v/Az6nzGVPdLNGr)it is. Thanks!

[tormento]

It's pretty clear that you did not install the VC2015 redistributable even though you claimed you did.
I reinstalled
18/03/2016 08:59 13.969.576 Visual C++ 2015 Redistributable Update 2.exe
18/03/2016 08:58 14.749.128 Visual C++ 2015 Redistributable Update 2_x64.exe

Result (https://www.solidfiles.com/v/3GKdDqe2dV455)

Notice any difference? Not to my eyes :)

Anyway reinstall worked. I think last time I installed x64 package only. Is possible that x64 KNL needs x86?

[Groucho2004]

Result (https://www.solidfiles.com/v/3GKdDqe2dV455)

Notice any difference? Not to my eyes :)
I'm not downloading from that site again. Pure popup hell.

Anyway reinstall worked. I think last time I installed x64 package only. Is possible that x64 KNL needs x86?
If the re-install worked then something was wrong with the redistributables, wouldn't you agree? I don't even know which version (x86/x64) of DepWalker you used.

I'm going to delete all my posts relating to this issue, I suggest you do the same.

[asarian]

I reinstalled
18/03/2016 08:59 13.969.576 Visual C++ 2015 Redistributable Update 2.exe
18/03/2016 08:58 14.749.128 Visual C++ 2015 Redistributable Update 2_x64.exe

Result (https://www.solidfiles.com/v/3GKdDqe2dV455)

Notice any difference? Not to my eyes :)?


The Redistributables (that sounds like a good title for a movie :P) also say you need to reboot your system after install. Maybe you hadn't?!

[Groucho2004]

The Redistributables (that sounds like a good title for a movie :P)
Agreed. :cool:


you need to reboot your system after install. Maybe you hadn't?!
That should not be necessary. However, I use the redist pack from ricktendo, much smaller and no Microsoft installer bullshit included. I never had to reboot, even when installing all versions from 2003 - 2015 in one go.

[tormento]

However, I use the redist pack from ricktendo, much smaller and no Microsoft installer bullshit included.
Where to download them?

[Zetti]

Where to download them?

http://my.repacks.space/VBCRedist_AIO_x86_x64.exe

[MysteryX]

To test whether the latest version of KNLMeans can be used on a computer, I run this script.


P="Encoder\"
LoadPlugin(P+"KNLMeansCL.dll")
colorbars(pixel_type = "yv12").killaudio().trim(1, 1)
Result = true
try {
KNLMeansCL()
} catch(error_msg) {
Result = false
}
WriteFileStart("Temp.txt", string(Result))


If it returns false, I'll use version 6.11 instead. If the graphic card doesn't support GPU processing and v6.11 also fails, then what's my best option? Will CPU processing still work with either version?

[Groucho2004]

http://my.repacks.space/VBCRedist_AIO_x86_x64.exe
Direct linking doesn't seem to work. Here (http://repacks.net/forum/viewtopic.php?f=6&t=125) is the page.

[burfadel]

There's also the one I do, it's packaged and installs a little differently. It also removes any existing runtimes of that particular version (2015 etc) before installing the new version. This is beneficial so you don't have multiple redundant versions, and possibly resolves issues with existing installations. V42 is currently the latest version: https://onedrive.live.com/redir?resid=C1FACEB7B51DAE61!376011&authkey=!ANXnlaivqizeKUM&ithint=file%2cexe

The latest version can always be found here:
https://onedrive.live.com/redir?resid=C1FACEB7B51DAE61%21376011

I should point out that Ricktendo64 and I aren't competing for usership, it's just about providing options and choice.

[Khanattila]

To test whether the latest version of KNLMeans can be used on a computer, I run this script.


P="Encoder\"
LoadPlugin(P+"KNLMeansCL.dll")
colorbars(pixel_type = "yv12").killaudio().trim(1, 1)
Result = true
try {
KNLMeansCL()
} catch(error_msg) {
Result = false
}
WriteFileStart("Temp.txt", string(Result))


If it returns false, I'll use version 6.11 instead. If the graphic card doesn't support GPU processing and v6.11 also fails, then what's my best option? Will CPU processing still work with either version?
Of course. CPU processing should work in any version.
Just install the OpenCL driver for CPU. Intel specific or AMD generic.

[Magik Mark]

May I ask the best settings for removing film grain?

Thanks


Sent from my iPhone using Tapatalk

[tormento]

Just upgraded Win10_x64 to build 14342.

Pay attention that OpenCL.dll goes to heaven, dunno why. After having reinstalled, deinstalled, installed VC2015 redistributables, I found that small problem.

Reinstalling Nvidia drivers made things work again.

Just a reminder to everybody on fast build channel ;)