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

[Atak_Snajpera]

Is there a way to excluded specific CPU cores? I have a 5900X and core 21 is very flaky under load. Before I look into the BIOS to make any changes I was wondering if I can do this in software.

Than you, Archie

1) open notepad
2) write (make sure that path to ripbot264.exe is correct)

start /affinity 1 "c:\ripbot264.exe"
3) save as RipBot264.cmd

Run RipBot264.cmd

affinity mask works like this (example for 4 core cpu)

You count cores from right to left
4321

0101 = means select core 1 and 3
1010 = means select core 2 and 4

Then you have to convert that binary value to hex value so 0101 becomes 5 (/affinity 5) and 1010 becomes A (/affinity A)

Keep in mind that you have SMT so you will have to disable also core 20 because
Core 0 -> Physical CORE0
Core 1 -> Physical CORE0
Core 2 -> Physical CORE1
Core 3 -> Physical CORE1
Core 4 -> Physical CORE2
Core 5 -> Physical CORE2
Core 6 -> Physical CORE3
Core 7 -> Physical CORE3
Core 8 -> Physical CORE4
Core 9 -> Physical CORE4
Core 10 -> Physical CORE5
Core 11 -> Physical CORE5
Core 12 -> Physical CORE6
Core 13 -> Physical CORE6
Core 14 -> Physical CORE7
Core 15 -> Physical CORE7
Core 16 -> Physical CORE8
Core 17 -> Physical CORE8
Core 18 -> Physical CORE9
Core 19 -> Physical CORE9
Core 20 -> Physical CORE10
Core 21 -> Physical CORE10
Core 22 -> Physical CORE11
Core 23 -> Physical CORE11

[archiel]

Might help...

https://poweradm.com/set-cpu-affinity-powershell/

or

https://bitsum.com/tools/cpu-affinity-calculator/

Thank you.

[archiel]

1) open notepad
2) write (make sure that path to ripbot264.exe is correct)

start /affinity 1 "c:\ripbot264.exe"
3) save as RipBot264.cmd

Run RipBot264.cmd

affinity mask works like this (example for 4 core cpu)

You count cores from right to left
4321

0101 = means select core 1 and 3
1010 = means select core 2 and 4

Then you have to convert that binary value to hex value so 0101 becomes 5 (/affinity 5) and 1010 becomes A (/affinity A)

Keep in mind that you have SMT so you will have to disable also core 20 because
Core 0 -> Physical CORE0
Core 1 -> Physical CORE0
Core 2 -> Physical CORE1
Core 3 -> Physical CORE1
Core 4 -> Physical CORE2
Core 5 -> Physical CORE2
Core 6 -> Physical CORE3
Core 7 -> Physical CORE3
Core 8 -> Physical CORE4
Core 9 -> Physical CORE4
Core 10 -> Physical CORE5
Core 11 -> Physical CORE5
Core 12 -> Physical CORE6
Core 13 -> Physical CORE6
Core 14 -> Physical CORE7
Core 15 -> Physical CORE7
Core 16 -> Physical CORE8
Core 17 -> Physical CORE8
Core 18 -> Physical CORE9
Core 19 -> Physical CORE9
Core 20 -> Physical CORE10
Core 21 -> Physical CORE10
Core 22 -> Physical CORE11
Core 23 -> Physical CORE11

Thank you

[archiel]

Crop Question

I have a mkv file (h265) 2962x2160. I want to crop to 2960x2160 (dimensions divisible by 8) but if I set crop values of left=1 right =1, the output is cropped by 2 pixels from each side and ends up as 2958x2160. What am I misssing?

[LigH]

If you have video with chroma subsampling (YUV 4:2:0 ~ YV12 is most common), you are only allowed to crop in the resolution of the chroma samples, which may be only each 2 pixels in luma. This may be circumvented by converting to YUV 4:4:4 ~ YV24. But I am not sure how RipBot264 can handle that...

[TR-9970X]

Crop Question

I have a mkv file (h265) 2962x2160. I want to crop to 2960x2160 (dimensions divisible by 8) but if I set crop values of left=1 right =1, the output is cropped by 2 pixels from each side and ends up as 2958x2160. What am I misssing?

I have been using (not exactly) this script on hundreds of jobs:_

#Custom
LoadPlugin("%AVISYNTHPLUGINS%\ColorMatrix\ColorMatrix64.dll")
LoadPlugin("%AVISYNTHPLUGINS%\Plugins_JPSDR\Plugins_JPSDR.dll")
Import("%AVISYNTHPLUGINS%\Scripts\AutoBorders.avs")
video=Spline64ResizeMT(video,2690,2160)
video=AutoBorders(video,16.0/9.0)

Might work for you.

