RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY

[guest]

Didn't check, as I rarely use the preview.

Will check ASAP, and get back !!!!

OK, back to this..........

Have done a test, and running Preview, it had some big red text, showing the error msg.

KNLMeansCL:Fatal error
(clBuildProgram: please report Log-KNLMeansCL.txt)

So please find that log txt file attached for you perusal.

There were NO problems when using x264 !!!!

OK, another day, another test...

I loaded another file into Ripbot, chose KNLMeansCL, and did a preview....no problems :), BUT, as soon as I changed the Mono Noise to anything other than "0", it threw up an error in preview.

Cannot load: C:/Users/Documents/Ripbot264v1.19.3/Tools/Avisynth plugins/KNLMeansCL/KNLMeansCL.dll

So quite different the error log.txt I sent thru yesterday.

Hope this sheds a bit more light on the problem (unless it's just me)

[dv8r]

I'm looking at the radeon firepro cards burt. From everything i'm reading amd is way ahead in opencl. I get much better compression with the slow or slower setting. Quality is great with all the settings but the file size comes from which speed setting I'm in.

[guest]

I'm looking at the radeon firepro cards burt. From everything i'm reading amd is way ahead in opencl. I get much better compression with the slow or slower setting. Quality is great with all the settings but the file size comes from which speed setting I'm in.

So would the Firepro be noticably better that the "ordinary" HD or R series cards. Aren't Firepro's pretty expensive ??

Also, have you been using KNLMeans with x265 ??? If so, have you had the problem I've had (refer to previous posts).

Cheers

[guest]

OK, another day, more test's...

I loaded another file into Ripbot, chose KNLMeansCL, and did a preview....no problems :), BUT, as soon as I changed the Mono Noise to anything other than "0", it threw up an error in preview.

Cannot load: C:/Users/Documents/Ripbot264v1.19.3/Tools/Avisynth plugins/KNLMeansCL/KNLMeansCL.dll

I need to add that the above error is when using Avisynth +.

If I use Avisynth 2.60 the error message is rather different.

Along the lines of not finding the plugin, and that the missing library needs to be installed.

And now it's happening with both x264 & x265..any KNLMeansCL setting above 0 Mono Noise.

I even went to the trouble of downloading 1.19.2, and ALL the updates, but that didn't help :(.

[Atak_Snajpera]

yes you need avisynth 2.6 instead of +. I'm currently using 2.6.0.6.

[guest]

yes you need avisynth 2.6 instead of +. I'm currently using 2.6.0.6.

Yep, that's the version I have, and that's when KNLMeansCL says it can't load the libraries :(

See attached

[Atak_Snajpera]

Do not post images like that unless you want to get response after two weeks.

[soneca]

Yep, that's the version I have, and that's when KNLMeansCL says it can't load the libraries :(

See attached

This problem should be similar to mine, I'm using version 2.6.0(May 31, 2015) and the video card is compatible with OpenCL 1.2.

