Flare Workflow
 
 
 

The following workflow provides one example of working in a remote connection collaborative environment. In the example, Flare remote connects to a Inferno system and loads the setups and media it will work on directly from a Inferno project. Inferno has direct access to Flare setups and media at all times since Flare uses the Inferno 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 Inferno functionality that does not apply to Flare. Any Flare-specific considerations are outside the scope of the other chapters.

Flare with Inferno workflow:

  1. Start the application and connect to a remote framestore.
  2. Load a Batch setup and associated clips from Inferno.
    NoteMake sure the clips were saved to a Snapshot library in Inferno before loading the Inferno setup. Because Flare does not have access to the Inferno Desktop, Inferno clips must be saved to a library in order for Flare to find them.
  3. Create Snapshot libraries in which to save your clips.
  4. (Optional) Add or replace clips in the current Batch setup.
  5. Work with the Batch toolset. See the Batch chapters in Procedural Compositing with Batch.
  6. Perform basic gestural editing operations such as trimming, slipping, and sliding on any source clip. See the Editing chapters in Editing.
    NoteEditorial operations that involve record and source clips, for example, 3- and 4-point edits, overwrites, inserts, and appends, are not supported.
  7. Save your sources and Batch setups to a read-write library using the Snapshot feature.
  8. Process by doing one of the following:
    • Output clips to a read-write library.
    • Export image sequences. See Export Node.
  9. Play results processed with the Output node.