Workflow thoughts and ideas
Posted: Mon Jan 21, 2013 5:14 am
Hi guys-
As I start implementing Octane into my studio workflow I'm curious how others have done this. The issue is I'm pretty spoiled with my network clients rendering through C4D. Just send an animation to the network and all available computers pick up frames and start rendering. Very nice. Now however I'm faced with no network rendering and a room full of computers and GTX 680's.
I figure I can breakdown each rendering project into bite size pieces and split them up. Say I have 10 machines to render on, I create 10 versions of the project each with they're own network paths set and all that. The trouble is, what if there's a change to the main file? Now I have to re-make all those files and set directories all over again.
This could be a major pain in the ass.
Has anyone dealt with this in a studio environment? What is a better way to handle this?
Thanks all! Back to drinking my Octane Koolaid.
Alec
As I start implementing Octane into my studio workflow I'm curious how others have done this. The issue is I'm pretty spoiled with my network clients rendering through C4D. Just send an animation to the network and all available computers pick up frames and start rendering. Very nice. Now however I'm faced with no network rendering and a room full of computers and GTX 680's.
I figure I can breakdown each rendering project into bite size pieces and split them up. Say I have 10 machines to render on, I create 10 versions of the project each with they're own network paths set and all that. The trouble is, what if there's a change to the main file? Now I have to re-make all those files and set directories all over again.
This could be a major pain in the ass.
Has anyone dealt with this in a studio environment? What is a better way to handle this?
Thanks all! Back to drinking my Octane Koolaid.
Alec