You could also just edit the script that RB creates (which is basically the script I've shown).

But 2 pixels !!!!!

[archiel]

I have been using (not exactly) this script on hundreds of jobs:_

#Custom
LoadPlugin("%AVISYNTHPLUGINS%\ColorMatrix\ColorMatrix64.dll")
LoadPlugin("%AVISYNTHPLUGINS%\Plugins_JPSDR\Plugins_JPSDR.dll")
Import("%AVISYNTHPLUGINS%\Scripts\AutoBorders.avs")
video=Spline64ResizeMT(video,2690,2160)
video=AutoBorders(video,16.0/9.0)

Might work for you.

You could also just edit the script that RB creates (which is basically the script I've shown).

But 2 pixels !!!!!

Thanks for this. I note that the default resize is

video=Spline36ResizeMT(video,2690,2160)
What is the difference?

[TR-9970X]

Thanks for this. I note that the default resize is

video=Spline36ResizeMT(video,2690,2160)
What is the difference?

TBH, the only difference is probably the 64 instead of the 36.

For what I wanted, a custom script was easier than to edit EVERY single job, and there have been hundreds.

If it gets you the size you want, good, if it doesn't, you'll have to either wait for some other suggestions, or use a different app. (eg:- Handbrake)

[archiel]

TBH, the only difference is probably the 64 instead of the 36.

For what I wanted, a custom script was easier than to edit EVERY single job, and there have been hundreds.

If it gets you the size you want, good, if it doesn't, you'll have to either wait for some other suggestions, or use a different app. (eg:- Handbrake)

The script is more than fine; what I would like to understand why use 64 rather than 36 - what is being affected.

n.b. the two pixels is because I am also using SMDegrain and 2 pixels is the smallest crop in order to have the dimensions divisible by 8.

[TR-9970X]

The script is more than fine; what I would like to understand why use 64 rather than 36 - what is being affected.

n.b. the two pixels is because I am also using SMDegrain and 2 pixels is the smallest crop in order to have the dimensions divisible by 8.

Just to be different to the default...when I have the option.

https://avisynthplus.readthedocs.io/en/latest/avisynthdoc/corefilters/resize.html

Could you use MDegrain first to resize, then re-run your preferred SMDegrain script. (Good to know you use SMDegrain)

[LigH]

What is the difference?

See: ResampleHQ kernels visualization (https://amusementclub.github.io/ResampleHQ/kernels.html)

Point with the mouse at the names of the curves below the graph to highlight the curves matching the interpolation kernel functions.

Spline36 uses 6x6, Spline64 uses 8x8 sample points in the surroundings of the calculated pixel position to calculate the new color, so it is more accurate but also more elaborate.

[Pulp Catalyst]

Hi, i'm trying the SMDegrain Lite, however i like to use the batch mode, but i also use the "Addborder16by9" script. How can i combine this with the other scripts, for example if i use the option "rlev11_a--SMD 200" it will also add the "Addborder16by9" with it?

GEMINI helped me create this, not tested yet.

#Custom Script: SMDegrain with AutoBorders 16:9

# Load SMDegrain and its dependencies
LoadPlugin("%AVISYNTHPLUGINS%\masktools\masktools2.dll")
LoadPlugin("%AVISYNTHPLUGINS%\mvtools\mvtools2.dll")
LoadPlugin("%AVISYNTHPLUGINS%\RgTools\RgTools.dll")
LoadPlugin("%AVISYNTHPLUGINS%\SMDegrain_Lite\MedianBlur2.dll")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\ExTools.avsi")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\LSFplus.avsi")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\ResizersPack.avsi")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\SharpenersPack.avsi")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\SMDEGRAIN\SMDegrain.avsi")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\Zs_RF_Shared.avsi")

# Load AutoBorders (assuming AutoBorders.avs defines a function)
Import("%AVISYNTHPLUGINS%\Scripts\AutoBorders.avs")

# --- Processing Order ---

# 1. Apply AutoBorders to the input video (provided by RipBot as 'video')
# This will crop black bars and add new ones to achieve 16:9, making sure it's mod-compatible.
video = AutoBorders(video, 16.0/9.0)

# 2. Apply SMDegrain to the now-cropped and bordered video
video = SMDegrain(video, tr=3, thSAD=300, thSADC=150, contrasharp=true, prefilter=1, refinemotion=true)

# The final 'video' clip is automatically returned by AviSynth
# when it's the last variable modified, but explicitly returning
# it makes the script clearer for some.
return video

[TR-9970X]

Hi, i'm trying the SMDegrain Lite, however i like to use the batch mode, but i also use the "Addborder16by9" script. How can i combine this with the other scripts, for example if i use the option "rlev11_a--SMD 200" it will also add the "Addborder16by9" with it?

GEMINI helped me create this, not tested yet.

First of all, who's is GEMINI ??

And what is this :- "rlev11_a--SMD 200" ??

Looking at that "GEMINI" script, I would doubt that RB will work with that (I could be wrong), but I have been using a custom resizing script recently,

So give this a try, and see what happens.

