The following workflow
provides one example of working in a remote connection collaborative
environment. In this example, Flare remote connects to a Flame system
and loads the setups and media it will work on directly from a Flame project. Flame has
direct access to Flare setups and media at all times since Flare uses
the Flame framestore.
There may be some workflow
differences, if, for example, Flare creates the initial Batch
setups.
In the following workflow,
steps without cross references are specific to Flare and are
detailed in this chapter. Steps with cross references are covered
in other chapters and may contain some Flame functionality
that does not apply to Flare. Any Flare-specific considerations
are outside the scope of the other chapters.
Flare with Flame workflow:
- Start the application and connect to
a remote framestore.
- Load a Batch setup and associated clips
from Flame.
NoteMake sure the clips
were saved to a Snapshot library in Flame before loading the Flame setup.
Because Flare does not have access to the Flame Desktop, Flame clips
must be saved to a library in order for Flare to find them.
- Create Snapshot libraries in which to
save your clips.
- (Optional) Add or replace clips in the
current Batch setup.
- Work with the Batch toolset. See the Batch chapters in
Procedural Compositing with Batch.See
the Batch chapters in
Part 10: Procedural Compositing with
Batch.
- Perform basic gestural editing operations
such as trimming, slipping, and sliding on any source clip. See the Editing chapters in
Editing.See
the Editing chapters in
Part 8: Editing.
NoteEditorial operations
that involve record and source clips, for example, 3- and 4-point
edits, overwrites, inserts, and appends, are not supported.
- Save your sources and Batch setups to
a read-write library using the Snapshot feature.
- Process by doing one of the following:
- Output clips to a read-write library.
- Export image sequences. See
Export Node.
- Play results processed with the Output node.