Because clip history provides a record of most operations performed during a project, project collaboration is facilitated. Multiple users can work on a single clip and then use the clip history to navigate through changes made to a clip.
For instance, an Inferno, Flame, or Flint user could create a clip that included a colour correction and text effects. A Smoke user could then open the clip in Smoke on the EditDesk or in the Batch module, expand the history, and go directly to colour correction or text changes to make further modifications, regardless of the order in which the effects were created. The Inferno, Flame, or Flint user could also open the modified clip and use the clip history as a navigation tool in the same way.
The Clip History feature exists in Inferno 6.0, Flame 9.0, and Flint 9.0 or later, and in Smoke 7.0 and Backdraft Conform 7.0 or later. In Smoke and Backdraft Conform, you can view clip history that was created in Inferno, Flame, or Flint and vice versa. However, there are limitations to what you can access.
You cannot access certain modules created in Inferno, Flint, or Flame when you are in Smoke or Backdraft Conform. For example, if you view clip history in Smoke that contains a Compositor module (a module in Inferno, Flame, and Flint but not in Smoke), you cannot open the Compositor module from the Smoke clip history. Additionally, you cannot access any module in the history that precedes an unsupported module. Using the same example, if a cross-product-compatible module such as the Colour Corrector appeared in the clip history before the Compositor module, you would not be able to access the Colour Corrector module from the clip history in Smoke. You cannot change the order of modules, add modules, or delete modules in the clip history in Smoke and Backdraft Conform.
The following sections contain some basic clip history examples.
For a complete list of clip history support based on product and feature, see Clip History Features Per Product.
