AAF out of Sync in Protools

Dear Shotframe

Looking at the AAF creation we can see there are re-timed clips and a conform rate applied in the FCPXML

Essentially X2Pro doesn't support retiming or conforming, and clips will be at the original speed in the AAF.

X2Pro does not modify the audio file, we will however modify the duration of a clip to match. If I give you an exaggerated example, if a clip is at half speed in the FCPXML we will double the length of the clip in the timeline in the AAF but we will not alter the speed of the audio. The notes in the sidecar text file is essentially a list of the start times of these re-timed clips so that it can be supplied to who ever is doing the audio finishing that they will have to look at retiming's or conform rates for those clips.

For the sequence TK101_V6_211018_PictureLock.fcpxml you will need to advise the sound engineer that they will need to look in the AAF at the following two points and adjust these two clips in ProTools.
• The retimed clip at 00:06:35.12 has been moved to role retimed-dialogue.dialogue-1
• The retimed clip at 00:06:34.12 has been moved to role retimed-dialogue.dialogue-1

A conformed clip is one that FCP X has automatically retimed because the frame rate of the clips was very close the the frame rate of the project. For example when a 23.98fps clip is used in a 25fps project, FCP X will play the clip at just over 104% speed. FCP X does not alert the user when it conforms clips. If you look in the library in FCPX you can sort clips by frame rate. As we are looking at creating an AAF with Audio only, then the issue with conform rates for different clips is essentially meaningless as frame rates only refer to the video.
tall-downtown-office-building-on-sunn-day-2-SBV-322156539-4K is 23.97
flying-over-red-tile-rooftops-of-a-southwestern-suburban-neighborhood-SBV-337954491-4K is 29.97

Hope the above helps.

Yours Sincerely

James

AAF created using X2Pro 4.5.6
See attached settings used.
All frame rates are 25fps.
Sync goes out progressively worse towards the end of the timeline in Protools.
Only workaround was using EDL.