User Manual

Command Description
-listen
The node remains running and waits for incoming
requests from a manager.
-log <filename>
Causes the Render Node to output information about
the render to a log file. This appends to the end of an
existing log file.
-cleanlog
Clears existing text from a log file.
-verbose
Outputs more detailed information into the log file.
-quiet
Suppresses pop-ups and interface buttons from
displaying and needing interaction.
-version
Returns the Render Node version number.
-pri
high|above|normal|below|idle
Sets the node’s process priority to high, above, normal,
below, or idle.
-args <arg1> [, <arg2> ...]
Allows storing custom values that can be fetched by
calling the script function GetArgs(), which will return a
table of { <arg1>, <arg2>, ... }
TIP: An X11 virtual frame buffer is required to make a headless Linux command line
interface work.
Preparing Compositions for
Network Rendering
The way you construct a composition in Fusion Studio can help or hinder network rendering.
The media you read in, where plug-ins are installed, and the mix of operating systems on your
networked computers all play a part in how smoothly your network rendering goes. Your setup
must include several essential parts before network rendering will work:
 License dongle, Render Master, and Render Nodes must be on the same
local network (subnet).
 Fusion Server must be running as a background service on the same
computer where the dongle is installed.
 All source media from the comp should be placed on a network volume.
 The network volume must be mounted on each Render Node.
 Loaders must point to the media on the mounted volumes.
 Savers must write to a drive that is mounted on each render node.
 The Fusion comp must be saved to a volume that is mounted on each Render Node.
 All Render Nodes and Render Masters need read and write access to any volumes
specified as a source media location or render destination.
Chapter – 55 Rendering Using Saver Nodes 1055