[Dave LaRonde] “…if you only have one machine, it sounds counter-intuitive at first blush. Can you explain what’s going on when you use it?”
Sure — when you’re outputting an image sequence, there’s an option in the Render Settings to skip existing files. AE’s multi-machine renderer is somewhat naive; the render nodes don’t communicate with a manager or with each other; they look on shared storage for frames that don’t exist yet.
By default, all machines will begin with frame 0. The first one to hit the storage and see that Comp 1_00000.psd doesn’t exist will create that file on the shared storage to “claim” it, and then begin rendering the frame. When the other render nodes see frame 0 already exists, they will skip it and start looking for Comp 1_00001.psd. Each machine (really each instance in a multi-processing/multi-machine setup) continues this look-claim-render-save-look again process until the entire sequence is complete.
So how does this relate to a single-machine working? When you use the Multi-machine render settings and output modules, you’ll get a PSD sequence and “Skip existing frames” is checked by default.
If your render crashes and AE loses track of where it was, you can just add your comp back to the render queue and go; it will start at the beginning and skip everything it’s already rendered until it reaches a frame it hasn’t rendered yet.
There’s no need to use Multi-machine settings; you could manually check “Skip existing files” in the render settings for any image sequence-based output module — but since the settings are all already there straight out of the box, I prefer to use them.
Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events