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

[Atak_Snajpera]

Hardware decoding won't give you noticeable speed up because encoding process is a real bottleneck here. Basically decoding process is waiting for x264/x265 encoder.
Take a look a this example using software decoding
http://i.cubeupload.com/nPWuqQ.png

Source is VC-1 and encoding was done using veryslow preset. Decoding process consumes only ~3% of cpu time on Xeon E5-2690 2.9Ghz.

[jthekk2]

Hardware decoding won't give you noticeable speed up because encoding process is a real bottleneck here. Basically decoding process is waiting for x264/x265 encoder.Right, I understand that and MIGHT end up switching the indexing in my automated batch script to use FFMS/DGAVCIndex if that's what needed, but using DGDecodeNV + Ripbot without reindexing would be the ideal.

The main point I was trying to show, however, is that Ripbot doesn't handle previously indexed files properly. After further testing:

(1) If any AVS script loading any of FFMS2.dll, DGDecodeNV.dll or DGAVCDecode.dll and the video referenced is the appropriate file or index file (FFmpeg source for .mkv/DGSource for .dgi/AVCSource for .dga), Ripbot will encode the file locally and will not re-index the file.

(2) If the workaround from my first post is used (editing the ripbot automated avs script when the video file (.mkv with vc1/.mkv with vc1/.mkv with 264) itself is loaded into ripbot to import the avs script), the following occurs:
(A) FFMS: VC1 must be in MKV, otherwise local encoding. If in MKV, re-indexes with FFMS and encodes with distributed encoding using FFMS2 decoding and the OLD FFMSIndex file (the one referenced in the original AVS; I can only assume based on the avs scripts).
(B) DGDecodeNV: VC1 must be in MKV, otherwise local encoding. If in MKV, re-indexes with FFMS and encodes with distributed encoding using DGDecodeNV (got this working with server paths and checked the decoding method by using GPU-Z; GPU load went up during encode and also tested with a non-Nvidia GPU PC as a server which would not start its chunk of the encode as expected since it does not have nvcuvid.dll to do the actual decoding).
(C) DGAVCDecode: 264 must be in MKV, otherwise local encoding. If in MKV, re-indexes with DGAVCIndex and encodes with distributed encoding using the OLD DGAVCIndex file (the one referenced in the original AVS; I can only assume based on the avs scripts).

It seems odd that the workaround above produces the correct result in the end when all is said and done (distributed encoding with a preconfigured AVS script and pre-indexed MKV file using FFMS/DGAVCDecode/DGDecodeNV), but that the MKV has to be the file actually loaded into ripbot (VC1/264 only encode locally), the avs script within ripbot has to be changed (which takes time), and the file is re-indexed even though it doesn't use the index created by ripbot.

Possible Solutions:
- Allow distributed encoding with AVS scripts directly. This should remove the re-indexing problem as well as the need to put the files in MKVs, though this may require Ripbot to grab the path to the DGI/DGA/FFMSIndex files from the AVS script in order to calculate chunks.
- Allow DGI/DGA/FFMSIndex files as inputs. Doing should also look through the folder the files are loaded from and set the internal video script to match the AVS script with the same name as the index file. Loading in an index file as an input can also trigger a "flag" within Ripbot not to re-index the file but to instead look within the index that was inputted. This should also remove the requirement to have the file in an .mkv since the index files and avs files are the ones being loaded and analyzed and then piped into x264 (which can handle the index files as inputs).

If the reindexing issue above could be addressed, that would be awesome. Without reindexing and if the "copy to temp folder" can be replaced with a "move to temp folder" option, I would be able to incorporate Ripbot distributed encoding almost seamlessly into my automation scheme; I would simply have to pipe in the AVS scripts or Index files manually into Ripbot before letting the automation take over again (using a file watch of some sort for the outputs from Ripbot).

TL;DR:
(1) DGDecodeNV works in distributed encoding, but the file is reindexed with FFMS (vc1) or DGAVCIndex (264) before the encode even though DGDecodeNV is used. Possible solutions are allowing distributed encoding with avs files, or allow index files as inputs with flags to not reindex.
(2) Please create a toggle/option to move files to the TEMP folder instead of copy.

[deanoboxer]

getting an error from my client computer during distributed encoding
Socket Error # 10054
Connection reset by peer

And I can't stop the encode as it just brings up the error again. What could be causing it?

[Atak_Snajpera]

Firewall ? Probably something is blocking connection.

Connection reset by peer.

An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.


For testing purposes kill your firewall everywhere.

[ste8s]

I've included a screenshot of the window where it says no chapters. Should I show anything else? Thanks!

