Loading ...
Loading ...
Loading ...
Using Multiple Node Groups
A single Render Node can be a member of multiple groups. A single composition can also be
submitted to multiple groups. Submitting a composition to multiple groups results in it rendering on all
Render Nodes in the selected groups.
When a Render Node is a member of multiple groups, the order of the groups is important because
the order defines the priority for that Render Node.
For example, if groups are assigned to a Render Node as All, Hi-Performance, then renders submitted
to the All group take priority. Any renders in progress that were submitted to the Hi-Performance
group will be overridden. If the order is changed to Hi-Performance, All, then the priority is reversed.
Viewing the Render Log
The Render Log is displayed in the lower half of the Render Manager window, although it can also be
displayed in the console window. The text in the log displays the Render Manager activities, including
which frame is assigned to which Render Node, which Render Nodes have loaded the compositions in
the queue, and statistics for each render after completion.
To view the Render Log in the console:
– Open the Render Manager and choose Misc > Show Render Log.
There are two modes for the Render Log: a Verbose mode and a Brief mode. Verbose mode logs all
events from the Render Manager, while Brief mode logs only which frames are assigned to each
Render Node and when they are completed.
To disable Verbose mode:
– Choose Misc > Verbose Logging from the Render Manager’s menu bar.
Using Third-Party Render Managers with Fusion Studio
You can make use of third-party render manager software to control network rendering. This allows for
efficient sharing of your computer resources between the many applications that may make use of
them. Examples of such managers are Smedge from Uberware LLC, Rush from Seriss, and Deadline
from GetRender. Generally, these render managers use a command line renderer. By default, Fusion’s
Render Nodes operate as a service to the Fusion internal render manager. However, you can also run
the Render Nodes via the command line for third-party render managers.
Keep in mind that using a third-party render manager will prevent the use of some of Fusion’s network
rendering features, such as the ability to create network rendered Flipbook Previews and disk caches.
Command Line Rendering
For studios using third-party render farm managers like Deadline, Smedge, or Rush, the Fusion Render
Node can be called via command line passing arguments and file paths. In this Windows example, a
Render Node is called to load a composition called exampleV001, and render 10 frames:
//pathtoRN/FusionRenderNode.exe //pathtoProject/exampleV001.comp -render
-start 101 -end 110 -quit
This would start up, render frames from 101 to 110, and then quit.
Chapter 64Rendering Using Saver Nodes 1071
Loading ...
Loading ...
Loading ...