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

[LigH]

Well, I might be wrong all the time ... if you know what to blame, you are lucky, I would agree that network re-routing software can be a probable reason.

[slalom]

That was some security scanning tool, got it disabled

Even LAN speed is faster now

[TR-9970X]

There has been yet another small auto update

It's only RipBot264.exe, haven't tested it, hopefully someone has.

[f0ns02003]

Hi,

First of all let me thank you for your great job and program, it's my favourite to do my encodes :)

I've a problem when muxing files once videoencoding is finished, it seems that it's broken for me with last version.
It doesn't mux anything, gives you an "ERROR" log, it says it coulnd't find video.265 (although it was there) and the delete the 265 file.

Anyone else?

I'm on a Windows11 single machine, and a looong queue previosuly created before update, it was working perfectly before last update.

Thanks!

[TR-9970X]

Hi,

First of all let me thank you for your great job and program, it's my favourite to do my encodes :)

I've a problem when muxing files once videoencoding is finished, it seems that it's broken for me with last version.
It doesn't mux anything, gives you an "ERROR" log, it says it couldn't find video.265 (although it was there) and the delete the 265 file.

Anyone else?

I'm on a Windows11 single machine, and a looong queue previously created before update, it was working perfectly before last update.

Thanks!

Did you read any of the recent posts ?, "we" have had some issues now for a few weeks, and Atak sent out an auto update, but that seemed to just create some other issues, similar to what you're commenting on...then Atak post another small update.

Are your errors anything like slalom posted (below) ?

Now unfortunately I haven't had a chance to test any of these, busy doing stuff with Handbrake.

Not many have left comments or feedback, which is a shame.

I noticed you also posted on www.videohelp.com, so it's good that came here, as well.

[f0ns02003]

Did you read any of the recent posts ?, "we" have had some issues now for a few weeks, and Atak sent out an auto update, but that seemed to just create some other issues, similar to what you're commenting on...then Atak post another small update.

Are your errors anything like slalom posted (below) ?

Now unfortunately I haven't had a chance to test any of these, busy doing stuff with Handbrake.

Not many have left comments or feedback, which is a shame.

I noticed you also posted on www.videohelp.com, so it's good that came here, as well.

Eeemmm sorry, I reviewed lasts posts since the last update, not previous ones.

I update from time to time as the encoding machine is 24/7 working and I reviewed lasts posts since the last update (1.27.5 (August 2, 2025) according to videohelp, 10 days ago) specially when I read "Fixed: detection when mkv muxing fails", so I was surprised that was this what's failing.

I don't mind to execute manually the .cmds to process audio and mux, but the main problem is that it's deleting the 265 file that took hours to process!!

So, excuse-me, I thought I was the only one having this kind of problems as lasts posts since the last update are about distributed encoding :eek:

[slalom]

I don't mind to execute manually the .cmds to process audio and mux, but the main problem is that it's deleting the 265 file that took hours to process!!

So, excuse-me, I thought I was the only one having this kind of problems as lasts posts since the last update are about distributed encoding :eek:
Run jobmuxfiles.cmd to re-create the file. I'm not sure about the name, you will find it :)

[chainring]

job<job#>_MuxFiles.cmd

Just finished seven 4K movies, utilizing DE mode with six servers and no hiccups. Another two 4K movies are processing and no problems there, either.

[f0ns02003]

Run jobmuxfiles.cmd to re-create the file. I'm not sure about the name, you will find it :)

job<job#>_MuxFiles.cmd

Just finished seven 4K movies, utilizing DE mode with six servers and no hiccups. Another two 4K movies are processing and no problems there, either.

I already know it:

I don't mind to execute manually the .cmds to process audio and mux

In fact I run my own batch of cmds to run several of them in parallel (different videos) to take profit of an 32 threads cpu (otherwise it runs at about 30-40% of max processing power).

I solved this issue going back to 1.27.4 and disabling updates atm.

Thanks anyway!

[rlev11]

Since updating to the latest version, I have not seen any issues EXCEPT I still have the same issue of the encodingclient dropping out in the middle of an encode periodically. Turning off auto updates and copying back in version 1.18.3 of the encodingclient.exe as before solves the issue and I am able to run long batch encodes (24+ hours) without any issues.

