Avid workflows in Nucoda has been tested with Media Composer 8.0 and higher


General notes on using Avid sequences in Nucoda:


There are three main workflows when using Avid and Nucoda

    

  1. AAF to Nucoda for grading and finishing in Nucoda - this can include pre-computes and mixdowns, material is imported in Nucoda, graded and exported for delivery. 

    This can include the creation of a new Record OrderAAF that will reference the new record order file and can be checked into Interplay.


  1. AAF to Nucoda for grading the MXF media or re-conforming to original camera media. Return the source modified AAF to Avid relinking to the new graded material -
    this is a very common workflow and can include handles added to the graded media to facilitate edit adjustments. Mixdowns are fully supported.


  1. AAF to Nucoda and return MXF files to Avid for relinking - ensure that the media has a unique tape name, Camroll, Lab Roll or Reel for relinking.
    We will also retain the original Avid SourceID to make relinking material more robust.



In all cases it is recommended that a pre-grade stage is performed on the Avid


  • Mixing down and replacing any re-time and freeze frames on the timeline - for users who want to use the relink or return AAF

  • Mixing down complex nested effects breaking them out for reassembly in the Avid

  • Mixing down any non dissolve transitions and AVX effects or breaking out the media for grading and re-assembly.


Media format support

Nucoda supports the reading and writing of OP-Atom MXF media.


  • IMX 25

  • IMX 50

  • DV25

  • DV50

  • DNxHD LB

  • DNxHD SQ

  • DNxHD HQ

  • DNxHD HQX

  • DNxHD 444


DNxHR will only be available in resolutions larger than HD

  • DNxHR LB

  • DNxHR SQ

  • DNxHR HQ

  • DNxHR HQX

  • DNxHR 444


  • Uncompressed YUV 10 and 8 bit

  • Uncompressed RGB Files


Nucoda also supports reading a wide range of other media formats including


  • XAVC 100
  • ProRes


Nucoda can write the following Op1a formats


  • XDCAM 50 - Including the HDF01a specification
  • AVCi-100


Please note that media format availability will depend on the frame rate and resolution.
Not all frame rates support all resolutions.


Composition support

  • Nucoda support the import and export of AAF compositions and also EDL
  • CMX3600, Char16 and Char32)


Markers imported as Segment or Timeline 


Nucoda and Phoenix now correctly assigns Segment and Timeline markers when imported from AAF,  based on the marker type in the Avid timeline.


For EDL the Avid convention is followed:


* LOC: 01:00:01:14 RED  VIDEO  will add a segment bookmark
* 01:00:03:23 BLUE  - will add a timeline bookmark


Using markers in AAF to indicate speed changes

If an AAF is imported into the application any speed or variable speed changes that were applied in Avid will be marked on the clip as segment bookmarks. The bookmarks will contain the value of the keyframe at that point.

This will allow the user to easily duplicate speed ramps when using tools like Re:Vision FX Twixtor.
 



Audio support

  • Nucoda supports Mono and Stereo Audio tracks from Avid
  • Audio must be 48000 / 24 Bit PCM (MXF)
  • Audio and audio tracks are supported when importing AAF compositions.


Users can choose which audio track should be imported when importing an AAF, by default the setting is to import all tracks.

AAF_New.PNG


Clicking on the Select Audio Tracks button will open a dialog that will  show available tracks to select for import. Once opened, a track selection must be made else no tracks will be imported at all



.AAF_Selection.PNG


 Track names are retained but the will be reordered numerically in Nucoda.
 Using this option will not affect AAF round trip workflows.


Avid Interplay and Nexis support

Nucoda is able to import material directly from an attached Nexis storage system (Avid license is required) Exports can also be made to the Nexis using automatic backup and staging options.

If the Nucoda is attached to an Avid Nexis (ISIS) with Interplay the user can check clips and sequences into Interplay directly while exporting from Nucoda.


Export file naming

When exporting OpAtom MXF files in any Source order format, the names are automatically generated on export and no user input is accepted.

In  Mixdown Rec the user can name the file as required.


Metadata

Nucoda reads the LabRoll, CamRoll and Reel fields when importing and exporting media from Avid, this metadata will be passed through from Avid to Nucoda and back to aid a relink workflow.
 

  • The user can inject a custom project name when exporting material
    (currently only in DNxHD formats)


  • Exported material can be tagged with a user editable suffix for the Avid name to identify graded media. An upcoming release will add support for all fields including user generated data to be round tripped. Currently AAF roundtrip material is tagged as DV_Graded

  • To aid in file relinking Nucoda will use the SourceID field in the original imported MXF from 2017.2

    

Support for Avid effects:

  • Dissolves 

  • In / Out dissolves

  • Dip to colour is described as a dissolve in Avid and needs to be replaced in Nucoda

  • Animated PIP, Resize and 3D Resize (option for maintaining animation on import of AAF)

  • Avid media Mixdowns are supported on import and export using AAF

  • Avid pre-computes - this means that Nucoda can read Avid rendered effects for grading, if a sequence contains pre-computes it cannot go back to Media Composer since pre-computes cannot be relinked in Media Composer.

    • Merging the grades into updated AAF sequences will not work for pre-compute shots because they do not contain timecode or tape name information.

    • Ensure 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 across as dissolves.


  • Nested effects are not supported - it is recommended that they are rendered or mixed down before the AAF is created and imported into Nucoda.

  • AVX effects like Boris FX are not supported on import from AAF - it is recommended that they are rendered or mixed down before the AAF is created and imported into Nucoda.

  • Re-times and speed effects

    • Standard re-times are supported -speed ramps are not supported at this time

    • It is recommended that re-times and freeze frames are mixed down and replaced on the Avid timeline before importing the composition into Nucoda.

    • Make sure that if there is mixed frame rate material with Motion adapters applied.

  • Subclips are supported

  • Multicam is not supported - multicam edits should be committed before exporting the AAF from Avid, use the “Commit Multicam edits” command when right clicking on the Avid sequence.

  • Please also ensure that no Stereo compound clips are in the composition


