I have tried changing settings in the memory and multiprocessing section of preferences on the render engines and seems to work right when that is not enabled.
Well, not to state the obvious: Then don't use MP?! It's actually pretty clear: You have effects in your projects that are dependent on temporal magic and/or are in some way generally not MP or network render safe (MB Looks anyone?). Therefore the issues appear to be pretty much what you can expect - it's all running in quirks mode and because of the intense network activity e.g. when a temporal effect needs to decode multiple frames for analysis and may block a source clip, you are seeing timeouts where the otehr instances never kick in. I'm afraid this goes beyond just looking for a technical cause. This may be inherent in your whole workflow and the way you structure your projects...
1 person found this helpful
As Mylenium says, don't use Render Mutliple Frames Simultaneously multiprocessing when rendering with mutliple computers across a network.
Thank you guys for your help. Sorry for the delay, I was distracted by the earthquake we had on the East coast! Take care!