render-001.xml
render-002.xml
The padded frames will still send info to the unpadded ones as well.
Here's how I have it setup at my network at home to do this:
I mounted the indigo folder from the server on the slave machines and then symlinked the server's logmaster.txt file to the indigo folder on the slave machines.
Next, run "tclsh indigo_slaverender.tcl" with the extra arguments. The first is the number of mutations it should look for. The second is the full path to the directory of renderable files:
/home/dudeman/indigo/renderdirectory
The third is the IP address or hostname (if hostname works) of the indigo master.
tclsh indigo_slaverender.tcl 500 /home/dudeman/indigo/renderdirectory 192.168.1.122
This will work with any type of mounting and linking system so long as the logmaster.txt file from lego's script is readable on the slaves.
If you find problems or anything wrong with it, let me know.
Also, it runs wine/indigo through nice -10 because on rendering for long periods of time on my computer, the system would be unuseable after 32 hours of rendering.http://www.davidhipp.com/scripts/indigo_slaverender.tcl
http://www.davidhipp.com/scripts/indigo ... tcl.tar.gz
I'm working on my own master script and/or possibly a combo script for both master and slave. I can make this work with windows fairly easily if someone will tell me one thing... Since I haven't done much command line stuff with windows, I don't know what the equivalent to the "killall" command would be or even if that's the best way to kill the indigo render in windows. Could anyone give me a command to pass and kill all indigo processes? Does indigo.exe somexml.xml > logmaster.txt throw everything into logmaster.txt like it does in linux?
If I know those, I can enable windows render slaves and possibly render masters.