Bump.

[Atak_Snajpera]

Are you sure that you are working on correctly decrypted source?

[soneca]

Atak, what changes to version 1.19.3?

[guest]

Atak, what changes to version 1.19.3?

Yes, another disadvantage of the auto update process...no changelogs :(

[Wildfire]

A suggestion: perhaps RipBot264 could show a window with information about the update after it has updated. That way, we would know the changes in the update.

[ste8s]

I've been using RipBot successfully for many years now. However I recently got a new computer, and reinstalled everything. But now RipBot can't seem to rip anything. I've tried reinstalling, and all that. Alas.

When I "Add", select the .m2ts file as per usual, it shows the selected .mpls file, but says there are no chapters. If I hit "OK" anyway, I get the following error:

Exception EFOpenError in module RipBot264.exe at 000239F2....etc.

As a sanity check, I did try to rip this same file on my old computer, and it was ready to work normally. I can't imagine what I did differently with my new machine.

Help! :P

I'm using v1.19.3.

Any ideas? Is this a common issue? I don't know.

[guest]

As a sanity check, I did try to rip this same file on my old computer, and it was ready to work normally. I can't imagine what I did differently with my new machine.

What if you copied the files you ripped off the old pc, onto the new, and see if that works.

It does sound like it might be a "ripping" problem, what are you using ?

What differences are there between the 2 pc's ?

[ste8s]

What if you copied the files you ripped off the old pc, onto the new, and see if that works.

It does sound like it might be a "ripping" problem, what are you using ?

What differences are there between the 2 pc's ?

I'm using MakeMKV at the moment. It's possible that it's MakeMKV and not Ripbot, but I'm not completely sure. Perhaps an update to either of these programs has caused an issue?

About a year ago, I ripped a blu-ray from my library (Monsters Inc) using MakeMKV and Ripbot together. It worked great then. Today I re-ripped this same blu-ray with MakeMKV, and it seemed to be fine. However, Ripbot isn't showing chapters, video, audio, or subtitles in the "select stream" dialog.

All of that said, I did some more digging and found an old MakeMKV rip of a different blu-ray that I ripped about 5 months ago. Ripbot was able to work on it fine on my old computer, and it seems like it's working on my new computer as well.

Basically everything I ripped before September 2015 is working, and everything after isn't. Maybe it wasn't the computer switching, but a coincidental update? Or maybe I forgot to install something crucial? Lots of correlating here, but not a lot of causation.

[Atak_Snajpera]

When window pops-up go to temp folder and check what you have in following files

Blu-Ray_structure_info.txt
Blu-Ray_title1_info.txt

[ste8s]

When window pops-up go to temp folder and check what you have in following files

Blu-Ray_structure_info.txt
Blu-Ray_title1_info.txt

Blu-Ray_structure_info.txt says (beneath the command line stuff):

1) 00800.mpls, 00012.m2ts, 1:37:55
- Chapters, 16 chapters
- h264/AVC, 1080p24 /1.001 (16:9)
- DTS Master Audio, English, multi-channel, 48kHz

2) 00812.mpls, 0:20:14
[280+281+282+283].m2ts
- Chapters, 4 chapters
- h264/AVC, 1080p24 /1.001 (16:9)
- AC3, English, stereo, 48kHz


----

Blu-Ray_title_info.txt says (beneath the command line stuff):

The format of the source file could not be detected. <ERROR>

[guest]

I'm using MakeMKV at the moment. It's possible that it's MakeMKV and not Ripbot, but I'm not completely sure. Perhaps an update to either of these programs has caused an issue?

Well, when I ever need to rip a Bluray disc, I use AnyDVD HD, works a treat, and I generally rip them to a folder, then use Ripbot to do the rest.

[Atak_Snajpera]

ste8s
Like I said before most likely source was not correctly decrypted by makemkv.

[Atak_Snajpera]

Update 2016.02.04
Added: KNLMeansCL denoiser (requires GPU with OpenCL 1.2 support)
Changed: Levels (PC->TV and TV->PC) separated from colors section

[dv8r]

You're the man Atak, Thanks a ton for the addition of nlmeanscli. Greatly appreciated. Now I have no use for handbrake anymore as that was all I used it for.

[soneca]

Update 2016.02.04
Added: KNLMeansCL denoiser (requires GPU with OpenCL 1.2 support)
Changed: Levels (PC->TV and TV->PC) separated from colors section

Thank you!

[guest]

Update 2016.02.04
Added: KNLMeansCL denoiser (requires GPU with OpenCL 1.2 support)
Changed: Levels (PC->TV and TV->PC) separated from colors section

