To use the interoperability features between different Creative Finishing applications and workstations, you must be running the same version of Wiretap Server on each workstation. Depending on the Creative Finishing product and the operating system it is running on, the naming convention of the Wiretap Server changes.
| Current Release | ||
| Linux: 2013 Extension 1 | Mac OSX: 2013 | Windows: 2013 Extension 1 |
| Previous Release | ||
| Linux: 2013 | Mac OSX: 2012 Subscription Advantage Pack 2 | Windows: 2013 |
File path translation ensures that different workstations running different operating systems are able to convert file paths from other operating systems to a file path in their native file structure. This ensures compatibility between Linux, Mac OSX and Windows workstations in a collaborative workflow, as the different workstations send and receive commands to exchange media to and from shared storage.
Shared Storage in a Workgroup Environment
Before performing finishing and grading in a shared project from multiple workstations, using a shared storage (NAS/SAN), you must configure the following files:
To make sure Lustre is able to read media files from its direct connection to a shared storage, you must edit the PathTranslationTable portion of the init.config file, as follows:
<PathTranslationTable> <PathTranslation src="172.16.129.101@wtg:/Volumes/QASAN01" dst="localhost@wtg:/QASAN01"/>
This example translates a Mac Wiretap Gateway mountpoint to its corresponding Linux Lustre mountpoint, which allows Lustre to read the media from its own storage mount point, rather than from the remote workstation.
wiretap_path_translation_db.xml
It is possible to render media files on a shared storage and write the sequence and clips metadata in the Smoke / Flame Premium Media Library or Shared Folder (Wiretap Render). If the shared volume does not have the same mount point on the two workstations, you must add the corresponding mount points to the wiretap_path_translation_db.xml file, as follows:
Add the corresponding mount points:
<map src_os="Linux" src_path="/QASAN01" dst_os="MacOSX" dst_path="/Volumes/QASAN01" /> <map src_os="MacOSX" src_path="/Volumes/QASAN01" dst_os="Linux" dst_path="/QASAN01" />
Save the file and restart Stone+Wire
Performing a Wiretap render writes the files and the generated clips and sequence(s) that will reference the translated path.
You must render BatchFX segments and BatchFX on gaps prior to importing the sequence into Lustre.
All transitions are preserved by Lustre.

Axis Transition in Smoke/Flame (Image courtesy of EVN PRODUCTIONS)

Axis Transition displayed as a dissolve in Lustre (Image courtesy of EVN Productions)
Custom transitions are rendered media and appear as a clip in Lustre. This clip is maintained in Smoke/Flame when you reload the sequence after it is rendered in Lustre. It is recommended to create your custom transitions after the source media has been graded and replaced in Smoke/Flame.

Custom Transition in Smoke/Flame (Image courtesy of EVN PRODUCTIONS)

Custom transition in Lustre

Custom transition in Smoke/Flame after render from Lustre
All Timeline FX are preserved in Lustre. Lustre retains the Timeline FX metadata and displays the source clip rather than the result clip of the Timeline FX. Timeline segments with Timeline FX are displayed in the Lustre sequence with a Timeline FX icon. The Timeline FX are reapplied in Smoke/Flame when you reload the sequence.

Adjustment layers are supported like any other Timeline FX. However, they are not displayed when scrubbing or playing back in Lustre and cannot be graded. The original adjustment layer is restored in Smoke/Flame when you reload the sequence after it has been rendered in Lustre.

Containers and Matte Containers
Containers and matte containers created in Smoke/Flame are preserved in Lustre.
Multi-channel clips created in the Lustre sequence are recreated as matte containers in Smoke/Flame.