If someone has experienced this please offer some insight and if it's a bug then Atak I hope you can get it fixed soon. I proceeded to run the job and it is working but on just one machine obviously but I would really like to get the distributed encoding working again. After a reboot I launched it again and in the settings I could see that it applied the distributed encoding "Off" setting even though it crashed. On the master I also noticed a warning icon and clicked it, it says that it can't connect or that it couldn't disconnect gracefully or something of that sort.įor another test disabled the distributed encoding in the settings and after hitting "Apply" again Ripbot crashed and I had to force shut it down. Also, what's odd is that the port on the server used to be 1000 and now it says 1003 for some reason when I never touched it and looks like it's not connecting. It compiles the chunks list and then just sits there as "Qued" and nothing happens.
Ripbot264 distributed encoding access violation update#
However, after the latest Ripbot update it's gotten worse as now the client won't even start encoding. I made no changes to my computers with only Ripbot updating itself automatically. It used to work flawlessly but now it seems like it's working every second time. When this happens the only way to close Ripbot is to force shut it down. On the master it will say "Idle" and is stuck at some percentage while the slave says "Encoding" but just sits there with a "Starting" message. Recently, I have an issue with Ripbot264's distributed encoding where it will crash randomly during the second pass.
0 kommentar(er)
