Manualshelf

2017

ManualsBrandsAutodesk ManualsApplicationsSmoke
101102103104105106107108109110
Table Of Contents
About Intermediates Formats
Transcoded intermediates from Avid Media Composer supported in Smoke:
■ AVC-Intra 50
■ AVC-Intra 100
■ DNxHD
■ XDCam EX
■ XDCam HD
Transcoded intermediates from Avid Media Composer not supported in Smoke:
■ -J2K MXF
■ 1:1 MXF
■ 1:1p 10b MXF
■ Apple ProRes in MXF
■ Avid DNxHR (also known as DNxRI)
When conforming unsupported intermediates, use the Preferred Media ➤ Original Sources 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.
NOTE In MXF Op-Atom files generated by Avid Media Composer, audio tracks appear in the MediaHub as a single
audio channel file (A1). But once imported, the tracks display the original channels.
Working with Path Translation
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:
1 Close Smoke.
2 Open a shell window.
3 As root, open the following file in a text editor:
/usr/discreet/cfg/pathTranslation.cfg
4 Define a Source path and a Destination.
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:
<PathTranslationTable>
<PathTranslation src="/Volumes/SAN" dst="/ProductionSAN" />
</PathTranslationTable>
90 | Chapter 6 Importing and Exporting Media