Creative Finishing workstations can use Burn if they are on the same version. When changing parameters, restart the software for them to be used.
Location of parameters
- Linux: edit /usr/discreet/<product_home>/cfg/init.cfg.
- OS X: run the Setup utility which is usually in Applications/Autodesk/[application name]/Utilities. Backburner settings are in the Backburner tab, under Application Settings.
- Parameters
- Manager Hostname [BackburnerManagerHostname]
- The hostname or IP address of the Backburner Manager system that will handle background jobs submitted by the workstation.
- Job Priority [BackburnerManagerPriority]
- The priority for jobs submitted by the workstation to Backburner Manager, from 1 (most important) to 100. With the default setting, all jobs are given the same priority, and Backburner Manager manages jobs and network resources automatically. Changing this setting is not recommended and may compromise access to the background processing network for other users.
- Server Group [BackburnerManagerGroup]
- Specifies a server group (a preset group of render nodes) used to process jobs submitted by the application. By default, Backburner Manager assigns a job to all available render nodes capable of processing it. If you have a dedicated group of render nodes for processing jobs, set the value to the name of the render node group.
- Group Capability [BackburnerManagerGroupCapability]
- Enables or disables the submission of jobs that require a GPU (such as floating point jobs) to the background processing network. Configure this according to the GPU capabilities of the nodes in the background processing network:
- Software: none of the nodes in the background processing network is equipped with a GPU. The application will not send jobs that require a GPU to the background processing network, but only jobs that can be processed in software mode (using OSMesa) by the render nodes.
- GPU: all the nodes in the background processing network are GPU-enabled. The application will send all jobs to the GPU-equipped nodes in the background processing network, even if some jobs do not specifically require a GPU node. The GPU-equipped render nodes will render jobs that require a GPU, as well as OSMesa jobs. If the background processing network also contains nodes without a GPU, and this setting is used, , all jobs are sent only to GPU-equipped render nodes, and the nodes without a GPU are never used.
- Hybrid: the background processing network contains a mix of nodes with GPUs and without GPUs. The application will send all jobs to the background processing network, and Backburner Manager will distribute each job to the appropriate type of render node. Jobs that require a GPU are sent only to GPU-equipped nodes, while jobs that do not require a GPU are sent to any available render node (GPU or non-GPU), to be processed in software mode. Use this setting only if you are sure that at least one node in the background processing network is equipped with a GPU. Attempting to submit a job that requires a GPU to a background processing network with no GPU-enabled nodes results in the job being stuck in the queue indefinitely.