[TR-9970X]

Since updating to the latest version, I have not seen any issues EXCEPT I still have the same issue of the encodingclient dropping out in the middle of an encode periodically. Turning off auto updates and copying back in version 1.18.3 of the encodingclient.exe as before solves the issue and I am able to run long batch encodes (24+ hours) without any issues.

I'm glad you've commented on this again...

I have to say that I haven't had the opportunity to test the latest, some say it's now OK, other's are not convinced, and like yourself, if the client is still randomly "disappearing", we don't need that !!!!

So one question, are you now running the very latest auto updated 1.27.5, but using 1.18.3 client ??

[Wishbringer]

@rlev11:
On the other hand,
i had some week long encodings with three clients (several x265 very slow UHD movie encodes in a row) with win 11 25h2 inside builds and no problems, no drops.
Only clean windows install, except prerequesits for RB nothing other tools installed.
Using clean RB, fresh update to 1.27.5 but with latest x265 build.
So maybe some hickups with other tools installed?

[rlev11]

I'm glad you've commented on this again...

I have to say that I haven't had the opportunity to test the latest, some say it's now OK, other's are not convinced, and like yourself, if the client is still randomly "disappearing", we don't need that !!!!

So one question, are you now running the very latest auto updated 1.27.5, but using 1.18.3 client ??

Yes, Auto Update to the latest, then turn off auto updates, and copy 1.18.3 back into the folder

[rlev11]

@rlev11:
On the other hand,
i had some week long encodings with three clients (several x265 very slow UHD movie encodes in a row) with win 11 25h2 inside builds and no problems, no drops.
Only clean windows install, except prerequesits for RB nothing other tools installed.
Using clean RB, fresh update to 1.27.5 but with latest x265 build.
So maybe some hickups with other tools installed?


That's really good to know. I always get a drop out within a few hours. I am not discounting the possibility there there is "something else" that is causing this issue, just have no idea best way to troubleshoot what the cause is.
Next step will probably be to spin up one of my older boxes and load fresh install on it with nothing else, then use that as a client only PC and see what happens.

[TR-9970X]

That's really good to know. I always get a drop out within a few hours. I am not discounting the possibility there there is "something else" that is causing this issue, just have no idea best way to troubleshoot what the cause is.
Next step will probably be to spin up one of my older boxes and load fresh install on it with nothing else, then use that as a client only PC and see what happens.

I'm sort of going with the "something else"...

I wasn't having any issues several weeks ago, and it was only when the 13900KF was in the DE mix. but then it started happening with a couple of other PC's.

I hadn't changed anything significant with RB, the ONLY thing that was regularly happening was Windows updates, but I can't pinpoint when or what :(

The saga continues....

UPDATE:- First opportunity to give the fully updated RB a good run today, approx 6 hours without a hiccup between the 9950X3D & 7950X.

Also first run with my optimised AVX512 build, including the brand new FFMPEG 8.0 :)

[Juha]

I have an issue with a specific movie. Mediainfo says it's interlaced, but Ripbot doesn't consider it interlaced, thus not allowing to deinterlace it. Can someone check this?:

https://www.mediafire.com/file/avb9aw0li6uba5y/VOGTER_clip.mkv/file

[LigH]

MediaInfo only reports that the encoder was set up to use interlaced encoding. It doesn't check if there is really any temporal progress between the fields in the same frame.

On a Blu-ray disc, for some combinations of resolution and frame rate it is mandatory to set the encoder to interlaced mode, no matter the video content. That was one reason to implement the "fake interlaced" mode in x264's MBAFF algorithm: It reports that interlaced macroblocks might occur, but will encode all macroblocks in progressive mode.

[Atak_Snajpera]

I have an issue with a specific movie. Mediainfo says it's interlaced, but Ripbot doesn't consider it interlaced, thus not allowing to deinterlace it. Can someone check this?:

https://www.mediafire.com/file/avb9aw0li6uba5y/VOGTER_clip.mkv/file

Remux that file in mkvtoolnix and set proper FPS value to 25
Video file does not require deinterlacing. It is just a regular 1080p25 content.

[Juha]

Ok, thanks

[SquallMX]

