|
There seems to be something wrong with the latest 1.25 of Ripbot and the 1.16 EncodingServer. I had reported issues with trying to get a batch to start properly (adding a file via Add worked, though), however as of today, even adding a file via that method did not work with distributed encoding. What happens is that the file demuxes and this and that fine, then the dist encoding master window pops up for pass1 and nothing happens. None of the server farm responds. Their encodingserver instances literally do not receive the TCP command at all. Nothing appears in the logging console. I switched out for 1.15.1.0 of the encodingserver and THEN they started to receive commands but were unable to open the file for writing to my shared folder. It's only when I went back to Ripbox 1.24 and used IT'S encoding client, and encodingserver 1.15.1.0 on all of my boxes, that everything started working again. INCLUDING batch processing! Some weird networking change has evidently been done in the code which breaks connectivity. I disabled my firewall and tested pings between the machines, no problem at all. The problem now is that using RB 1.24 I get the old error stating that video.265 file could not be opened. Are there any known distributed encoding connectivity issues that others have experienced with RB 1.25 and EncodingServer 1.16? Using Windows 7 SP1.
--Dhry
|