MC AAF export changed in 2018.10?

[ErikGuldager]

Did MC AAF export change in 2018.10?

I read that since the last few releases it is required to have MC/PT at the same version level because of AAF inconsistencies.

We have had a few issues lately where PT just wouldn't link up som files in the AAF properly.

I read about it on gearslutz, and as we are in the process of updating the last few MCs to 2018.12 we may be starting to see this issue creep up.
I just want to know more.

Links to any info appreciated.

[AndrewAction]

Originally Posted by ErikGuldager

Did MC AAF export change in 2018.10?

I read that since the last few releases it is required to have MC/PT at the same version level because of AAF inconsistencies.

We have had a few issues lately where PT just wouldn't link up som files in the AAF properly.

A known bug MCCET-2825 causes some AAF exports with embedded media from recent versions of MC did not to import correctly into PT's 12.7.1 and earlier.
Chatter in the MC forums around the time of the last MC update suggested that a fix for this, though not in the last release (MC 2018.12.1), was being worked on and could be expected soon.

Andrew

[AndrewAction]

Todays update I have not tested this yet but the readme with MC 2018.2, released this morning, indicates the problem is resolved.

Bug Number: MCCET-2825. An AAF embedded export from Media Composer did not import properly into Pro Tools v12.7.1 and earlier.
If you experience this problem, enable the “ProTools 10/12 compatibility” option in the Export As AAF dialog. The exported AAF will be compatible with earlier versions of Pro Tools.

Note This does not apply to AAF's exported with linked media

Andrew