Can you add support for ProRes 4:2:2?, I'm getting a error when encoding ProRes 4:2:2 files to x265, I need to add "-pix_fmt yuv420p10le" manually to "jobX_EncodeVideoPass1.cmd" and it gets deleted each time I edit settings using the main window.

[TR-9970X]

Can you add support for ProRes 4:2:2?, I'm getting a error when encoding ProRes 4:2:2 files to x265, I need to add "-pix_fmt yuv420p10le" manually to "jobX_EncodeVideoPass1.cmd" and it gets deleted each time I edit settings using the main window.

If I recall correctly, I think you can encode 4:2:2 with a particular command in the x265 profile...

I don't have any to check it.

[LigH]

If I recall correctly, I think you can encode 4:2:2 with a particular command in the x265 profile...

See: https://x265.readthedocs.io/en/master/cli.html#profile-level-tier

For x265, there is e.g. the profile main422-10.

And x264 has a similar profile high422.

[TR-9970X]

See: https://x265.readthedocs.io/en/master/cli.html#profile-level-tier

For x265, there is e.g. the profile main422-10.

And x264 has a similar profile high422.

Interesting.

I wonder if its changed since I tried it last (older x265, years ago), I recall you basically only needed to remove any "main" commands.

[LigH]

Due to a lack of personal experience in this corner, I will not say that x265 is certainly unable to auto-detect a required profile. It may be able. If not, you now know that you can manually specify it.

It may be important to know that 4:2:2 profiles only seem to exist for higher bit depths (10, 12).

[TR-9970X]

Due to a lack of personal experience in this corner, I will not say that x265 is certainly unable to auto-detect a required profile. It may be able. If not, you now know that you can manually specify it.

It may be important to know that 4:2:2 profiles only seem to exist for higher bit depths (10, 12).

Yes, it definitely isn't auto detect....a custom command line IS required :)

[muratkoc]

I have a setting with megui.which I can add a code to I would like to include it in the great how can I convert this setting

program --crf xxxx --threads 6 --deblock -3:-3 --bframes 5 --b-adapt 2 --ref 5 --merange 32 --me umh --no-fast-pskip --output "output" "input"

[TR-9970X]

I have a setting with megui.which I can add a code to I would like to include it in the great how can I convert this setting

program --crf xxxx --threads 6 --deblock -3:-3 --bframes 5 --b-adapt 2 --ref 5 --merange 32 --me umh --no-fast-pskip --output "output" "input"

Looks like these are x264 commands.

Some of those command option's could probably be set elsewhere in the app, but I would suggest creating a custom x264 command to use within RipBot, and see what you get !!

Look in the "Profiles" folder, then under "avc" folder for "examples"

[muratkoc]

https://i.postimg.cc/htZYdLwf/MG-3230.png,

Hallo thanks for the answer. Yes, there are examples, but the commands in there are a bit different than what I've always used with megui up to now. These are the settings, or rather, these are the settings I use for Enco for MKV, and I tried to include a few settings. But somehow the commands don't work, so my question was, is there anyone out there who knows something about these settings and can put together something similar to these values? It's simply about the settings, better picture, higher bitrate, and so on.

[TR-9970X]

Hallo thanks for the answer. Yes, there are examples, but the commands in there are a bit different than what I've always used with megui up to now. These are the settings, or rather, these are the settings I use for Enco for MKV, and I tried to include a few settings. But somehow the commands don't work, so my question was, is there anyone out there who knows something about these settings and can put together something similar to these values? It's simply about the settings, better picture, higher bitrate, and so on.

Have you used Ripbot much ??

I haven't bothered with MeGUI, but with a little "practice", you should get the results you're after with RB.

[chainring]

I'm bringing back an old post from a different user that wasn't addressed and the same problem is throwing me for a loop.

https://forum.doom9.org/showpost.php?p=1925161&postcount=18702

I have stumbled upon an hevc stream ripbot seems to have massive problems with, two notable problems:
- It seems to have problems decoding it in the first way: Auto cropping does not work with the message :" 'INF' is not a valid floating point value ", setting cropp left and right to 1000 and it can not generate a preview, no matter how often I press new frame.
I've seen that before, and worked around it by analyzing it in a different software and then just punching in the numbers manually.
-Additionally, and this is first for me: When trying to encode, not matter the settings, distributed or single machine encoding and the target codec, at exactly the time it fails. The fps goes up, the bitrate goes way way down, and the cpu consumptino goes down to, on all machines that are participating. When done in in DE mode, the later chunks are just very small and are only black, and if mixed together the video just stalls at the last good frame. The Original Video play back fine on all sorts of players and machines.

