but it likely won't work. I've never gotten this to successfully work. It also won't import many AAFs (from Premier, or Avid, for instance). I always have to use ProTools to open an OMF or AAF, then export it out as a new AAF, which vegas then happily imports...EXCEPT for the fact that it still splits stereo audio files (i.e. music tracks) as split mono.

I concur with flyerstl, "it likely won't work"

Ever since Vegas originally incorporated the AAF protocol, (VP-6 I think) I could never get to work right or consistently (export or import). I use OMF.. (at least when I can).. and can work around the drawbacks like file size limits ect, Unfortunately VP never supported OMF, so I used a third-party converter app. was necessary. I used the CubonoSoft converter until SSL acquired it, (then demanded (ransom) 3x the original cost to reinstall). I currently use AATranslator.

This too is a MAJOR problem for me. I want to sing the praises of Vegas Pro for feature film audio post but I hesitate because any time I have to work with AAFs and Vegas Pro "it likely won't work" comes into play. And when it does work there are subtle and insidious problems that crop up (everything looks fine but many Timeline Events are slipped out of sync - differently for each track and a variable amount per Event - so there is no fix that doesn't take weeks of manual syncing that I have found yet). I hope it we can solve this! I'd love to keep working in Vegas Pro for future large projects!

Both of these formats (OMF & AAF) are self proclaimed standards that never should have been created.  Although the container format is always a standard, the methods of describing data within the container are not.  They each have multiple ways of describing the same thing and since everyone has a slightly different way of doing things within the containers, they might as well not exist at all.  To call them any kind of standard is really a joke.  OMF is literally a format within a container format.  AAF (and MXF) are much worse because they are a format within a container within a structured storage format.  

Take for example ProTools and Media Composer each has their own 'standard' for both AAF and OMF and they are both very different animals. While PT for example can read an MC AAF it barely supports most of what is written into that AAF while a totally unrelated entity like Nuendo can read far more detail from an MC AAF than Avid's ProTools - go figure.

So try not to be too hard on the Vegas devs as this is not an easy sandpit to be playing in.

You are right SuiteSpot. I was exasperated when I wrote the comment above. Thanks for taking the time to explain AAFs better. I did think it was an actual standard where issues arose from different software just functioning differently and needing to translate and interpret the standard. I'll do some research and learn some more about AAFs. I'm not surprised however; when I export complex projects with Premiere Pro into AAF - it throws errors when importing the AAF it just generated!

Premiere is not the only DAW with that issue I can assure you ;-)

Feel free to contact me directly (info at aatranslator dot com dot au) should you need more info or assistance on a particular AAF or AAF related matter

Thanks for the contact. I wish I was aware of AA Translator 3 months ago.

Shhhh, it's one of the industry's best kept secrets ;-)

AA Translator works well with VP, offering a few EDL import/export option types.Prior to AAT, I used the Cui Bono Soft converter which became unaffordable when it acquired by SSL.