Latest Ripbot264 1.27.5 Distributed Encoding Broken?

[tommy2010]

Hi Everyone and author of Ripbot,

Ripbot264 just got updated on my Windows 10 computer to the latest version 1.27.5 and after this update I can no longer do distributed encoding. As soon as I click "Start" I get the "job finished" notification and in the job queue the job becomes tagged with an *ERROR*. But when in the settings I set the "Distributed Encoding Mode" to "OFF" and click "Start" the encoding starts without an issue but not in the distributed mode obviously.

Additional notes:

- network between my main and slave machines is working fine
- both machines are Windows 10
- latest Ripbot264 is installed on both machines

Has anyone experienced the same or similar issues with distributed encoding after updating to latest Ripbot264? If so I would appreciate it if you could point me in the right direction to resolve the problem?

Thank you in advance.

EDIT: I suspect the newly introduced SuperviseProcess.exe is why the distributed encoding becomes killed, anyway to configure it?

[burt123]

Hi Everyone and author of Ripbot,

Ripbot264 just got updated on my Windows 10 computer to the latest version 1.27.5 and after this update I can no longer do distributed encoding. As soon as I click "Start" I get the "job finished" notification and in the job queue the job becomes tagged with an *ERROR*. But when in the settings I set the "Distributed Encoding Mode" to "OFF" and click "Start" the encoding starts without an issue but not in the distributed mode obviously.

Additional notes:

- network between my main and slave machines is working fine
- both machines are Windows 10
- latest Ripbot264 is installed on both machines

Has anyone experienced the same or similar issues with distributed encoding after updating to latest Ripbot264? If so I would appreciate it if you could point me in the right direction to resolve the problem?

Thank you in advance.

EDIT: I suspect the newly introduced SuperviseProcess.exe is why the distributed encoding becomes killed, anyway to configure it?

Hi tommy2010,

I feel your pain, as I have had the exact same thing happen, the error msg's pop up so quick I can't read what they are telling me.

I had to go back to the previous .exe's for RB to work again using Distributed Encoding (DE, as we call it).

There has been another auto update since that problem, haven't tested it yet, so it might be something you need to get done.

Have you thought about posting directly to the RipBot thread on Doom9.org ???

Good luck.

[tommy2010]

Hi burt123,

Thank you for replying. I contacted the author directly and it ended up being a bug in the software which he quickly addressed. Now the latest RipBot is working again in the distributed encoding mode without an issue. After the update, If you have any jobs in the queue marked with an *ERROR* simply double click on each and then click "Done" to refresh each job. Then clicking the "Start" button should start DE as before. Remember to update RipBot on your slave machines as well.

Best,
Tom