To simplify the conform process, create the AAF project on the workstation running Smoke. And when exporting the AAF, save the AAF to the root of the media used in that timeline: the media should either be with the AAF, or within a folder alongside the AAF.
To simplify the conform process, when conforming on a Linux workstation, save the AAF to the root of the media used in that timeline: the media should either be with the AAF, or within a folder alongside the AAF. If you are conforming on a Mac, create the AAF project on that Mac. And when exporting the AAF, save the AAF to the root of the media used in that timeline: the media should either be with the AAF, or within a folder alongside the AAF.
To import a sequence using the MediaHub:
You can view the frame rate from the Preview Panel.
Smoke converts the AAF to its sequence format. According to the Media and Relative Search options, the sequence can be relinked or not, and the sources also imported, or not. The media itself is imported using the option file format options defined in the Format Specific Options tab.
You can also import a sequence from Conform:
You can select multiple sequences to import, using Shift-click and Ctrl-click.
If a source is used multiple times in a sequence, or across multiple sequences, and Save Sources Separately is enabled, only one instance of the source is imported. And the sources are saved in a sources folder.
If you plan on perform a Connected conform, you must import your sequences into a Reel group. Make sure to drag and drop the sequences on top of a Reel group, or to import from Conform. When you import your sequences through Conform, they are always added to the Sequences reel of the default Reel group, making sure you will be able to use the Sources and Shots sequences required for the Connected conform workflow.
In Smoke, when you conform an AAF using RED .r3d media files, you can also apply the RED Source Settings defined in Avid Media Composer. Source Settings are the color settings edited in either Media Composer.
To use the RED Color Settings defined in Media Composer:
This setting can also be set in the MediaHub.
The RED sources are displayed using the color settings defined in Avid Media Composer.
When using Keep Source Settings, never relink to clips already imported in Smoke because they already have color settings that cannot be overridden by the relinking process. Instead, make sure to use one of the following approaches:
Debayering resolution is not part of the information contained in the AAF Source Settings. You must therefore specify the debayering settings before locating the R3D files, or the media's resolution will not match that of the sequence. You should do this from the MediaHub before importing the AAF, or from the Media Import window as you locate the AAF.
Matching the resolution of an AAF to the fully debayered resolution of R3D files:
The resolution information is copied from the R3D file. Any AAF (or XML for that matter) will be imported to that resolution.
To set the debayering settings before importing the AAF:
You can then following the instructions above to import the AAF.
To set the debayering settings as you import the AAF:
This setting can also be set in the MediaHub.
The RED sources are displayed using the color settings defined in Avid Media Composer.
The options Search and Import Files and Link to Media Files are performed sequentially:
Transcoded intermediates from Avid Media Composer supported in Smoke:
Transcoded intermediates from Avid Media Composer not supported in Smoke:
When conforming unsupported intermediates, use the
option from the Media Import window to link to the original media files. Or from Media Composer, transcode the sources to a supported format.Sequences made using a unsupported frame rate, such as 48 fps, cannot be conformed in Smoke.
When you import an AAF or an FCP XML file with Link to Media Files enabled, Smoke tries to reconnect to the sources using the paths defined within. But if you are working in a collaborative environment where multiple OSes are used with varying volume mountpoints, or using a dead drop, you will run in cases where the path in the imported sequence cannot be resolved by Smoke. Most common case is with an AAF produced on a Mac OS X, where external volumes are mounted under /Volumes/, while on Linux, such volumes can be mounted on any point. This is where path translation comes in, allowing you to convert a path from one format into another. Once path translation is set up, linking and relinking to sources should be seamless.
You set up the path translation in a configuration file, where you define pairs of paths.
To set a path translation pair:
/usr/discreet/cfg/pathTranslation.cfg
For example, we need Smoke to search media files that was seen from a an offlining Mac at /Volumes/SAN, but seen from the conforming Linux workstation at /ProductionSAN:
Smoke will now translate any source path found in pathTranslation.cfg into its paired destination path when you import a sequence or use Link To Media File in Conform.