|On this page|
The Net Barrier uses the tracker to ensure multiple machines stay in step with each other. This is useful if some external shared drive is being used to transfer data and you need to make sure that the machines don’t out pace each other.
Begins the render with the last render control settings.
Opens the render control dialog to allow adjustments of the render parameters before rendering.
Render with Take
Uses the settings in a particular take while rendering. Choose Current to use the current take when rendering.
Valid frame range
Limits the rendering of frames, when set to Render frame range or Render frame range only.
Render any frame
Allow the renderer to render any and all frames.
Render frame range
Only render the frames in the range set below, but allow the renderer to render other frames if they are referenced by in-range frames.
Render frame range only (strict)
Only render the frames in the range set below, and don’t allow the renderer to render other frames, even if they are referenced by in-range frames.
The port specified when starting the simtracker.py process for communication.
What machine will run the simtracker.py process for synchronization. If this is blank, no attempt at synchronization or data transfer will occur.
The job name to describe this synchronization or data exchange event. By using different job names one can have machines part of separate data-exchange and synchronization events.
Cooking is blocked until the given number of peers report into the tracker that they are done. Then they are all allowed to continue. Useful if you have a bunch of machines you need to operate in lock step.
Post Barrier Value
The given synchronization value is posted as the current barrier value for the job name. The machine is allowed to continue unimpeded. This is useful for a producer machine whose output other machines depend on, but which can operate as fast as it wishes.
Wait Barrier Value
Waits for the barrier value stored in the job name to reach the synchronization value. Then it is allowed to continue. This is useful to ensure consumer machines do not outpace the producers.
The slice number that this machine should report itself as. Each machine connecting under the job name should have its own unique slice number. Sometimes this can be inferred from the operation so this parameter will be absent.
Number of Peers
Total number of machines that have to synchronize. Sometimes this can be determined from the operation so this parameter will be absent.
The barrier value to post, if in post mode, or to wait for, if in wait mode.
Run this script before any rendering.
Run this script before each frame.
Run this script after each frame.
Run this script after all rendering.
Frame being rendered.
Total number of frames being rendered.
In this example, we demonstrate how a netbarrier ROP node can be used to ensure that multiple machines stay in sync with each other.
The following examples include this node.