The movies I'm having trouble with are 4K releases of "The Crow (1994)" and "Freddy's Dead: The Final Nightmare (1991)". Those are the most recent I recall. Coincidence they're both old movies?

I've ripped and re-ripped both movies. Both discs play fine. The remuxes generated by MakeMKV play fine.

Cropping on The Crow works as expected. However, whether DE mode or single server mode is used, the resulting file doesn't play properly. The one from DE has a failure point at exactly the same time (or super close) no matter how many times I've tried encoding it. At the point in question, the video goes black while the audio still plays. I've turned off DE mode and encoded in regular mode; the end result is audio greatly out of sync with video.

On Freddy's Dead: The Final Nightmare (1991), I've only tried encoding in DE mode so far and it exhibits the cropping error and the entire movie encodes at a super low bitrate (less than 1Mbps), resulting in blank/black video.

[Atak_Snajpera]

have you tried updating LSMASH source
https://github.com/HomeOfAviSynthPlusEvolution/L-SMASH-Works/releases

Included version in ripbot264 is 5 years old so it may contain some bugs.

[TR-9970X]

Included version in ripbot264 is 5 years old so it may contain some bugs.

Well, who's fault is that :o

Might be time to do a refresh, and update some stuff that's still relevant, and remove old stuff that isn't.

[Atak_Snajpera]

if it ain't broken, don't fix it

[chainring]

No go after updating to the latest L-SMASH source from the link you provided. Not only did it not help with the problem I'm having, it's also really slow during indexing. I haven't timed the difference, but it's very noticeable. I'll try earlier versions and report back.

[TR-9970X]

No GPU listed in the OpenCL window.

I was setting up RB on my new build, and to my surprise, my new Gigabyte RTX 5070Ti, was NOT displayed. there was NOTHING ! :eek:

However, on another PC with an RTX 4080 Super, everything was displayed as it should.

Would the 5070Ti be "too new" for whatever RB uses to detect the GPU's ?? :confused::confused:

Latest drivers.

[Wishbringer]

Didn't drop NVidia OpenCL for 32bit on 50x0 Series?
There were some other issues with those cards (PhysX dropped, problems with CUDA).
So maybe another driver "feature" issue from NVidia

[TR-9970X]

Didn't drop NVidia OpenCL for 32bit on 50x0 Series?
There were some other issues with those cards (PhysX dropped, problems with CUDA).
So maybe another driver "feature" issue from NVidia

Thanks...

Maybe I should try older or newer driver....

[Wishbringer]

If it is a "feature", then all drivers will have same problem.
I don't know, if RB check per 32bit or per 64bit.
In past RB was hybrid with some 32 and some 64 bit tools.
Don't know actual state.

[TR-9970X]

If it is a "feature", then all drivers will have same problem.
I don't know, if RB check per 32bit or per 64bit.
In past RB was hybrid with some 32 and some 64 bit tools.
Don't know actual state.

I downloaded the very latest driver, but yet to test.

It must be something to do with the 5070, 'cause I'm using the same driver package on my 4080 Super, with no issue.

Hopefully Atak will comment.

Cheers.

[Wishbringer]

Didn't drop NVidia OpenCL for 32bit on 50x0 Series?
said so

[TR-9970X]

said so

Well, it's something that Atak will have to address then.

I'm sure I won't be the only user that has 5000 + series cards.

[Atak_Snajpera]

Didn't drop NVidia OpenCL for 32bit on 50x0 Series?
There were some other issues with those cards (PhysX dropped, problems with CUDA).
So maybe another driver "feature" issue from NVidia

You might be right. My tool OpenCLinfo.exe was compiled as Win32 instead of x64. That would explain why It does not detect 32 bit opencl driver on latest nvidia gpus.

[Atak_Snajpera]

Here is a source for OpenCLinfo.exe. Something broke on my ancient Microsoft Visual Studio 2013 and I can't even compile it anymore. (bunch of weird errors I haven't seen before)