E:\>"C:\Programas\RipBot264v1.19.2\tools\avs2yuv\avs2yuv.exe" "E:\Temp\RipBot264temp\job16\job16.avs" -o - | "C:\Programas\RipBot264v1.19.2\tools\x264\x264_x64.exe" --crf 18 --fps 24000/1001 --force-cfr --min-keyint 24 --keyint 240 --frames 512 --sar 1:1 --preset slower --tune film --stdin y4m --output "E:\Temp\RipBot264temp\video.264" -
error: LoadPlugin: unable to load "C:\Programas\RipBot264v1.19.2\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll", Module not found. Install missing library?
(E:\Temp\RipBot264temp\job16\job16.avs, line 29)
y4m [error]: bad sequence header magic
x264 [error]: could not open input file `-'

[Atak_Snajpera]

Does this file exist in this path "C:\Programas\RipBot264v1.19.2\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll" ?

[guest]

Does this file exist in this path "C:\Programas\RipBot264v1.19.2\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll" ?

Mine is here:-...RipBot264v1.19.3\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll, but not in C:/Programs.

I haven't got a c:/Programs !!! (Windows 10)

Do I need to have the Ripbot folder in a particular place, I thought it was "portable", and I've always had it in the Documents Folder.

As yes, this is also my error.

[guest]

Do not post images like that unless you want to get response after two weeks.

I apologize, is it because it takes that long to be "approved" ??

[Atak_Snajpera]

Mine is here:-...RipBot264v1.19.3\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll, but not in C:/Programs.

I haven't got a c:/Programs !!! (Windows 10)

Do I need to have the Ripbot folder in a particular place, I thought it was "portable", and I've always had it in the Documents Folder.

As yes, this is also my error.

It was question for soneca

[Atak_Snajpera]

I apologize, is it because it takes that long to be "approved" ??

Sometimes it takes 1-2 weeks... I'm surprised that you haven't noticed that already ;)

[guest]

It was question for soneca

Maybe so, but know I'm "happy" that I am not the only one that is having a problem.

And, DOES Ripbot need to be in a particular location, or IS it portable ???

[guest]

Sometimes it takes 1-2 weeks... I'm surprised that you haven't noticed that already ;)

Very rarely attach anything, so no.........:)

[soneca]

Does this file exist in this path "C:\Programas\RipBot264v1.19.2\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll" ?

Yes, all right. This file may be corrupted, it was replaced but the message remains.
At least on the other machine is working properly. ;)

http://s20.postimg.org/s8hyawuq5/knl.png

[guest]

Yes, all right. This file may be corrupted, it was replaced but the message remains.
At least on the other machine is working properly. ;)

http://s20.postimg.org/s8hyawuq5/knl.png

So you've got problem's on one PC, but not the other ?!?!?

[Atak_Snajpera]

Most likely knlmeanscl is unable to initialize opencl.dll library. NVIDIA opencl drivers are probably buggy.

[soneca]

The two PCs have the latest(361.75) drivers from nvidia.

[soneca]

So you've got problem's on one PC, but not the other ?!?!? Yes, strange that! :confused:

[Wildfire]

The latest beta is 361.82 which includes a fix for the videocard suddenly becoming an ejectable device. Might try those just for the sake of it.

[guest]

Yes, strange that! :confused:

It would be annoying, alright.

Its a shame that Atak has gone to the trouble of adding this feature, and us nVidia users are having problems :(

Well, I'm going to try the latest drivers, and also try the process on one of my AMD carded PC's.

I have to say, I wonder how Handbrake gets it work ???

[guest]

The two PCs have the latest(361.75) drivers from nvidia.

How different are the 2 pc's ??

[guest]

The latest beta is 361.82 which includes a fix for the videocard suddenly becoming an ejectable device. Might try those just for the sake of it.

Didn't work for me :(

GTX 580, Windows 10 x64 1511

[guest]

OK, finally got to test this on an AMD graphics carded PC (HD6850), and it worked a treat.

Also tried with HD4870, Windows 8.1, threw up a "new" error msg, in preview. error=0x7e (Missing DLL, Error 0x7e) apparently.

Try latest nVidia drivers on GTX580, Windows 10, no change, still has problems.

Next test, GTX680, Windows 10.

OK, just did a test on the GTX680 Windows 10 PC, and that works :)

So, is it the GTX580, being too old for this version ??

[Atak_Snajpera]

yes radeon hd4xxx and gtx580 are too old.

[guest]

yes radeon hd4xxx and gtx580 are too old.

Bugger, so that's it, then, no workaround ???

Time to upgrade then :(

So what card do you have ???

So would an R series AMD card do a good enough job, or would it be better to go for a "mid level" FirePro V7900.

[Atak_Snajpera]

I still have r4850. I recommend some used r7850.

[guest]

I still have r4850. I recommend some used r7850.

So that means that you can't use KNLMeansCL, then !!!

[Atak_Snajpera]

No I can't.

[soneca]

How different are the 2 pc's ??

Basically the pc that it works using the GTX 760 card and the other does not work that uses the GTX650. But the strange thing is that the two video cards are 100% compatible with OpenCL 1.2 and at least theoretically should work.

[Ryushin]

Is it possible to add software based NLMeans sometime in the future? My servers only have basic video output to just display the console.

Plus with DE every device would have to have an appropriate card in order to work.

[Atak_Snajpera]

You can have software NLMeans even now. Replace GPU string with CPU in script.

[guest]

You can have software NLMeans even now. Replace GPU string with CPU in script.

You've gotta be kiddin' me !!!!! :confused:

So how come you chose to go down the GPU route ?

#Denoise
LoadPlugin("C:\Users\burt123\Documents\RipBot264v1.19.3\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll")
LoadPlugin("C:\Users\burt123\Documents\RipBot264v1.19.3\Tools\AviSynth plugins\flash3kyuu_deband\flash3kyuu_deband.dll")
video=KNLMeansCL(video,d=1, a=2, s=4, h=2, device_type="GPU").f3kdb

Is the above line the one that needs to be changed ???

If so, I DID change the "GPU" to "CPU", and it didn't change anything :(

[soneca]

I had tried the CPU did not work.
PC does not work GPU, the same message.
E:\>"C:\Programas\RipBot264v1.19.2\tools\avs2yuv\avs2yuv.exe" "E:\Temp\RipBot264temp\job16\job16.avs" -o - | "C:\Programas\RipBot264v1.19.2\tools\x264\x264_x64.exe" --crf 18 --fps 24000/1001 --force-cfr --min-keyint 24 --keyint 240 --frames 512 --sar 1:1 --preset slower --tune film --stdin y4m --output "E:\Temp\RipBot264temp\video.264" -
error: LoadPlugin: unable to load "C:\Programas\RipBot264v1.19.2\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll", Module not found. Install missing library?
(E:\Temp\RipBot264temp\job16\job16.avs, line 29)
y4m [error]: bad sequence header magic
x264 [error]: could not open input file `-'