#Custom
LoadPlugin("%AVISYNTHPLUGINS%\masktools\masktools2.dll")
LoadPlugin("%AVISYNTHPLUGINS%\mvtools\mvtools2.dll")
LoadPlugin("%AVISYNTHPLUGINS%\RgTools\RgTools.dll")
LoadPlugin("%AVISYNTHPLUGINS%\ColorMatrix\ColorMatrix64.dll")
LoadPlugin("%AVISYNTHPLUGINS%\Plugins_JPSDR\Plugins_JPSDR.dll")
LoadPlugin("%AVISYNTHPLUGINS%\SMDegrain_Lite\MedianBlur2.dll")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\ExTools.avsi")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\LSFplus.avsi")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\ResizersPack.avsi")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\SharpenersPack.avsi")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\SMDEGRAIN\SMDegrain.avsi")
Import("%AVISYNTHPLUGINS%\SMDegrain_Lite\Zs_RF_Shared.avsi")
Import("%AVISYNTHPLUGINS%\Scripts\AutoBorders.avs")
video=SMDegrain(video, tr=3, thSAD=300, thSADC=150, contrasharp=true, prefilter=1, refinemotion=true)
video=Spline64ResizeMT(video,2690,2160) # optional
video=AutoBorders(video, 16.0/9.0)

I can't test this script, as my RB is setup differently, and the call's will be worded differently.

[tormento]

See: ResampleHQ kernels visualization
It would be nice to see more kernels in there, such as the ones from last iteration of AVS+, libplacebo and jpsdr's ResampleMT.

Who is the author?

[LigH]

According to http://avisynth.nl/index.php/ResampleHQ it was Cory Nelson; the main site used to be on int64.org but is no more, I believe.

Original thread by 'PhrostByte' (last active: 2nd August 2015) here: https://forum.doom9.org/showthread.php?t=160038

Since VapourSynth was created, it has been developed further there as well.

[TR-9970X]

In the last several weeks or so I have been doing 100's of TV series encodes, and I have been using 3 of my main PC's (the 13900KF, 7950X & 9950X3D), and they are getting the job done very nicely, however, about a week ago I noticed that randomly the Encoding Client window would "disappear" to the Taskbar, but I could not "show" it, and when ALL the other PC's finished whatever chunk they were encoding, it would just stop the whole process.

The only way I could get things going again was to force a stop to ALL the processes on the Client PC (9950X3D), and restart RB, and it would pickup from where it stopped, and continue still it happened again.

Strange thing is, if I don't have the 13900KF in the mix, the problem doesn't occur.

I did a reluctant fresh setup on the 13900KF, only to have the exact same thing happen.

I'm puzzled by this, as the 13900KF (if that IS the problem PC), hasn't really missed a beat for a long time.

[rlev11]

I have had this same issue on and off ever since the encodingclient.exe version has gone past 1.18.3.0, so it's been a while(last version without ANY issues). In fact I was also getting ready to post something here on this. Sometimes I get quite a few encodes in a batch done without issue, and sometimes after only a couple. Same thing, the encoding client window will just "disapear" from the desktop, the servers finish up their current chunk, then I have to close everything in task manager and start over. At least it does pick up where it left off, but I can no longer trust leaving a batch job unatended overnight or for any long period of time. The encodingclient will still exist in task manager, but it is doing nothing. Appears if it has sat for a while, Event Viewer will have an entry the encodingclient.exe has hung, but no other usefull information.

Interesting on the 13900kf maybe having involvement in this. I don't run my full farm all the time, but I do always have a i7-14700 as part of the mix. My other 2 intels (i5-13500,14500) I don't always fire up. Next run I have in a couple of days I'll take the 14700 out of the mix and only run the Ryzens for a while and see if the issue goes away for me as well. Could be something with that whole P and E cores and win11 kicking out butts??? I do run the client on my 9950x. All my intels were also part of the mix when I was running 1.18.3.
I've tried running the exe's in compatability mode to no change. Also tried running everything in high performance mode as well.

I used to get around it by copying back in 1.18.3, but last time I tried that it didn't work probably due to compatibility with versions of the other components. Could probably figure out a version mix that works again, just haven't felt the need yet.

Not sure if there is something I can run to monitor the encodingclient process and get some sort of error dump out of it when it fails to help troubleshoot, but would be willing to assist in troubleshooting in any way possible. It is just so intermittant it may take a while as I have found no condition to force a quick failure.

[TR-9970X]

I have had this same issue on and off ever since the encodingclient.exe version has gone past 1.18.3.0, so it's been a while (last version without ANY issues). In fact, I was also getting ready to post something here on this. Sometimes I get quite a few encodes in a batch done without issue, and sometimes after only a couple. Same thing, the encoding client window will just "disappear" from the desktop, the servers finish up their current chunk, then I have to close everything in task manager and start over.

Thanks for the thorough reply, rlev11 :)

It's "good" to know that I am not the only one having this issue.