AAF import dialog options:

Importing an AAF is done via the import menu in the library:


AAF_001.PNG



1. Media Files : Set the path to the files needed for import


2. Import: Set to select whether the AAF is imported into a new composition or merged with the current. Please note, that for a round trip only the original imported AAF is used.


3. Overwrite existing track

4. Merge grades - select this to merge grades from a previous composition into a new one.


5. Select to import the material referenced in the AAF file


6. Select to link the material to the imported composition


7.  Use precomputes (Avid renders) and apply retimes to clips choosing this option will apply Nucoda retimes to clips with Avid Motion effects (no speed ramps) and use any available pre-computes (renders) that were in the sequence when the AAF was created. Please note, using this option will not allow a successful round trip.

8.  Expand timewarped clips and expand nested tracks - this option will replace any Avid retimes with filler on the timeline to represent the actual length of the timewarped clip, and will place the full source media on a separate track, with the start points of the clips at the same timecode. This allows for the grading of the source material which can be returned to the Avid. Nested effects are not supported, clicking the option will

     however split rendered Avid titles into Matte and Fill and place them on the timeline.


9, 10 Apply Pan & Scan to Master or Input FX layer - Please note that once applied, these effect will be rendered as part of the output file - in a round-trip scenario the effects will have to be removed from the sequence in Avid to avoid them from being resized a second time in the Avid.


AAF export dialog options: Export as part of a AAF Roundtrip workflow (only available if an AAF was imported to create the composition)


Export dialog.PNG    


  • The name and destination entered in the main file output area is the name and destination of the new AAF file that will be created (please ensure that the original AAF is always accessible since it is accessed during export.

  • Set any required handles  - if there is not enough the available amount will be exported.

  • Format options will vary depending on frame rate and resolution

  • MXF Export directory is the destination of the MXF files

  • Check in to Interplay  select this option to check the MXF files into Interplay (setup is in preferences)


Export MXF source files from Nucoda to Avid for relinking

    OP1a_Source.PNG


  • When doing source order export, names are auto generated, any names will be ignored if entered.

  • Avid Project  allows the user to use the original project name or specify a unique project name for the MXF files  - this is useful to sift files later. (Only in DNxHD formats)

  • For relink to work in AVID please ensure that the file has a valid and usable source file name that can be used as a relink marker along with TC - please note the correct setting to use in Media Composer is Start TC and Source FIle Name.

  • If you are exporting OpAtom for relinking after an AAF import you can use Start TC and Source ID

  • You may also need to select the ignore filename extension option when relinking.

  • Because Avid cannot reliably differentiate between files that are the same resolution, TC and Source, consider relinking to selected material or to place the new material on a different volume for relinking.

  • Deselect the option to relink only to material from current project


Export MXF OP-Atom from linked or re-conformed camera masters.

   
AAF timeline export


    OP1a_Source.PNG


  • When doing source order export, file names are auto generated, any names will be ignored if entered.

  • Avid Project  allows the user to use the original project name or specify a unique project name for the MXF files  - this is useful to sift files later. (Only in DNxHD formats)

  • Clip names from the AAF will not be retained if media has being re-conformed to original camera media

  • For relink to work in AVID the Nucoda Tape name will be copied to the TAPE field in Avid.

  • s a valid and usable source file name that can be used as a relink marker along with TC - please note the correct setting to use in Media Composer is Start TC and Source FIle Name.


  • You may also need to select the ignore filename extension option when relinking.

  • Because Avid cannot reliably differentiate between files that are the same resolution, TC and Source, consider relinking to selected material or to place the new material on a different volume for relinking.

  • Deselect the option to relink only to material from current project


Export MXF Record mixdown files to Avid


OP1a_Record.PNG


  • When choosing MXF OpAtom and Mixdown Record the user can specify a filename for the mixed down MXF clip

  • Selecting Generate AAF will create a new AAF referencing the new mixed down file in a Media Composer sequence.


  • The use case for this option is as follows:    

  • Import an AAF sequence that is complete, apart from grading, this includes audio tracks

  • The grade is performed

  • The files are exported as a single mixed down video file. A new AAF is created referencing the current audio and the new mixed down MXF file. The AAF contains a Media Composer

    sequence that can go directly to an Interplay ready for playout.AAF and Avid workflow changes.


Changes to Avid MXF Relink workflows


In this release we have made improvements to the Relink workflow when using  MXF OpAtom files, we have reinstated a feature that was removed in 2016.1 that precluded users  from relinking by Source ID,
it required a Tape Name or Tape Name data duplicate into the LabRoll,Camroll or Soundroll fields to relink against.


We have made a change that will now correctly use the Source ID from the original Avid MXF to ensure relinking is successful. Please ensure that the new exported material is exported to a new folder or volume to allow for easy relinking.

The Source ID field is also correctly propagated when using DNxHR (Larger than HD) resolutions allowing relinking of DNxHR sources as well.