Hi Joe,
In addition to the plugins, you should make sure you have all the necessary fonts installed on all the necessary render nodes.
When collecting the files for the watch folder, make sure that your number of machines allowed accounts for your multiprocessing settings (i.e., 4 quad machines would be 16).
If a render fails, check the last few frames committed to disk to make sure they are properly rendered (non-blank). Delete any bad frames. Then you just re-add the comps to the queue, re-collect to the network, and it will skip all the previously rendered frames
Your performance will probably depend on how beefy your server is, because AE’s network renderer is unsophisticated. It’s pretty easy to tie up the disks or saturate your network when you’ve got multiple render nodes each looking for the next frame to render, then pulling the footage it needs for the frame, then writing it back out.
If you have several sequences to render, it might be faster for you to collect the files onto your render nodes directly, with each node watching a folder on a directly-attached drive, and have each node work on one sequence at a time, locally. If it’s just one sequence, you could split it up manually by setting different start and end frames, then manually collect them all into a single folder to create your Quicktimes. It’s extra manual to set up and finish, but you will save time by not creating a bottleneck at the server or network.
I always use image sequences for my renders, whether they are network renders or not, because if you have to make a tweak, you only need to re-render the affected frames and recreate the QT movie from the image sequence. Again, it’s a couple extra steps, but it really saves time on lengthy renders.
If you’ve got time, I’d suggest you take an old project and run a test of both the above scenarios to see which is really faster with your setup.
Good luck,
Walter Soyka, Principal
Keen Live, Inc.
Presentation, Motion Graphics & Widescreen Design
RenderBreak: A Blog on Innovation in Production