I just had a thought, the 13900KF had been behaving itself for a LONG time, I wonder if it was a Windows 11 update a week or so back that changed something :confused:

I should have run the older version of Windows 11 when I did the fresh setup a couple of days back, instead I just ran update after the install.

I also will try slightly older build(s) of "Client", and see what happens.

I doubt you will have any issues just running the Ryzens :)

Just a side note, I still haven't been using the Threadripper much, as I want to "dedicate" that to just doing 4K stuff, however, I have tried it on a few encodes, and even tho it's not that much faster in fps, it can handle more encoding servers, so I would compare it to say 2, 7950X's. (depending on the settings in RB).

I have found the 9950X3D to be awesome, it's noticeably faster than the 7950X, and just for kick's, I ran the 3950X and running just 1 server, it was so slow in comparison, in fact, it slowed the whole process down by using a chunk that a faster PC could have used :(

So I might as well retire most of what used to be good PC's, as they now are just power wasters :(

Anyway, a bit off topic there...

I will be testing the client issue today, and I will report back when I have some results.

Cheers.


UPDATE:- I managed to find 1.19.0 & 1.19.1 Encoding Client's, and unfortunately, they cause that old "Authentication Failed" error :(

So we either need to find another solution, or if Atak can figure out what might be causing it, but as he hasn't got a 13 or 14 Gen CPU, it's probably something he won't be able to investigate.

I wonder if it was a Windows 11 update, a bit of a pain to check that.


UPDATE #2:- OK, uninstalled recent updates, and that didn't help.

Disabled ALL the E cores in BIOS, didn't help.

So for now, I can't successfully use the 13900KF, as a Server, at least :(

I wonder if the 13900KF was the Client to the Ryzen's, as Servers ??

[rlev11]

Worth a shot to try running the 13900KF as the client but without running a server on that PC. So it is just acting as the chunk distributor to the Ryzens as the servers and see what happens

[TR-9970X]

Worth a shot to try running the 13900KF as the client but without running a server on that PC. So it is just acting as the chunk distributor to the Ryzen's as the servers and see what happens

Yes, either way could prove something.

Could also use the TR, or the 7950X as the client, and see if the 13900KF does the same thing to them.


UPDATE:- Just finished a 2 hour session using the 7950X as the Client, and the 13900KF as the only Server...NO ISSUES !!!! :) (must be the 9950X3D)

[rlev11]

Just running only 6 of my Ryzens the encodingclient window dropped out during the 3rd job of a batch. So at this point I really doubt that it is a Intel/AMD difference issue.
Trying now bumping back the avisynth memory on all the servers from 16 gig to 8 gig just to change something.
Next after the memory change I will try is not running a server on the client PC and see if that makes a difference. Also going to try but I doubt it will change is running the servers and maybe the client doing a "run as administrator" just to change something.

My thought is whatever code that changed in the encodingclient.exe on the update from 1.18.3 to the next version has something in it kills the window under certain circumstances, just haven't figured out what those are yet. 1.18.3 I believe was the last version before in the client window server names changed colors with green and red, and the ability to see server errors from the client window. Looks like to me that was Version 1.27.3 which seems right.

EDIT:
After running most of the day and trying different things, I think I have it narrowed down to one of my 7900x Servers. I used my low power Plex box as a client only, and was able to reproduce the issue quickly and multiple times. Each time the window dropped, I noticed my one server when I started the client back up, the server window was open, but no communication was happening and would have to close and open the encoding server on that one same box. I shut that pc down and have been running for about 2 hours now without a hiccup. Could very well be that I put that server together around the same time ripbot updated and making me think it was the client app. Time to update and reset bios, replace the nic, and do a clean install on that 1 box and see what happens. (Knocks on wood things remain working without that 1 box!!!)

I did run process monitor while the issue cropped up, all I get is repeated Process Profiling messages on encodingclient.exe when normally there is 1 and then it logs communication starting back up to the servers

[TR-9970X]

@rlev11,

Sounds interesting, will be interesting if a fresh setup will solve your problems.

I was running for about six hours today, with the 7950X as the client, the 9950X3D as a server and the 13900KF as a server.

No issues, so I think I'm in a similar situation to you, where I'm going to have to do a fresh setup, etc on the 9950X3D, 'cause it doesn't like the 13900KF, as you know.

[rlev11]

I loaded up a large batch job and let it run overnight without the offending server in the mix and had no issues so I am convinced now the issue is that 1 box that I run just the encodingserver on. I double checked and made sure the ip was right, and the MAC address was correct in the encodingclient.ini file.

Not sure best way to troubleshoot this further. There is just some condition with the communication between the encodingclient.exe and a remote encodingserver.exe that can cause the client to just drop out like it does.

Once I get that offending box rebuilt, I will run process monitor against the encodingserver.exe process and if it fails again maybe I can get some usefull information from that end as to what is happening. I guess I can also fire up wireshark and monitor the traffic as well if that 1 box keeps failing.