Thanks, should be interesting.

So, 2 more servers, next, please :)

[BigM]

When I enable "Use Auto-Update" I get the following error message:
'07.10.2015 17:34:06' is not a valid date and time

I think this might be caused by my European date-format. But the date shown is not the current date, it's a date in the past. Screenshot was taken today.

[Atak_Snajpera]

I do not see it.

[BigM]

I do not see it.

I suppose I located the problem:
When I change the parameter LastCheck= in updater.ini to a past date in another date format, the udpate works:
LastCheck=2016-01-01 12:12:12

[Atak_Snajpera]

great!

[BigM]

I will monitor this and have a look, if the date format switches again next update.

[guest]

Update 2016.02.04
Added: KNLMeansCL denoiser (requires GPU with OpenCL 1.2 support)

Hi Atak, does this denoiser support multiple GPU's, to speed up the process ??

eg:- 2 or more nVidia GTX 580's.

Will DE be utilized as much, as original denoiser is CPU based, and KNLMeansCL is GPU based !!!

Does OpenCL work better with AMD/ATI GPU's ??

Since writing this, I have seen your post on the KNLMeansCL forum, which maybe answering my question re GTX580's....might I need to use a lesser version of KNLMeansCL...eg:-v0.6.11.

From what I can see your "version" is the lastest, which may not support my range of ageing graphics cards :(, although I do have one pc with a GTX680 SOC

[Atak_Snajpera]

modern amd gpus are generally better with opencl than nvidias. AMD gpus support even OpenCL 2.1 while nvidia stuck in OpenCL 1.2. Please correct me if I'm wrong but sharing resources among (SHARED VIRTUAL MEMORY) gpus requires OpenCL 2.0 .

[guest]

modern amd gpus are generally better with opencl than nvidias. AMD gpus support even OpenCL 2.1 while nvidia stuck in OpenCL 1.2. Please correct me if I'm wrong but sharing resources among (SHARED VIRTUAL MEMORY) gpus requires OpenCL 2.0 .

OK, that's interesting, I guess I'll have to do some comparison testing.

So what denoiser will work better with DE ??

[Atak_Snajpera]

So what denoiser will work better with DE ??
CPU obviously because you do not have to worry whether GPU on some PC supports OpenCL 1.2 or not.

[guest]

CPU obviously because you do not have to worry whether GPU on some PC supports OpenCL 1.2 or not.

So, if you DID have other PCs with appropriate GPUs, then what ?

Sorry, but did you answer about multiple GPU's in one PC ??

[soneca]

Update 2016.02.04
Added: KNLMeansCL denoiser (requires GPU with OpenCL 1.2 support)
Changed: Levels (PC->TV and TV->PC) separated from colors section

After I updated the nvidia drivers on the PC with the GTX760 card and KNLMeansCL denoiser started to work, but on the other PC with GTX650 board the denoiser does not work even after the update.

E:\>"C:\Programas\RipBot264v1.19.2\tools\avs2yuv\avs2yuv.exe" "E:\Temp\RipBot264temp\job13\job13.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\job13\job13.avs, line 29)
y4m [error]: bad sequence header magic
x264 [error]: could not open input file `-'

[Atak_Snajpera]

make sure that OpenCL.dll is in C:\Windows\System32 and in C:\Windows\SysWOW64
Also make sure that GTX650 supports OpenCL 1.2
Use this tool -> http://developer.download.nvidia.com/compute/DevZone/OpenCL/Projects/oclDeviceQuery.zip
oclDeviceQuery.exe


Sorry, but did you answer about multiple GPU's in one PC ??
Requires OpenCL 2.0. NVIDIA cards support only 1.2. Check this http://developer.amd.com/community/blog/2014/10/24/opencl-2-shared-virtual-memory/

So, if you DID have other PCs with appropriate GPUs, then what ?
Then use what works best for you.

[guest]

make sure that OpenCL.dll is in C:\Windows\System32 and in C:\Windows\SysWOW64
Also make sure that GTX650 supports OpenCL 1.2
Use this tool -> http://developer.download.nvidia.com/compute/DevZone/OpenCL/Projects/oclDeviceQuery.zip
oclDeviceQuery.exe

Requires OpenCL 2.0. NVIDIA cards support only 1.2. Check this http://developer.amd.com/community/blog/2014/10/24/opencl-2-shared-virtual-memory/

Then use what works best for you.

OK, thanks, for answering that.

Is there a chance that a lower version of KNLMeansCL might be required for lower spec cards ? (only going on what I understood on the KNLMeansCL forum)

[soneca]

Thanks!
The GTX 650 supports OpenGL 1.2, confirmed.
Later when I return home I will check if the dll files are present.

[guest]

Since writing this, I have seen your post on the KNLMeansCL forum, which maybe answering my question re GTX580's....might I need to use a lesser version of KNLMeansCL...eg:-v0.6.11.


Have checked with "ocl query", and indeed my nVidia cards are v1.2, which means the version of KNLMeansCL you have incorporated into Ripbot doesn't support.

However, my AMD HD6850 cards are OpenCL 2.0 !!

How can I "downgrade" to v0.6.11, so that I have support ??

Also, how do I actually know that the denoiser is working ??

Sorry for all the stupid questions !!!!!

[soneca]

Files(OpenCL.dll) are there in Windows\System32 and Windows\SysWOW64 folder.

Log.

D:\Downloads\oclDeviceQuery\NVIDIA GPU Computing SDK\OpenCL\bin\Win32\Release\oclDeviceQuery.exe Starting...

OpenCL SW Info:

CL_PLATFORM_NAME: NVIDIA CUDA
CL_PLATFORM_VERSION: OpenCL 1.2 CUDA 8.0.10
OpenCL SDK Revision: 7027912


OpenCL Device Info:

1 devices found supporting OpenCL:

---------------------------------
Device GeForce GTX 650
---------------------------------
CL_DEVICE_NAME: GeForce GTX 650
CL_DEVICE_VENDOR: NVIDIA Corporation
CL_DRIVER_VERSION: 361.75
CL_DEVICE_VERSION: OpenCL 1.2 CUDA
CL_DEVICE_OPENCL_C_VERSION: OpenCL C 1.2
CL_DEVICE_TYPE: CL_DEVICE_TYPE_GPU
CL_DEVICE_MAX_COMPUTE_UNITS: 2
CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3
CL_DEVICE_MAX_WORK_ITEM_SIZES: 1024 / 1024 / 64
CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
CL_DEVICE_MAX_CLOCK_FREQUENCY: 1202 MHz
CL_DEVICE_ADDRESS_BITS: 32
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 256 MByte
CL_DEVICE_GLOBAL_MEM_SIZE: 1024 MByte
CL_DEVICE_ERROR_CORRECTION_SUPPORT: no
CL_DEVICE_LOCAL_MEM_TYPE: local
CL_DEVICE_LOCAL_MEM_SIZE: 48 KByte
CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 64 KByte
CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_OUT_OF_ORDER_EXEC_MODE_ENABLE
CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_PROFILING_ENABLE
CL_DEVICE_IMAGE_SUPPORT: 1
CL_DEVICE_MAX_READ_IMAGE_ARGS: 256
CL_DEVICE_MAX_WRITE_IMAGE_ARGS: 16
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 16384
2D_MAX_HEIGHT 16384
3D_MAX_WIDTH 4096
3D_MAX_HEIGHT 4096
3D_MAX_DEPTH 4096

CL_DEVICE_EXTENSIONS: 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
cl_khr_byte_addressable_store
cl_khr_icd
cl_khr_gl_sharing
cl_nv_compiler_options
cl_nv_device_attribute_query
cl_nv_pragma_unroll
cl_nv_d3d9_sharing
cl_nv_d3d10_sharing
cl_khr_d3d10_sharing
cl_nv_d3d11_sharing


CL_DEVICE_COMPUTE_CAPABILITY_NV: 3.0
NUMBER OF MULTIPROCESSORS: 2
NUMBER OF CUDA CORES: 384
CL_DEVICE_REGISTERS_PER_BLOCK_NV: 65536
CL_DEVICE_WARP_SIZE_NV: 32
CL_DEVICE_GPU_OVERLAP_NV: CL_TRUE
CL_DEVICE_KERNEL_EXEC_TIMEOUT_NV: CL_TRUE
CL_DEVICE_INTEGRATED_MEMORY_NV: CL_FALSE
CL_DEVICE_PREFERRED_VECTOR_WIDTH_<t> CHAR 1, SHORT 1, INT 1, LONG 1, FLOAT 1, DOUBLE 1


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

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

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

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

oclDeviceQuery, Platform Name = NVIDIA CUDA, Platform Version = OpenCL 1.2 CUDA 8.0.10, SDK Revision = 7027912, NumDevs = 1, Device = GeForce GTX 650

System Info:

Local Time/Date = 20:54:42, 2/7/2016
CPU Arch: 0
CPU Level: 6
# of CPU processors: 12
Windows Build: 7601
Windows Ver: 6.1 (Windows Vista / Windows 7)

[Atak_Snajpera]

Have checked with "ocl query", and indeed my nVidia cards are v1.2, which means the version of KNLMeansCL you have incorporated into Ripbot doesn't support.
Version you have in ripbot264 was designed for OpenCL 1.2 so it should work with your gfx card if oclDeviceQuery says that GPU has support for it . Older version 0.6.11 was for OpenCL 1.0.

Also, how do I actually know that the denoiser is working ??
Select denoiser, select denoising strength and click PREVIEW SCRIPT.

[guest]

Version you have in ripbot264 was designed for OpenCL 1.2 so it should work with your gfx card if oclDeviceQuery says that GPU has support for it . Older version 0.6.11 was for OpenCL 1.0.

Select denoiser, select denoising strength and click PREVIEW SCRIPT.

Thanks again, you're a patient man :)

[mdchaser]

This may not be specific to ripbot but has anyone noticed when doing x264/x265 encodes of the same movie using the same settings as a test that the x265 version actually comes out larger? Not what I was expecting and I think I'm missing something obvious here...

[guest]

This may not be specific to ripbot but has anyone noticed when doing x264/x265 encodes of the same movie using the same settings as a test that the x265 version actually comes out larger? Not what I was expecting and I think I'm missing something obvious here...

I have only done a few x265 encodes, but yes, I have noticed that some have come out about the same or larger. It must be a bitrate thing.

[mdchaser]

I have only done a few x265 encodes, but yes, I have noticed that some have come out about the same or larger. It must be a bitrate thing.

Oh good, at least I'm not going crazy... Do you know if you are at least getting better quality given the efficiency of x265? I wouldn't mind larger files if it also means better quality.

[dv8r]

I'm loving this program. I dreamed about an app like this forever ago. I picked up some cheap refurbished dell's off ebay with i5's and setup a 5 machine cluster so far. Everything is running great. Wake on LAN ran without a hitch. Actually impressed with the dell's. I can get the same fps out of them as an older dual Xeon (X5460) machine, and they run a lot cooler and quieter lol. This is much better than building a new machine with high dollar hardware, and it's faster. My bro just built a dual machine and it was high $$$. Ripbot is faster. I've been playing around some with the TV-PC and tweak settings a bit. HEVC is pretty nice now that it doesn't take forever and a day and I can actually get thru an encode without saying screw this. THANKS Atak!!! Now I need to add some opencl cards and see how good nlmeans looks. Anyone tried the nlmeans yet?

[guest]

... Do you know if you are at least getting better quality given the efficiency of x265? I wouldn't mind larger files if it also means better quality.

Unfortunately, I haven't got a really good way of viewing them on my Smart TV, other than via a pc, running PowerDVD.

I wish I had a TV that played HEVC natively :(

Having said that, it does look PRETTY good on a 27" Dell monitor.

Early days for me, with this.

[guest]

Now I need to add some opencl cards and see how good nlmeans looks. Anyone tried the nlmeans yet?

May I ask what cards you are thinking of getting ??

I have mainly nVidia cards due to the CUDA support for the other software I like to use......

And I dont think ATI/AMD & nVidia cards play nicely, if they are in the same pc :(

[Atak_Snajpera]

This may not be specific to ripbot but has anyone noticed when doing x264/x265 encodes of the same movie using the same settings as a test that the x265 version actually comes out larger? Not what I was expecting and I think I'm missing something obvious here...

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.

[guest]

Hi Atak,

I think I may have stumbled onto a bug.

When selecting KNLMeansCL, and x265 (10 bit), as soon as you select "Done" to save the job, the info.txt file disappears in that jobs "Job Folder", and as a result, it fails.

But when using HQDN3D, isn't a problem.

I've tested this on 2 very different pc's...same result :(

[Atak_Snajpera]

Does preview script work with enabled knlmeanscl?

[guest]

Does preview script work with enabled knlmeanscl?

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

Will check ASAP, and get back !!!!

[Atak_Snajpera]

If you do not check so how do you know that selected denoising strength is good ?!?! So basically you chose some random number without even checking how filtered frame looks like ?

[guest]

If you do not check so how do you know that selected denoising strength is good ?!?! So basically you chose some random number without even checking how filtered frame looks like ?

Well, my process is that I have been doing this for quite a while now, I just have a "feel" what setting (number) I need to use, to get the desired result, generally it's good, if not, I'll run it thru again...doesn't take that long, with the powerful pc's I have.

I preview what I am going to process first, using VLC, figure out what I think the noise level (which is about all I filter) is, and go from there :)

I generally do final color & volume adjustments with Premiere Pro CC.