PC running GPU the message changes.
E:\>"C:\Programas\RipBot264v1.19.2\tools\avs2yuv\avs2yuv.exe" "E:\Temp\RipBot264temp\job41\job41.avs" -o - | "C:\Programas\RipBot264v1.19.2\tools\x264\x264_x64.exe" --crf 18 --fps 24000/1001 --force-cfr --min-keyint 24 --keyint 240 --frames 512 --sar 1:1 --preset slower --stdin y4m --output "E:\Temp\RipBot264temp\video.264" -
error: KNLMeansCL: no compatible opencl platforms available!
(OpenCL 1.2 API)
(E:\Temp\RipBot264temp\job41\job41.avs, line 31)
y4m [error]: bad sequence header magic
x264 [error]: could not open input file `-'

[guest]

Basically the pc that it works using the GTX 760 card and the other does not work that uses the GTX650. But the strange thing is that the two video cards are 100% compatible with OpenCL 1.2 and at least theoretically should work.

Hey, up until a short time ago, I couldn't get my GTX650 to work, but since installing these :-

https://www.microsoft.com/en-US/download/details.aspx?id=40784

it does :)

I think it was the x86 version that did it, but they are small, so try what hopefully will work for you.

[guest]

I had tried the CPU did not work.
PC does not work GPU, the same message.
E:\>"C:\Programas\RipBot264v1.19.2\tools\avs2yuv\avs2yuv.exe" "E:\Temp\RipBot264temp\job16\job16.avs" -o - | "C:\Programas\RipBot264v1.19.2\tools\x264\x264_x64.exe" --crf 18 --fps 24000/1001 --force-cfr --min-keyint 24 --keyint 240 --frames 512 --sar 1:1 --preset slower --tune film --stdin y4m --output "E:\Temp\RipBot264temp\video.264" -
error: LoadPlugin: unable to load "C:\Programas\RipBot264v1.19.2\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll", Module not found. Install missing library?
(E:\Temp\RipBot264temp\job16\job16.avs, line 29)
y4m [error]: bad sequence header magic
x264 [error]: could not open input file `-'

