About Batch Rendering

Use the Render node to output clips to the Desktop or Media Library. Use the Write File node to export open clip files or image sequences in any supported format to the system disk. With the Render node, metadata is kept; with the Write File node, metadata is not kept, unless Create Open Clip is enabled.

When ready to generate final clips or intermediate results, define the settings for each Render and Write File node to be rendered, then use the Render drop-down to make a rendering selection. By default, clips rendered using a Render node appear in the provided Batch Renders reel under the Batch Shelf. Use the Renders Destination drop-down of the Render Node settings menu to specify another location.

Render and Write File nodes support the RGB, RGB-A, and Multi-Channel processing modes.

When working with multiple resolutions, the resolution of the Render or Write File node is determined by the clip or node feeding it. However, the output can be resized to any resolution.

Use the Render List to manage multiple Render and Write File processes.

Proxy Quality and Rendering

The proxy quality workflow affects the Batch rendering options. The Resolution button in the Render and Write File nodes settings offers two options:

• Working Resolution: This tells Batch to render the media at the current working resolution. If the current working resolution is set to Proxy, Batch renders at proxy resolution. If the current working resolution is set to Full, Batch renders at full resolution. This is the default option.
• Full Resolution: This option forces Batch to render at full resolution, regardless of the current working resolution.
  
  
  
  

Naming Output Nodes

To help organize outputs, Render and Write File nodes can be created using the name of any output socket in the process tree. With the node selected in the Schematic view, press N and click a node output. The name of the node is updated. To change the node name, or to change the name of the original output socket, redo the naming process.

Tokens are also available to set default Render node and Write File node names:

• To define a name for one user, use the Default Render Node Name and Default Write File Node Name fields located the Batch & Batch FX Preferences.
• To define a name based on specific criteria or for multiple workstations, use the batchDefaultRenderNodeName and batchDefaultWriteFileNodeName python hooks, located in /opt/Autodesk/<installed_application>/python/batchHook.py.
  
  
  
  

Exporting with Open Clip Data

Open Clip files can be created using a Write File node by enabling Create Open Clip.

An Open Clip file is an XML file which describes channels, media, and versions. Create Open Clip files to be used inside Batch with the Import node, such as within a context of render passes between Flame and a 3D application.

For more information, see About Open Clip Files.

Exporting with Setup Data

Batch setup information can be exported alongside the media created using a Write File node by enabling the Include Setup. This allows someone to view and modify the original Batch setup, similar to how you can edit Clip History.

Advanced: Executing Batch from the Command Prompt

The rendering of a Batch setup can be executed directly from a shell command in order to render complex process trees while the workstation is not in use, such as overnight. The following command starts Flame for a specified project, and renders a specified Batch setup:

/opt/Autodesk/flame_<VERSION>/bin/startFlame -J <project name> -W <workspace name> -b <batch setup file path>

Alternatively, the -b part of the shell command can be replaced with the -s option used to run a defined python script. This allows the rendering of a Batch Group in the Desktop rather than a Batch setup on the file system.

/opt/Autodesk/flame_<VERSION>/bin/startFlame -J <project name> -W <workspace name> -s <python script file path>