At least I have a better understanding now of where the issue is, just not what the issue is....

[Pino72]

Hi,

since the auto update to 1.27.4 my network rendering stopped working on clients:

Encoding server clients all give this error message:

[2025-07-21 15:08:49] Client established connection with server.
[2025-07-21 15:08:50] Command "CONNECT" received from client.
[2025-07-21 15:08:50] Connecting with client... (192.168.178.25:1003)
[2025-07-21 15:08:50] Established connection with client. (192.168.178.25:1003)
[2025-07-21 15:08:50] Command "AUTHENTICATE" received from client.
[2025-07-21 15:08:51] ERROR! File \\192.168.178.25\RipBot264temp\job1\Chunks\44.cmd does not exist!
[2025-07-21 15:08:51] Encoding terminated.


[2025-07-21 15:08:51] Connection Closed Gracefully.

Going back on all 3 Pc's to 1.26 and it works again.

Other problem which was already mentioned here Version 1.27.4 does not show up in Win 11 (öatest updates installed) on my Ryzen 9800X3D. Task is running but no GUI. No way to access Ripbot and encoding servers also not loading.

Any idea how to fix both problems? I looked for the xxx.exe mentioned in other post that are preventing RB to load properly but no change and also did not have widget.exe running anyway and the other exe was not even on my system that was mentioned.

Thanks

[TR-9970X]

Hi,

since the auto update to 1.27.4 my network rendering stopped working on clients:

Encoding server clients all give this error message:

[2025-07-21 15:08:49] Client established connection with server.
[2025-07-21 15:08:50] Command "CONNECT" received from client.
[2025-07-21 15:08:50] Connecting with client... (192.168.178.25:1003)
[2025-07-21 15:08:50] Established connection with client. (192.168.178.25:1003)
[2025-07-21 15:08:50] Command "AUTHENTICATE" received from client.
[2025-07-21 15:08:51] ERROR! File \\192.168.178.25\RipBot264temp\job1\Chunks\44.cmd does not exist!
[2025-07-21 15:08:51] Encoding terminated.


[2025-07-21 15:08:51] Connection Closed Gracefully.

Going back on all 3 Pc's to 1.26 and it works again.

Other problem which was already mentioned here Version 1.27.4 does not show up in Win 11 (öatest updates installed) on my Ryzen 9800X3D. Task is running but no GUI. No way to access Ripbot and encoding servers also not loading.

Any idea how to fix both problems? I looked for the xxx.exe mentioned in other post that are preventing RB to load properly but no change and also did not have widget.exe running anyway and the other exe was not even on my system that was mentioned.

Thanks

Over 5 years since your last post, and you're just now having problems?