PC running GPU the message changes.
E:\>"C:\Programas\RipBot264v1.19.2\tools\avs2yuv\avs2yuv.exe" "E:\Temp\RipBot264temp\job41\job41.avs" -o - | "C:\Programas\RipBot264v1.19.2\tools\x264\x264_x64.exe" --crf 18 --fps 24000/1001 --force-cfr --min-keyint 24 --keyint 240 --frames 512 --sar 1:1 --preset slower --stdin y4m --output "E:\Temp\RipBot264temp\video.264" -
error: KNLMeansCL: no compatible opencl platforms available!
(OpenCL 1.2 API)
(E:\Temp\RipBot264temp\job41\job41.avs, line 31)
y4m [error]: bad sequence header magic
x264 [error]: could not open input file `-'

It also seems that you need a CPU that supports OpenCL, and I think it's only the fairly new generation of Intel CPU's that do.

So what CPU's are you running ???

[mdchaser]

Remove --aq-strength 2 from your HEVC profile. That option was added as workaround for poor detail preservation in dark areas.
It is no longer needed for latest x265 version.

Thank you sir that did it! Encodes are now about 40% smaller than when using x264.

Do you think x265 has hit a point where it is "better" than x264 or does it still have a long way to go? I'm trying to decide on which codec to use since 99% of my viewing is done on a computer.

[soneca]

It also seems that you need a CPU that supports OpenCL, and I think it's only the fairly new generation of Intel CPU's that do.

So what CPU's are you running ???

I think any Intel that supports the SSE4.1 supports OpenCL.
My older processor(i7 980X) supports SSE4.2.

This version of Visual C++ is already installed.

[guest]

I think any Intel that supports the SSE4.1 supports OpenCL.
My older processor(i7 980X) supports SSE4.2.

This version of Visual C++ is already installed.

So to get the CPU to use open cl...there must be driver or something !?!?

So you still can't get your 650 to work, then ?? It got mine working.

[Wildfire]

OpenCL runs on your videocard, so if you have an add-on videocard it will run on that - if supported by the videocard. If you have an Intel CPU with integrated graphics which support OpenCL, the CPU videocard needs to be enabled.

[Atak_Snajpera]

So how come you chose to go down the GPU route ?
because CPU route is extremely sloooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooowwwwwwwwwwwwwwwwwwwwwwwwww.
FRAME SIZE: 1920x1080
CPU: Intel XEON E5-2690 2,9 GHz (8C/16T)
http://i.cubeupload.com/NVmAod.png

So to get the CPU to use open cl...there must be driver or something !?!?
It looks like that NVIDIA OpenCL platform does not see CPU as compatible OpenCL device. If you had AMD OpenCL platform installed you would get also this

C:\Users\Dave\Desktop\NVIDIA GPU Computing SDK\OpenCL\bin\Win32\Release\oclDeviceQuery.exe Starting...

OpenCL SW Info:

WARNING: NVIDIA OpenCL platform not found - defaulting to first platform!

CL_PLATFORM_NAME: AMD Accelerated Parallel Processing
CL_PLATFORM_VERSION: OpenCL 1.2 AMD-APP (937.2)
OpenCL SDK Revision: 7027912


OpenCL Device Info:

2 devices found supporting OpenCL:

---------------------------------
Device ATI RV770
---------------------------------
CL_DEVICE_NAME: ATI RV770
CL_DEVICE_VENDOR: Advanced Micro Devices, Inc.
CL_DRIVER_VERSION: CAL 1.4.1734
CL_DEVICE_VERSION: OpenCL 1.0 AMD-APP (937.2)
CL_DEVICE_TYPE: CL_DEVICE_TYPE_GPU
CL_DEVICE_MAX_COMPUTE_UNITS: 10
CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3
CL_DEVICE_MAX_WORK_ITEM_SIZES: 256 / 256 / 256
CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
CL_DEVICE_MAX_CLOCK_FREQUENCY: 625 MHz
CL_DEVICE_ADDRESS_BITS: 32
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 128 MByte
CL_DEVICE_GLOBAL_MEM_SIZE: 256 MByte
CL_DEVICE_ERROR_CORRECTION_SUPPORT: no
CL_DEVICE_LOCAL_MEM_TYPE: global
CL_DEVICE_LOCAL_MEM_SIZE: 16 KByte
CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 64 KByte
CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_PROFILING_ENABLE
CL_DEVICE_IMAGE_SUPPORT: 0
CL_DEVICE_MAX_READ_IMAGE_ARGS: 0
CL_DEVICE_MAX_WRITE_IMAGE_ARGS: 0
CL_DEVICE_SINGLE_FP_CONFIG: INF-quietNaNs round-to-nearest round-to-zero round-to-inf fma

CL_DEVICE_IMAGE <dim> 2D_MAX_WIDTH 0
2D_MAX_HEIGHT 0
3D_MAX_WIDTH 0
3D_MAX_HEIGHT 0
3D_MAX_DEPTH 0

CL_DEVICE_EXTENSIONS: cl_khr_fp64
cl_amd_fp64
cl_khr_gl_sharing
cl_amd_device_attribute_query
cl_khr_d3d10_sharing

CL_DEVICE_PREFERRED_VECTOR_WIDTH_<t> CHAR 16, SHORT 8, INT 4, LONG 2, FLOAT 4, DOUBLE 2


---------------------------------
Device Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
---------------------------------
CL_DEVICE_NAME: Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
CL_DEVICE_VENDOR: GenuineIntel
CL_DRIVER_VERSION: 2.0 (sse2,avx)
CL_DEVICE_VERSION: OpenCL 1.2 AMD-APP (937.2)
CL_DEVICE_OPENCL_C_VERSION: OpenCL C 1.2
CL_DEVICE_TYPE: CL_DEVICE_TYPE_CPU
CL_DEVICE_MAX_COMPUTE_UNITS: 16
CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3
CL_DEVICE_MAX_WORK_ITEM_SIZES: 1024 / 1024 / 1024
CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
CL_DEVICE_MAX_CLOCK_FREQUENCY: 2901 MHz
CL_DEVICE_ADDRESS_BITS: 32
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1024 MByte
CL_DEVICE_GLOBAL_MEM_SIZE: 2048 MByte
CL_DEVICE_ERROR_CORRECTION_SUPPORT: no
CL_DEVICE_LOCAL_MEM_TYPE: global
CL_DEVICE_LOCAL_MEM_SIZE: 32 KByte
CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 64 KByte
CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_PROFILING_ENABLE
CL_DEVICE_IMAGE_SUPPORT: 1
CL_DEVICE_MAX_READ_IMAGE_ARGS: 128
CL_DEVICE_MAX_WRITE_IMAGE_ARGS: 8
CL_DEVICE_SINGLE_FP_CONFIG: denorms INF-quietNaNs round-to-nearest round-to-zero round-to-inf fma

CL_DEVICE_IMAGE <dim> 2D_MAX_WIDTH 8192
2D_MAX_HEIGHT 8192
3D_MAX_WIDTH 2048
3D_MAX_HEIGHT 2048
3D_MAX_DEPTH 2048

CL_DEVICE_EXTENSIONS: cl_khr_fp64
cl_amd_fp64
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_khr_gl_sharing
cl_ext_device_fission
cl_amd_device_attribute_query
cl_amd_vec3
cl_amd_printf
cl_amd_media_ops
cl_amd_popcnt
cl_khr_d3d10_sharing

CL_DEVICE_PREFERRED_VECTOR_WIDTH_<t> CHAR 16, SHORT 8, INT 4, LONG 2, FLOAT 4, DOUBLE 0


---------------------------------
2D Image Formats Supported (80)
---------------------------------
# Channel Order Channel Type

1 CL_R CL_SNORM_INT8
2 CL_R CL_SNORM_INT16
3 CL_R CL_UNORM_INT8
4 CL_R CL_UNORM_INT16
5 CL_R CL_SIGNED_INT8
6 CL_R CL_SIGNED_INT16
7 CL_R CL_SIGNED_INT32
8 CL_R CL_UNSIGNED_INT8
9 CL_R CL_UNSIGNED_INT16
10 CL_R CL_UNSIGNED_INT32
11 CL_R CL_HALF_FLOAT
12 CL_R CL_FLOAT
13 CL_A CL_SNORM_INT8
14 CL_A CL_SNORM_INT16
15 CL_A CL_UNORM_INT8
16 CL_A CL_UNORM_INT16
17 CL_A CL_SIGNED_INT8
18 CL_A CL_SIGNED_INT16
19 CL_A CL_SIGNED_INT32
20 CL_A CL_UNSIGNED_INT8
21 CL_A CL_UNSIGNED_INT16
22 CL_A CL_UNSIGNED_INT32
23 CL_A CL_HALF_FLOAT
24 CL_A CL_FLOAT
25 CL_RG CL_SNORM_INT8
26 CL_RG CL_SNORM_INT16
27 CL_RG CL_UNORM_INT8
28 CL_RG CL_UNORM_INT16
29 CL_RG CL_SIGNED_INT8
30 CL_RG CL_SIGNED_INT16
31 CL_RG CL_SIGNED_INT32
32 CL_RG CL_UNSIGNED_INT8
33 CL_RG CL_UNSIGNED_INT16
34 CL_RG CL_UNSIGNED_INT32
35 CL_RG CL_HALF_FLOAT
36 CL_RG CL_FLOAT
37 CL_RGBA CL_SNORM_INT8
38 CL_RGBA CL_SNORM_INT16
39 CL_RGBA CL_UNORM_INT8
40 CL_RGBA CL_UNORM_INT16
41 CL_RGBA CL_SIGNED_INT8
42 CL_RGBA CL_SIGNED_INT16
43 CL_RGBA CL_SIGNED_INT32
44 CL_RGBA CL_UNSIGNED_INT8
45 CL_RGBA CL_UNSIGNED_INT16
46 CL_RGBA CL_UNSIGNED_INT32
47 CL_RGBA CL_HALF_FLOAT
48 CL_RGBA CL_FLOAT
49 CL_ARGB CL_SNORM_INT8
50 CL_ARGB CL_UNORM_INT8
51 CL_ARGB CL_SIGNED_INT8
52 CL_ARGB CL_UNSIGNED_INT8
53 CL_BGRA CL_SNORM_INT8
54 CL_BGRA CL_UNORM_INT8
55 CL_BGRA CL_SIGNED_INT8
56 CL_BGRA CL_UNSIGNED_INT8
57 CL_LUMINANCE CL_SNORM_INT8
58 CL_LUMINANCE CL_SNORM_INT16
59 CL_LUMINANCE CL_UNORM_INT8
60 CL_LUMINANCE CL_UNORM_INT16
61 CL_LUMINANCE CL_HALF_FLOAT
62 CL_LUMINANCE CL_FLOAT
63 CL_INTENSITY CL_SNORM_INT8
64 CL_INTENSITY CL_SNORM_INT16
65 CL_INTENSITY CL_UNORM_INT8
66 CL_INTENSITY CL_UNORM_INT16
67 CL_INTENSITY CL_HALF_FLOAT
68 CL_INTENSITY CL_FLOAT
69 CL_RA CL_SNORM_INT8
70 CL_RA CL_SNORM_INT16
71 CL_RA CL_UNORM_INT8
72 CL_RA CL_UNORM_INT16
73 CL_RA CL_SIGNED_INT8
74 CL_RA CL_SIGNED_INT16
75 CL_RA CL_SIGNED_INT32
76 CL_RA CL_UNSIGNED_INT8
77 CL_RA CL_UNSIGNED_INT16
78 CL_RA CL_UNSIGNED_INT32
79 CL_RA CL_HALF_FLOAT
80 CL_RA CL_FLOAT

---------------------------------
3D Image Formats Supported (80)
---------------------------------
# Channel Order Channel Type

1 CL_R CL_SNORM_INT8
2 CL_R CL_SNORM_INT16
3 CL_R CL_UNORM_INT8
4 CL_R CL_UNORM_INT16
5 CL_R CL_SIGNED_INT8
6 CL_R CL_SIGNED_INT16
7 CL_R CL_SIGNED_INT32
8 CL_R CL_UNSIGNED_INT8
9 CL_R CL_UNSIGNED_INT16
10 CL_R CL_UNSIGNED_INT32
11 CL_R CL_HALF_FLOAT
12 CL_R CL_FLOAT
13 CL_A CL_SNORM_INT8
14 CL_A CL_SNORM_INT16
15 CL_A CL_UNORM_INT8
16 CL_A CL_UNORM_INT16
17 CL_A CL_SIGNED_INT8
18 CL_A CL_SIGNED_INT16
19 CL_A CL_SIGNED_INT32
20 CL_A CL_UNSIGNED_INT8
21 CL_A CL_UNSIGNED_INT16
22 CL_A CL_UNSIGNED_INT32
23 CL_A CL_HALF_FLOAT
24 CL_A CL_FLOAT
25 CL_RG CL_SNORM_INT8
26 CL_RG CL_SNORM_INT16
27 CL_RG CL_UNORM_INT8
28 CL_RG CL_UNORM_INT16
29 CL_RG CL_SIGNED_INT8
30 CL_RG CL_SIGNED_INT16
31 CL_RG CL_SIGNED_INT32
32 CL_RG CL_UNSIGNED_INT8
33 CL_RG CL_UNSIGNED_INT16
34 CL_RG CL_UNSIGNED_INT32
35 CL_RG CL_HALF_FLOAT
36 CL_RG CL_FLOAT
37 CL_RGBA CL_SNORM_INT8
38 CL_RGBA CL_SNORM_INT16
39 CL_RGBA CL_UNORM_INT8
40 CL_RGBA CL_UNORM_INT16
41 CL_RGBA CL_SIGNED_INT8
42 CL_RGBA CL_SIGNED_INT16
43 CL_RGBA CL_SIGNED_INT32
44 CL_RGBA CL_UNSIGNED_INT8
45 CL_RGBA CL_UNSIGNED_INT16
46 CL_RGBA CL_UNSIGNED_INT32
47 CL_RGBA CL_HALF_FLOAT
48 CL_RGBA CL_FLOAT
49 CL_ARGB CL_SNORM_INT8
50 CL_ARGB CL_UNORM_INT8
51 CL_ARGB CL_SIGNED_INT8
52 CL_ARGB CL_UNSIGNED_INT8
53 CL_BGRA CL_SNORM_INT8
54 CL_BGRA CL_UNORM_INT8
55 CL_BGRA CL_SIGNED_INT8
56 CL_BGRA CL_UNSIGNED_INT8
57 CL_LUMINANCE CL_SNORM_INT8
58 CL_LUMINANCE CL_SNORM_INT16
59 CL_LUMINANCE CL_UNORM_INT8
60 CL_LUMINANCE CL_UNORM_INT16
61 CL_LUMINANCE CL_HALF_FLOAT
62 CL_LUMINANCE CL_FLOAT
63 CL_INTENSITY CL_SNORM_INT8
64 CL_INTENSITY CL_SNORM_INT16
65 CL_INTENSITY CL_UNORM_INT8
66 CL_INTENSITY CL_UNORM_INT16
67 CL_INTENSITY CL_HALF_FLOAT
68 CL_INTENSITY CL_FLOAT
69 CL_RA CL_SNORM_INT8
70 CL_RA CL_SNORM_INT16
71 CL_RA CL_UNORM_INT8
72 CL_RA CL_UNORM_INT16
73 CL_RA CL_SIGNED_INT8
74 CL_RA CL_SIGNED_INT16
75 CL_RA CL_SIGNED_INT32
76 CL_RA CL_UNSIGNED_INT8
77 CL_RA CL_UNSIGNED_INT16
78 CL_RA CL_UNSIGNED_INT32
79 CL_RA CL_HALF_FLOAT
80 CL_RA CL_FLOAT

oclDeviceQuery, Platform Name = AMD Accelerated Parallel Processing, Platform Version = OpenCL 1.2 AMD-APP (937.2), SDK Revision = 7027912, NumDevs = 2, Device = ATI RV770, Device = Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz

System Info:

Local Time/Date = 18:40:7, 2/3/2016
CPU Arch: 0
CPU Level: 6
# of CPU processors: 16
Windows Build: 7601
Windows Ver: 6.1 (Windows Vista / Windows 7)

[dv8r]

OpenCl on Nvidia cards is lacking. AMD has Opencl 2.0 and Nvidia seems to be stuck on 1.2. Nvidia would rather see CUDA prevail over opencl, so I wouldn't expect much from them. And it's with all apps. I've had just as much troubles with Adobe Premiere trying to use opencl and cuda. It's pretty new stuff. From reading up on it people seem to have much less hassle with AMD gpu's and Opencl. But even then you can run into issues with certain cards not being recognized etc.
Thanks for giving us the option to try gpu denoising Atak. Will figure it all out soon enough. There aren't many programs giving people the option at the moment. Handbrake uses CPU NLMeans and yes it is painfully slow. But I have seen some great quality and compression using it as well if you can bare the wait. You're on the bleeding edge lol. The quality with any CUDA based encoders suck bad. Theyre fast but terrible quality. Using OpenCl for denoising/scaling seems like a great way to speed things up and still use x264 and x265. Using Premiere and H.264 produces some terrible looking quality. Terrible compared to ripbot and HEVC or AVC. I still can't figure out why everyone writing an encoding app doesn't have distributed encoding. Glad you figured that out!!!

[guest]

OpenCl on Nvidia cards is lacking. AMD has Opencl 2.0 and Nvidia seems to be stuck on 1.2. Nvidia would rather see CUDA prevail over opencl, so I wouldn't expect much from them. And it's with all apps. I've had just as much troubles with Adobe Premiere trying to use opencl and cuda. It's pretty new stuff. From reading up on it people seem to have much less hassle with AMD gpu's and Opencl. But even then you can run into issues with certain cards not being recognized etc.
Thanks for giving us the option to try gpu denoising Atak. Will figure it all out soon enough. There aren't many programs giving people the option at the moment. Handbrake uses CPU NLMeans and yes it is painfully slow. But I have seen some great quality and compression using it as well if you can bare the wait. You're on the bleeding edge lol. The quality with any CUDA based encoders suck bad. Theyre fast but terrible quality. Using OpenCl for denoising/scaling seems like a great way to speed things up and still use x264 and x265. Using Premiere and H.264 produces some terrible looking quality. Terrible compared to ripbot and HEVC or AVC. I still can't figure out why everyone writing an encoding app doesn't have distributed encoding. Glad you figured that out!!!

Well said :)

[dv8r]

I got the same red message as you Burt about not finding the .dll file. I'm not chasing it down much because I'm using an old card which I suppose isn't supported. It is crazy that amd drivers say the card should be compatible but it's in the nlmeans readme that the older cards just aren't supported. One frustrating thing about opencl and cuda. So there's no reason for me to chase a ghost at this point. I'll upgrade cards soon enough and see how that goes. I've looked at the firepro cards because I need a shorter card for my nodes as they are thin desktops. Gonna have to find the lowest end firepro's/radeon that will be supported because of power requirements with these Dell power supplies. They don't give you many options when it comes to graphics cards. I have read that the professional cards are more catered for opencl type work than the radeon's. Radeons are more for gaming etc. Either way I'll let ya know what works for me when I get to that point. That's about all we can do is see what works and what doesn't. The good thing is you did get a newer card to work.

[dv8r]

Hey Atak I had a question about wake on Lan. I initially had it running (I thought) then it started not working so well. I have always inserted a MAC address with colons for seperators such as 1K:H7:K8:90 etc. After going thru my nodes meticulously and pulling bios batteries, triple checking settings in bios and for my network adapters I still couldn't get it working consistently. So I tried some other wake on lan apps for windows and they were all working as they should. They of course had scanned my network and got the MAC address on their own. I noticed the mac address in those apps were using a - for a seperator. I tried this and all seems to be working now. So for instance MAC address 1K-H7-K8-90-A1 etc. Now when the distributed encoding window displays my nodes awake as they should. I was curious if there was anyway to have the main machine query an offline node to start encoding every so often in case a node restarts during an encode. I'm not sure why this has happened several times to me where a node drops offline and doesn't restart during the encode. Thanks for any thoughts on this.

[dv8r]

Forgot to ask in the previous post, if there were a way to send Wake packets to a node when you click the ON button in DE window also. For if a node were to go into sleep mode it would wake when trying to turn it ON.

[dv8r]

So I decided to see why I was getting the error that ripbot couldn't find the knlmeancl.dll file. I eventually went and downloaded the older version of knlmeanscl from github and inserted it into my ripbot folder. The 64 bit version wouldn't work but ripbot sees the 32 bit version. So I got past that hurdle. I'm not sure why it won't see the knlmeanscl.dll file that is originally in the folder. Corrupted maybe or the wrong version?? I am running windows 10 64 bit. Now ripbot just says there isn't a opencl device. My card is old of course. Strange that my radeon control panel still says I have opencl 2.0 installed. I wish all this stuff could be backwards compatible. Not sure why it isn't.

[guest]

So I decided to see why I was getting the error that ripbot couldn't find the knlmeancl.dll file. I eventually went and downloaded the older version of knlmeanscl from github and inserted it into my ripbot folder. The 64 bit version wouldn't work but ripbot sees the 32 bit version. So I got past that hurdle. I'm not sure why it won't see the knlmeanscl.dll file that is originally in the folder. Corrupted maybe or the wrong version?? I am running windows 10 64 bit. Now ripbot just says there isn't a opencl device. My card is old of course. Strange that my radeon control panel still says I have opencl 2.0 installed. I wish all this stuff could be backwards compatible. Not sure why it isn't.

Hey, I tried the older version from github (v0.6.11 or whatever), copied (well basically what you did), and all I got was a different error message (on an nVidia card, Windows 8.1 & 10 x64)

What card are you trying to use ??

[dv8r]

I'm not really trying to use this old card, it's an hd5500. But I knew ripbot should at least see the .dll file because it was in the directory. The only file ripbot would see was the 32 bit .dll file. Then my error changed from not finding the .dll in my ripbot folder to not having a opencl device. Now I could at least run it on CPU if I wanted to but it is very slow. Before I got ripbot to see the .dll I couldn't change the script to CPU because it couldn't find the .dll for whatever reason.