Difference between revisions of "UM:Rendering Avid Effects"
m (Upload page Rendering_Avid_Effects) |
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_Effects|UM:Retimes}} |
{{Template:M-Title|Rendering Avid Effects}} | {{Template:M-Title|Rendering Avid Effects}} | ||
Line 40: | Line 40: | ||
<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_Effects|UM:Retimes}} |
</div> | </div> |
Latest revision as of 12:06, 15 October 2014
When exporting an AAF from the Avid, one of the Export Settings available is Render Video Effects :
Enabling this will cause the Avid AAF export process to render all timeline effects. Avid calls these renders pre-computes.
If you are planning on returning to the AVID via AAF, we would recommend that you do not select the Apply AAF effects option on import into the Nucoda. |
Pre-Computes
Introducing pre-computes to the work flow adds some extra complexity that you will need to be aware of :
• | Pre-compute clips will not re-link on return to the Avid. They will also not be updated in the exported AAF (an Avid limitation). |
• | Merging the grades into updated AAF sequences will not work for pre-compute shots because they do not contain timecode or tapename information. |
Make sure all effects used in the Avid are fully rendered (no partial renders).
By default, Nucoda treats all transitions as dissolves, if you sequence contains any transition such as 3D wipes or spins, you will have to mix these down for them to appear in the AAF, renders will just come accross as dissolves. |