OK, so you have the latest updates for RipBot ?? (even tho there hasn't been any for nearly 6 months).

When did you update to 1.27.4 ? If you just updated with "old" Jobs in the queue, then that might be a problem.

Have you checked the free space on the drive where the RipBot Temp folder is?

Windows 11 24H2, all up to date? Have any of the network share's or settings or permissions been changed?

And what is "xxx.exe" referring to?

And yet 1.26.0 works...interesting.

[Pino72]

Over 5 years since your last post, and you're just now having problems?

OK, so you have the latest updates for RipBot ?? (even tho there hasn't been any for nearly 6 months).

When did you update to 1.27.4 ? If you just updated with "old" Jobs in the queue, then that might be a problem.

Have you checked the free space on the drive where the RipBot Temp folder is?

Windows 11 24H2, all up to date? Have any of the network share's or settings or permissions been changed?

And what is "xxx.exe" referring to?

And yet 1.26.0 works...interesting.

Well, I am using Ripbot for many years now and of course there were always some little problems with Encodingclient.exe freezing after finishing the Job and other small stuff but hey basically it just worked very well for me.

Win 11 completely up to date, as well as was Ripbot on version 1.27.4 at the end. No idea when he updated Ripbot since he is or was doing that on his own via auto update...

I tried on all 3 machines with 1.27.4 but then I have the error on both clients. With 1.26 on all machines all good I can do it like all the years before. with 1.27.4 on the server machine and 1.26 on the client also same error so it seems to be related to the 1.27.4 release?

To xxx.exe I was referrring to one other guy who mentioned some exe file that ürevented Ripbot from shwing the GUI....but that is a different problem of course but also related to the 1.27.4 version it seems and newest Win11 being up to date?

IP's of all clients and the server are still the same, nothing changed.

I of course deleted old jobs and created new ones...still the same.

For what I need I will then stay on 1.26 for now since everything is working. May try a newer version once it comes out then.

[TR-9970X]

I loaded up a large batch job and let it run overnight without the offending server in the mix and had no issues so I am convinced now the issue is that 1 box that I run just the encodingserver on. I double checked and made sure the ip was right, and the MAC address was correct in the encodingclient.ini file.

Not sure best way to troubleshoot this further. There is just some condition with the communication between the encodingclient.exe and a remote encodingserver.exe that can cause the client to just drop out like it does.

Once I get that offending box rebuilt, I will run process monitor against the encodingserver.exe process and if it fails again maybe I can get some usefull information from that end as to what is happening. I guess I can also fire up wireshark and monitor the traffic as well if that 1 box keeps failing.

At least I have a better understanding now of where the issue is, just not what the issue is....

So have you found what might be causing this problem ??

I'm now starting to get it with other PC combinations.

I was using the 7950X & the 5950X today, and the 7950X was losing the "Client", so now I'm just running the 7950X to see if it still happens.

But regardless of what PC crashes the Client, it's a hard crash that requires a forced stop.

So it's NOT an Intel thing.

[rlev11]

I re-did what I thought was my offending server from scratch, worked for about 6 hours in a batch over the weekend, had high hopes, but then the client window dropped out again. Turned that server off and then it ran another 6 hours until the batch job finished up without error. So no, I did not find what is causing this...

I found encodingclient.exe version 1.18.4 which I now believe is the last version I did not have this issue with. I know it started with the the first version where the encoding client server names changed colors with green and red, and you could open up error messages from the servers on the client when there was a server error. I am going to copy that into my client pc leaving all the other exe's at their latest versions and use that for a while and see if the issue is still there. Will then also turn off auto updates so it leaves it be. It works with a couple of my boxes running just as a quick test. I think the only issue I will have is there will be that file sharing issue from a few months back with 24H2 and WMIC being depreciated. On my couple boxes I have fresh 24h2 installs on, I'll just re-enable wmic on those machines for now.

Probably won't know one way or the other for a couple weeks until I have the chance to fire up a couple long batch jobs.

[TR-9970X]

I re-did what I thought was my offending server from scratch, worked for about 6 hours in a batch over the weekend, had high hopes, but then the client window dropped out again. Turned that server off and then it ran another 6 hours until the batch job finished up without error. So no, I did not find what is causing this...

I found encodingclient.exe version 1.18.4 which I now believe is the last version I did not have this issue with. I know it started with the the first version where the encoding client server names changed colors with green and red, and you could open up error messages from the servers on the client when there was a server error. I am going to copy that into my client pc leaving all the other exe's at their latest versions and use that for a while and see if the issue is still there. Will then also turn off auto updates so it leaves it be. It works with a couple of my boxes running just as a quick test. I think the only issue I will have is there will be that file sharing issue from a few months back with 24H2 and WMIC being depreciated. On my couple boxes I have fresh 24h2 installs on, I'll just re-enable wmic on those machines for now.

Probably won't know one way or the other for a couple weeks until I have the chance to fire up a couple long batch jobs.

OK, well it seems to be becoming a bit more of an issue..

I tried a couple of older client builds (1.19.0 & 1.19.1), and they didn't work due to the authentication issue, due to a change with 24H2, and Atak had to "fix" that, which he did.

Also, due to a significant change with x265 builds, Atak had to "fix" that, which he did, and it's been running pretty sweet since.

I would be surprised if going way back to 1.18.3 would actually work on 24H2.

And now that I am seeing this issue on more of my PC's, I can't help but think it's a Windows update thing, as there hasn't been any RB update since late February.

It doesn't help that Atak doesn't have reasonably current hardware, and he prefers Windows 7, also not knowing how much he actually uses RipBot these days, then he's not affected by these issues.

I think that when I did a fresh install of 24H2 on the 13900KF a couple of weeks back, I should have left it at the older version build it was, instead of updating it straight away.

Did you do an update on your fresh install, or was it the latest build already ??

If it IS a Windows thing, then we're in trouble :(

I'll just re-enable wmic on those machines for now

I tried to do this back when this was changed, but had no success, how do you do that ??

UPDATE:- I found client 1.18.4 and replaced 1.19.2, on the 7950X, and it was working well, on its own using DE, then I did the same to the 13900KF, and almost instantly when the Server started on the 13900KF, client dropped out on the 7950X.

[rlev11]

So I found my original post on this issue from Oct 8 2024. I was copying back in encodingclient.exe ver 1.18.3 which was working for me at the time. I used that version of the encodingclient and ran a test and ALL 14 of my encoding servers connected this time. So I am going to just leave it go with that version for a while and see what happens again.

[TR-9970X]

So I found my original post on this issue from Oct 8 2024. I was copying back in encodingclient.exe ver 1.18.3 which was working for me at the time. I used that version of the encodingclient and ran a test and ALL 14 of my encoding servers connected this time. So I am going to just leave it go with that version for a while and see what happens again.

That should produce some interesting results....

Are you running up to date 24H2 on all 14?

After my instant 13900KF problem, I shut that down and had the 9950X3D as the server to 7950X, with 1.19.2 clients on both... I had the client disappear on thee 7950X a couple of times.

But its still strange that this only started a couple of weeks ago.

I will try 1.18.3 next time (tomorrow).

[Ryushin]

Hello Atak,

Thank you for you for continuing to support RB as it's been essential for me. (BTW, your PM box is full)

I posted a few months back about a job that created an info1.txt file and I'm having the same thing happen now with four particular files.

I ripped the Mary Tyler Moore Show and extracted 150+ episodes. All but four went through fine and I have no idea why since they were all encoded the same way. But four of them generated a info1.txt file and they can't render the file when trying preview them. Turn off Inverse Telecine and they work fine.

I've included one of the files here along with it's job folder.
https://cloud.chrisdos.com/s/GiPizfizQYFYwGk

I use Handbrake to convert to BT.2020 color matrix before adding them to RB.

If you have time to look into this I would appreciate it. Thanks much Atak.

[TR-9970X]

Something Ryushin said made me look for updates, and sure enough, we've got one RB is now 1.27.5 :)

There are 10 "new" items, however a couple of them have the same version/build number, and some are still not as current as they could have been.

But there is a new item called "superviseprocess", cannot find any reference to it with RB, so it might be a "silent operation".

Changelog explains, so the client issue has been modified, and the small issue I had with some subtitles also "fixed" :)

And to echo what Ryushin said, thanks for the ongoing support.

I've just noticed that Atak has finally updated the download link on page 1, it's now 1.27.5, instead of 1.26.0. THANKYOU !!!!

Even https://www.videohelp.com/ is showing the update :)

[TR-9970X]

@rlev11,

I wonder if the current update might rectify the problem we've been having....

Changelog:-

v1.27.5
Added: EncodingClient.exe is now monitored by SuperviseProcess.exe. EncodingClient.exe will be automatically killed if does not consume CPU cycles for 1 minute.
Fixed: Segmented subtitles are now correctly saved in UTF-8 format instead of UTF-16
Fixed: Cover Art downloading
Fixed: detection when mkv muxing fails

[rlev11]

I will let it update to 1.27.5 and see what happens. Not a large enough sample size to feel 100% confident, but since reverting the client back to 1.18.3 last week. I have done a couple 2-3 hour sessions and a 6 hour one without any issues.

[TR-9970X]

I will let it update to 1.27.5 and see what happens. Not a large enough sample size to feel 100% confident, but since reverting the client back to 1.18.3 last week. I have done a couple 2-3 hour sessions and a 6 hour one without any issues.

Well I didn't get around to trying 1.18.3 because I haven't done anything in the last couple of days, and now this new ones out, so I may not have to bother.

Clearly Atak has been reading our posts, and has released a "fix", among other things. :)