// OpenCLdevices.cpp : Defines the entry point for the console application.
//

#include "stdafx.h"
#include <stdio.h>
#include <stdlib.h>
#ifdef __APPLE__
#include <OpenCL/opencl.h>
#else
#include <CL/cl.h>
#endif

#include <cstring>

int _tmain(int argc, _TCHAR* argv[])
{
cl_uint i, j;
char* info;
char* value;
cl_device_type devicetype = NULL;
size_t infoSize;
size_t valueSize;
cl_uint platformCount;
cl_uint deviceCount;
cl_platform_id *platforms;
cl_device_id* devices;
cl_uint maxComputeUnits;
const char* attributeNames[5] = { "Name", "Vendor",
"Version", "Profile", "Extensions" };
const cl_platform_info attributeTypes[5] = { CL_PLATFORM_NAME, CL_PLATFORM_VENDOR,
CL_PLATFORM_VERSION, CL_PLATFORM_PROFILE, CL_PLATFORM_EXTENSIONS };
const int attributeCount = sizeof(attributeNames) / sizeof(char*);


if (argc > 1)
{
if (!strcmp(argv[1], "/gpu"))
{
devicetype = CL_DEVICE_TYPE_GPU;
}
else
if (!strcmp(argv[1], "/cpu"))
{
devicetype = CL_DEVICE_TYPE_CPU;
}
else devicetype = CL_DEVICE_TYPE_ALL;
}
else
{
devicetype = CL_DEVICE_TYPE_ALL;
}



// get platform count
clGetPlatformIDs(5, NULL, &platformCount);

// get all platforms
platforms = (cl_platform_id*)malloc(sizeof(cl_platform_id)* platformCount);
clGetPlatformIDs(platformCount, platforms, NULL);

// for each platform print all attributes
for (i = 0; i < platformCount; i++) {

printf("\nPlatform %d. \n", i );

for (j = 0; j < attributeCount; j++) {

// get platform attribute value size
clGetPlatformInfo(platforms[i], attributeTypes[j], 0, NULL, &infoSize);
info = (char*)malloc(infoSize);

// get platform attribute value
clGetPlatformInfo(platforms[i], attributeTypes[j], infoSize, info, NULL);

printf(" %-11s : %s \n", attributeNames[j], info);
free(info);

}


}

printf("\n");

free(platforms);



// get all platforms
clGetPlatformIDs(0, NULL, &platformCount);
platforms = (cl_platform_id*)malloc(sizeof(cl_platform_id)* platformCount);
clGetPlatformIDs(platformCount, platforms, NULL);

for (i = 0; i < platformCount; i++) {

// get all devices
clGetDeviceIDs(platforms[i], devicetype, 0, NULL, &deviceCount);
devices = (cl_device_id*)malloc(sizeof(cl_device_id)* deviceCount);
clGetDeviceIDs(platforms[i], devicetype, deviceCount, devices, NULL);

// for each device print critical attributes
for (j = 0; j < deviceCount; j++) {

// print device name
clGetDeviceInfo(devices[j], CL_DEVICE_NAME, 0, NULL, &valueSize);
value = (char*)malloc(valueSize);
clGetDeviceInfo(devices[j], CL_DEVICE_NAME, valueSize, value, NULL);
printf("%d.%d Device name : %s \n", i , j , value);
free(value);


// print hardware device version
clGetDeviceInfo(devices[j], CL_DEVICE_VERSION, 0, NULL, &valueSize);
value = (char*)malloc(valueSize);
clGetDeviceInfo(devices[j], CL_DEVICE_VERSION, valueSize, value, NULL);
printf(" Hardware version : %s \n", value);
free(value);

// print software driver version
clGetDeviceInfo(devices[j], CL_DRIVER_VERSION, 0, NULL, &valueSize);
value = (char*)malloc(valueSize);
clGetDeviceInfo(devices[j], CL_DRIVER_VERSION, valueSize, value, NULL);
printf(" Software version : %s \n", value);
free(value);

// print c version supported by compiler for device
clGetDeviceInfo(devices[j], CL_DEVICE_OPENCL_C_VERSION, 0, NULL, &valueSize);
value = (char*)malloc(valueSize);
clGetDeviceInfo(devices[j], CL_DEVICE_OPENCL_C_VERSION, valueSize, value, NULL);
printf(" OpenCL C version : %s \n", value);
free(value);

// print parallel compute units
clGetDeviceInfo(devices[j], CL_DEVICE_MAX_COMPUTE_UNITS,
sizeof(maxComputeUnits), &maxComputeUnits, NULL);
printf(" Compute units : %d \n", maxComputeUnits);

printf("\n");
}

free(devices);

}

free(platforms);
//getchar();
return 0;
}

