Having now done a little research on what, exactly, the AAF format is and having read the following about it:
AAF is designed to be a data representation of works in progress, as compared to MXF (Material Exchange Format), which is for exchanging finished media products
I have bolded the words that clearly state this is not for finished works, so can you tell us how the inclusion of this format would benefit users of VPX?
You need to be aware that Magix staff do not routinely visit the forum so may not see your request but I am genuinely interested in the benefits you see if export to AAF was included.
AAF is used to address interoperability in video production. VPX does not handle composoting well, and I would like to be able to move media easily between tools. As it currently stands, I am not even able to get the video project into Vegas without having to redo everything... this is a waste of effort and time. Not sue why the focus on "works in progress" is mentioned, as if VPX should always have to do all, till the rendering setp. What if I would like to choose to render in Vegas, due to speed differences? Also, we are living in a multi-vendor world and vendor lock-in is a no-no. VPX stands out already in other ways... and especially in ease of use...