[rlev11]

Hello Atak,

Thank you for you for continuing to support RB as it's been essential for me. (BTW, your PM box is full)

I posted a few months back about a job that created an info1.txt file and I'm having the same thing happen now with four particular files.

I ripped the Mary Tyler Moore Show and extracted 150+ episodes. All but four went through fine and I have no idea why since they were all encoded the same way. But four of them generated a info1.txt file and they can't render the file when trying preview them. Turn off Inverse Telecine and they work fine.

I've included one of the files here along with it's job folder.
https://cloud.chrisdos.com/s/GiPizfizQYFYwGk

I use Handbrake to convert to BT.2020 color matrix before adding them to RB.

If you have time to look into this I would appreciate it. Thanks much Atak.

I downloaded this and tried it, when I choose inverse telcline or just decimate , i get a TFM: YV12 and YUY2 data only error when I preview script the video now. first time Zi tried it I just got the could not render error????

[Atak_Snajpera]

Hello Atak,

Thank you for you for continuing to support RB as it's been essential for me. (BTW, your PM box is full)

I posted a few months back about a job that created an info1.txt file and I'm having the same thing happen now with four particular files.

I ripped the Mary Tyler Moore Show and extracted 150+ episodes. All but four went through fine and I have no idea why since they were all encoded the same way. But four of them generated a info1.txt file and they can't render the file when trying preview them. Turn off Inverse Telecine and they work fine.

I've included one of the files here along with it's job folder.
https://cloud.chrisdos.com/s/GiPizfizQYFYwGk

I use Handbrake to convert to BT.2020 color matrix before adding them to RB.

If you have time to look into this I would appreciate it. Thanks much Atak.

1) Enable ONLY DECIMATE -> 23.976 FPS. INVERSE TELECINE IS NOT REQUIRED! There are no combing artefacts!

UPDATE
2) Update TIVTC to latest version
https://github.com/pinterf/TIVTC/releases/download/v1.0.29/TIVTC-v1.0.29.7z

extract from archive x64\TIVTC.dll and put it in Tools\AviSynth plugins\TIVTC

New version supports 10 bits!

[Ryushin]

1) Enable ONLY DECIMATE -> 23.976 FPS. INVERSE TELECINE IS NOT REQUIRED! There are no combing artefacts!

UPDATE
2) Update TIVTC to latest version
https://github.com/pinterf/TIVTC/releases/download/v1.0.29/TIVTC-v1.0.29.7z

