Setup guide

2 In /usr/discreet/burn_<version>/cfg/init.cfg uncomment the MemoryApplication keyword. This
keyword sets the amount of RAM in megabytes (MB) to be reserved for jobs. This keyword is disabled
by default so Burn can dynamically adjust the amount of RAM used for each job based on the resolution
of the project. When you enable this keyword, Burn reserves the same amount of memory for each
job regardless of the project's resolution.
3 If necessary, change the value for the MemoryApplication keyword to set the amount of RAM (in MB)
to be reserved for each job up to 1400 (about 1.4 GB). For example: MemoryApplication 1024. Setting
the MemoryApplication keyword so that the (total render node memory) - (value of MemoryApplication)
is less than 2600 MB may adversely affect the stability of the render node.
4 Save and close init.cfg and restart the Backburner Server on the render node by typing:
/etc/init.d/backburner_server start.
5 Optionally implement the following guidelines for processing Burn jobs. Although these guidelines
are not mandatory, following them may help increase the success rate while processing jobs on render
nodes with limited memory resources.
■ If you know that the size of images in your projects may cause render node failure, enforce guidelines
about what can and cannot be sent to the render nodes. For example, if you know that 2K and 4K
images with Batch setups exceeding six layers may cause the render nodes to fail, ensure these
setups are not sent to Burn.
■ If you know that the complexity of the effects sent for processing may cause render node failure,
simplify effects by creating multiple Batch setups or by processing memory-intensive effects locally.
For example, if you know that complex Batch setups with multiple logic ops and colour correction
may cause render nodes to fail, render these locally instead.
If, after following these guidelines, your render nodes still fail because of low memory, consider adding
memory to the render nodes. Matching the amount of memory on the render nodes with the amount of
memory found on your Creative Finishing workstation is the most effective solution to memory issues.
WiretapCentral and Wiretap Gateway Installation
WiretapCentral and Wiretap Gateway
Wiretap is a is a protocol that allows a client system to remotely browse, read, and write media and metadata
from Autodesk Creative Finishing applications. The Creative Finishing Wiretap server (ifffsWiretapServer)
is installed with Creative Finishing applications, and requires no modification for WiretapCentral. The server
runs independently of the Creative Finishing application.
Wiretap Central is a web-browser-based application that allows you access to the Smoke and Flame projects
through any web browser on any workstation that has the ability to see your system through the network.
Wiretap Central can perform 3 types of functions
1 Browse through projects of your machine or machines within your infrastructure. This means you can
go into clip libraries, view reels and even create reels for future incoming media.
2 Import R3D media as well as all the multi-channel passes embedded in an OpenEXR file for 3D
compositing into the database.
3 The exporting facility allows you to encode different types of media from within wiretap central without
having to disturb the Smoke and Flame system if they are being used in a creative session. This gives
you different format support compared to the export options within Creative Finishing applications.
For example you can export H264, Mpeg1, Mpeg2, Mpeg4, FLV, IPOD compatible files and a few other
formats.
WiretapCentral and Wiretap Gateway Installation | 133