[LigH]

Maybe, maybe ... try to define a lower C++ language era?

[Atak_Snajpera]

I've managed to fix Win32 version and it compiles again in Visual Studio 2013. However my x64 still is misconfigured and throws bunch of errors.

[TR-9970X]

OpenCL support for nVidia RTX 5000 series Graphics Cards:-

@Wishbringer & @Atak,

I did a fair bit of "research" and discovered that 32bit OpenCL support has indeed been dropped with the latest 58x.xx drivers, and as a result, RB can't display any info on the card under the OpenCL tab :(

However, after a bit more digging I then discovered that it IS still supported in 57x.xx drivers, so I downloaded the last of the 57x.xx series, which is 577.00.

I just installed it, and just like magic, the info is all there under the OpenCL tab :)

So if anybody else has this issue, this is the "workaround", until Atak can figure out how to compile an x64 OpenCLinfo.exe.

Ironic isn't it...."if it ain't broken, don't fix it".

[Viper714]

Thanks.

When using tonemap, the end result is quite similar on my end, compared to yours:
https://images2.imgbox.com/c3/72/b22ErA4X_o.png

Interestingly, that original clip looks quite different on my end, compared to you:
https://images2.imgbox.com/24/fa/P6d7NMo1_o.png

Maybe Media Player Classic / K-Lite codec pack does some tweaks to the 4K HDR video...

Anyway, as I have major share of my movies in 1080p SDR, I want to rip my 4K movies to look exactly like them because I have used to the brighter image :p

Though, that one particular scene does look fine, I admit. But I still don't like the overall look of BT2446 in other movies so I guess I'll need to do some setting tweaking.

Juha,
Did you find a solution to the dark-rendered movies?

I have been ripping & encoding Blu-ray (1080P) with RipBot for quite a long time. I started doing this with 4K movies and noticed the same dark tone in ALL of them compared to my 1080 encodes. I've had to adjust my TV settings to lighten up 4K movies, then change them again for 1080P movies. Really annoying. Would prefer a consistent setting for all versions.

I would appreciate it if you could share any settings, including your CQ mode value.

Again, I really appreciate any help you can provide.

[hardkhora]

For RipBot, there is the option to start with Windows... Is there an option to start encoding if there are items in the Queue that I'm missing?

Asking because what is happening is while encoding I get random reboots now and then (hard to predict) so my computer could sit for days if I don't check in every hour to see if it is still running.
-I noticed I get way more reboots when this particular computer is the "Server" (does the queue management/encoding client), rather than just being a node.
*So, I know the best thing is to figure out how to get it to reboot less but that still won't help the issue of needing to check in to see if jobs are pause because of a reboot.

[Atak_Snajpera]

For RipBot, there is the option to start with Windows... Is there an option to start encoding if there are items in the Queue that I'm missing?

Asking because what is happening is while encoding I get random reboots now and then (hard to predict) so my computer could sit for days if I don't check in every hour to see if it is still running.
-I noticed I get way more reboots when this particular computer is the "Server" (does the queue management/encoding client), rather than just being a node.
*So, I know the best thing is to figure out how to get it to reboot less but that still won't help the issue of needing to check in to see if jobs are pause because of a reboot.

maybe your power supply is dying? Check eventlog in windows
https://www.tenforums.com/tutorials/78335-read-shutdown-logs-event-viewer-windows.html

try also this command line
RipBot264.exe /start

[ReinerSchweinlin]

@Atak

I just encountered a small bug:

When encoding some DVD footage, that is put into an MKV Container, the Display ratio gets messed up as soon as the video is cropped. For example: A 16:9 movie stored in MPEG2 with black bars is usually stretched when played back - encoding it with ripbot without removing the black bars works fine - but when cropping is done, the aspect ratio gets messed up on the final file.