extract from archive x64\TIVTC.dll and put it in Tools\AviSynth plugins\TIVTC

New version supports 10 bits!

Fantastic. Thanks Atak. Yep, you're right, just needed Decimate. Good news about TIVTC added 10 bits.

Those four episodes are encoding now. Thank you, I appreciate it.

[rlev11]

Back to trying 1.18.3.... Updated ripbot client and all my servers to 1.27.5. about 3 1/2 hours into a batch encode, middle of a video, encodingclient window just closes, servers finish up their current chunk, then I have to reset everything and restart the encodes

[TR-9970X]

Back to trying 1.18.3.... Updated ripbot client and all my servers to 1.27.5. about 3 1/2 hours into a batch encode, middle of a video, encodingclient window just closes, servers finish up their current chunk, then I have to reset everything and restart the encodes

Well, that sux !!! :(

Back to the drawing board then :(

Was it the same PC ?

Hopefully I can get my gear updated to 1.27.5 today, and see what happens.

[MCFish]

In the last several weeks or so I have been doing 100's of TV series encodes, and I have been using 3 of my main PC's (the 13900KF, 7950X & 9950X3D), and they are getting the job done very nicely, however, about a week ago I noticed that randomly the Encoding Client window would "disappear" to the Taskbar, but I could not "show" it, and when........


This is nothing new. I've had it on/off for years. Never found out why. Tried older ripbots, different servers/clients. After weeks/months of not using ripbot I usually removed ripbot and started fresh and sometimes it could work awhile.
Think i had a script for awhile that checked encodingclient process and killed it, so it would mux the failed encode and continue to the next. Worked sometimes...
Doubt its a windows update issue. Have not seen it for a while now, "knock on wood"

[Atak_Snajpera]

Back to trying 1.18.3.... Updated ripbot client and all my servers to 1.27.5. about 3 1/2 hours into a batch encode, middle of a video, encodingclient window just closes, servers finish up their current chunk, then I have to reset everything and restart the encodes

1) Select job
2) Click edit (or double click on job)
3) Click done
4) Repeat for all jobs
5) START

[rlev11]

1) Select job
2) Click edit (or double click on job)
3) Click done
4) Repeat for all jobs
5) START

Will revert back to the latest versions and try this to restart a failed batch.
Any suggestions on how to troubleshoot why the encoding client window drops out periodically in the first place?? Always willing to help troubleshoot whatever I can...
Does not appear now to be directly related to an encoding server. All encoding servers are started with this command, only differences will be the thread numbers depending on the CPU specs.

encodingserver /ip xxx.xxx.xxx.xxx /port 1000 /clear-error-log /priority normal /restart-time-limit 1 /avisynth-prefetch-threads 16 /x264-threads 32 /x265-threads 32 /avisynth-setmemorymax 8

[TR-9970X]

I'm not having any success with 1.27.5 :(

I loaded up quite a few jobs, and it just throws up all sorts of unexplainable errors, so I abort !!

Gone back to the basics of 1.27.4, on the same job queue, and away it goes. :)

But I have to do this:_

1) Select job
2) Click edit (or double click on job)
3) Click done
4) Repeat for all jobs
5) START

[TR-9970X]

There has been another small auto update

It's only RipBot264.exe, and TIVTC, as far as I can tell, haven't tested it, hopefully someone has.

[LigH]

There is also a thread in the VideoHelp forum (https://forum.videohelp.com/threads/418830-Latest-Ripbot264-1-27-5-Distributed-Encoding-Broken). Same user?

[slalom]

@Atak

I get an error

D:\DirectCD\Program Setup Files\RipBot264v1.27.0>"D:\DirectCD\Program Setup Files\RipBot264v1.27.0\Tools\SuperviseProcess\SuperviseProcess.exe" ""D:\DirectCD\Program Setup Files\RipBot264v1.27.0\EncodingClient.exe" "E:\Temp\RipBot264temp\job715\job715_EncodingClient.meta"" /norestart /verbose 1 /log "E:\Temp\RipBot264temp\Job715\SuperviseProcess_log.txt" /appendlog
[2025-08-08 19:00:38] Process D:\DirectCD\Program COULD NOT BE CREATED!



D:\DirectCD\Program Setup Files\RipBot264v1.27.0>"D:\DirectCD\Program Setup Files\RipBot264v1.27.0\tools\mkvtoolnix\mkvmerge.exe" "@E:\Temp\RipBot264temp\job715\job715_MuxFiles.json"
mkvmerge v94.0 ('Initiate NON-OFFICIAL') 64-bit
Error: The file 'E:\Temp\RipBot264temp\job715\video.264' could not be opened for reading: open file error.

[LigH]

The double quoting due to a path with white spaces seems to be the reason. Try to unpack the tool into a directory without any white spaces...

[slalom]

Don't know how you want me to do that, but guess what!

Fracking NordVPN was behind this!