Setup guide

5 If this is the first filesystem you are configuring for this workstation: Get the FRAMESTORE ID, e.g. grep
"FRAMESTORE" /usr/discreet/sw/cfg/sw_framestore_map and use the ID value to update
/usr/discreet/sw/cfg/sw_storage.cfg e.g.
[Framestore]
ID=myworkstation
6 Optionally Configure bandwidth reservation (page 45).
7 Restart Stone and Wire with: /etc/init.d/stone+wire restart
8 Check the filesystem is mounted: /usr/discreet/sw/sw_df.
Any project created in your application after this point has the new standard filesystem partition as its
primary partition. Any pre-existing projects are unaffected by this setting and remain associated to their
respective partitions.
Single workstation rendering
In a standalone deployment, all the Backburner and creative application components needed for background
processing are installed on a single workstation.
Lustre
Lustre can work with streaming media-such as Red (.r3d) files-in two distinct ways. In the simplest
configuration, Lustre reads material natively through the Wiretap Gateway. In this case, the Wiretap Gateway
decodes the media on-the-fly, immediately returning proxy-quality images for use in Lustre. As shown in
the following illustration, Backburner is not needed. As in the native workflow, Lustre browses storage devices
via the Wiretap Gateway. Here, however, transcoding jobs are sent directly from the Lustre UI to the
Backburner Manager. The Backburner Manager sends the job to the Backburner Server, which invokes the
Autodesk MIO Adapter processing engine to carry out the transcoding. The MIO Adapter reads from storage
directly and writes its results to the Wiretap Gateway. The Backburner Monitor can optionally be used to
monitor job progress.
Background I/O
Background I/O is a media management tool for performing I/O with minimum impact on the performance
of the creative workstation. The tool has both a command-line and an embedded interface, and can:
■ Transfer clips using Wire
■ Publish clips
■ Stonify soft-imported clips
■ Resize clips
■ Generate proxies for clips
The embedded version of the tool makes use of Backburner for two operations only: to transfer clips using
Wire and to generate proxies for clips. The other operations to not require Backburner. In contrast, the
command-line version of the tool uses Backburner for all operations.
Stone and Wire are automatically installed during installation of the Visual Effects and Finishing application.
Not all Backburner components may have been installed during product installation.
The Backburner Web Monitor and Backburner Web Server are optional, for the purposes of Background I/O.
Requesting a “Background Wire” transfer from the Clip Library menu invokes Backburner. The Visual Effects
and Finishing application submits the job to the locally-installed Backburner Manager which invokes the
34 | Chapter 1 Flame Premium Installation and Configuration