Difference between revisions of "UM:Mxf Staging"
m (Upload page Mxf_Staging) |
m (Text replacement - "|Platform:" to "|UM:") |
||
Line 1: | Line 1: | ||
<div class="manualcontent"> | <div class="manualcontent"> | ||
− | {{Template:M-Navlinks-top| | + | {{Template:M-Navlinks-top|UM:Manual|UM:Avid_Ds|UM:Avid_Effects}} |
{{Template:M-Title|MXF Staging}} | {{Template:M-Title|MXF Staging}} | ||
Line 47: | Line 47: | ||
<p class="p_DVBodyText"><span class="f_DVBodyText"> </span></p> | <p class="p_DVBodyText"><span class="f_DVBodyText"> </span></p> | ||
− | {{Template:M-Navlinks-bottom| | + | {{Template:M-Navlinks-bottom|UM:Manual|UM:Avid_Ds|UM:Avid_Effects}} |
</div> | </div> |
Latest revision as of 12:07, 15 October 2014
When writing MXF files to a network volume, it is often more efficient to write the files locally first and then move them to the target location.
This is called staging.
Staging is particularly useful when exporting to Avid Unity or ISIS systems. Test your configuration to see which settings are best for your workflow. |
Staging Folder
If staged, MXF files are first written to the folder specified by the general.prefs configuration parameter (inside media section) :
tempRootDir "X:\path\to\folder\" |
When Staging Happens
AAF Export
If you are exporting an AAF file, the MXF files created are always staged to the folder specified in tempRootDir. Once successfully written, they are moved to the first Avid MediaFiles folder specified in the preference file.
If you have enabled Export To Interplay, once successfully written, they will be moved to the Avid Interplay sharedStorage location (see the general.prefs) and checked in.
MXF Exports
If you are exporting MXF files, the MXF files will be staged if the following general.prefs configuration parameter (inside mxf section) is set to true :
useTempAsStaging true |
When set to true, MXF files are staged to the folder specified in tempRootDir. Once successfully written, they are moved to the first Avid MediaFiles folder.