Reply To: X2Pro5 writes inaccurate, self-contradicting source timecode into embedded AAF

› Forums › X2Pro5 forum › X2Pro5 writes inaccurate, self-contradicting source timecode into embedded AAF › Reply To: X2Pro5 writes inaccurate, self-contradicting source timecode into embedded AAF

#1581
James Carrick
Keymaster

    Just an update for everyone to see what is going on, as we have been talking to Cinexpert directly.

    We looked at the XML and yes there is a difference between what is seen in FCP and what is seen in ProTools. The reason for this is that some of the media files have different lengths for their Video and Audio. i.e. clip 1, the audio was 5 frames shorter than the video. clip 2, the audio started 2 frames after the video started. The media is unusual but should not be considered exceptional. In a FCPXML it copes with these discrepancies by leaving holes. An AAF by contrast must be continuous so we should be padding these holes in the AAF, we are but instead of using the calculated filler duration we are only applying a 1ms pad. We are working on a fix for this and will advise shortly.

    Yours sincerely

    James.

    Scroll to top