Issue link: http://digital.copcomm.com/i/1010948
22 S U M M E R 2 0 1 8 C A S Q U A R T E R L Y NAMES AND INFO… I went into this looking to find a way for all data and metadata to translate across, including file name, source TC, destination TC, channel info, scene, and take num- bers as this is necessary to create a dialogue assembly. I exported the sequence as AAF and OMF referencing the source files. Here's what I experienced. OMF: As you can see in Fig._04, exporting as an OMF allowed the track names to transfer across (yay!) but did not carry across scene and take info or source timecode (boo!). Also, the OMF renumbered all the tracks as odd (1, 3, 5, 7, 9) and named the stereo music track as 11L/11R. If source TC, scene, and take info isn't that vital to you achieving the desired mix, this may be the way to go since it will retain original clip names. AAF – ENABLE MONO BREAKOUT: The AAF, on the other hand, imported with the following things being accurate: source TC, session TC, scene number, take number (see Fig._05). Interestingly, the name of the original file was replaced with the name of the video file, but included the file comment from the first track only. You can see the top blue track has the video track's name "Premiere_Test_Anim_Ref" but also includes what was in the channel field of the metadata "CH1_MonoMix_ NDF." For the poly WAV, all of the files retained the comment info from the first track "CH1_Lav1_NDF" instead of what their comments are in the original file (CH2_Lav2_NDF, CH3_Lav3_NDF, etc.). The files did retain the correct audio for their respective channel. Fig._04: OMF import results Fig._05: AAF import results with Mono Breakout Fig._06: AAF import results without Mono Breakout