I think that most people use AAF to After Effects.

I think that most people use AAF to After Effects.

Well, that would be funny… because it's meant for Avid Media Composer and Protools. :)

My opinion: almost nobody would use this workflow anymore.

I would still like to use XML export for sending to Resolve, but this has some flaws. Not sure if the issue is with Vegas' xml export or Resolve's handling thereof. (If you want to test, try exporting a set of still images and then changing the event length on a Resolve timeline. There are other issues with event fades, but these are less problematic.)

- Is this functionality useful for you?

- Do you use the import and/or export functionality?

No and no :)

Here also no

"Is this functionality useful for you?"
>> I would use it if it worked. (It never did import audio and the EDL timeline satisfactory mostly woruld not import at all., And gave up on it back in the SCS era. I actually have not MAGIX version of VP.

"Do you use the import and/or export functionality?"
>> I would use the import and export for audio if it was cross-application compatible"

"Does this functionality work as expected?"
>> Not in my experience

"What deficiencies does VEGAS have with the AAF functions?"
>> It never worked satisfactory for me to get audio post projects into VP from other NLEs. PP Avid MC, FCP, ect... When possible, I get an OMF and run though AA-Translator to convert to XML, Veg of Txt for VP. Somtimes I am forced to use 'SloTools'

"What is your work flow when using the AAF functions?"
>> Audio import for other NLEs (if it worked)

I'm a sound guy (Nuendo).

I usually receive AAFs from Avids and AAF/OMFs from Premier for all the TV stuff and and an AAF(for a guide temp FX and library music) and EDL3600 for the Dialogue compile ( also the AAF file in most cases can connected directly to the field recorder files ) for features.

Probably still important for exporting files to send to audio post.

Cheers

Hey Derek, thanks for asking the questions. That's awesome to have direct feedback.

AAF/OMF export is SUPER HELPFUL.

Especially for team projects where the audio mixer works on Protools or other software. I see it's missing from VP18 and would love to see it return to VP.

I'm currently searching for a workaround...

Just checking in here after finding it missing from 18. It wasn't perfect before but it was good enough for our needs. Be very keen to see this return as we edit in Pro tools and that feature disappearing has already led us to start looking seriously at premiere and resolve.

There should be some way of exporting audio for post-production to another DAW from Vegas.

No there is no easy way to do it.

I tried a lot of options of bringing my projects into Pro Tools or Nuendo.

Unfortunately only AAtranslater can do the work done or Vegas to XML, XML to Premiere, Premiere to OMF, OMF to Pro Tools, Pro tools to AAF, AAF to Nuendo. Sound silly but it works... :)

I'm running into this now and will repeatedly have issues working on multi-cam productions because of Vegas's inability to export AAF files so that audio can be handled by someone else. This seems like a necessity for any professional video editing platform. No way to output an OMF or AAF from Vegas? I'm currently trying to get an audio multitrack project out of Digital Performer and into Vegas. ...then out of Vegas and into ProTools. Any suggestions? If I purchase AA Translate will that do everything I need to do?

.."our team has some curiosity about the use of our AAF import and export functions..."

--

Your question is probably highly ironic, because in Vegas 18 there is NO AAF export OPTION. For me it is a very, very serious oversight on the part of the MAGIX team - how could you remove AAF from the export option and continue to call Vegas a professional program...???

Never use AAF, but XML is the most used functions I personally used to send the edit to colorist (Resolve).

And VEGAS Pro XML cant be translated to Resolve properly. I dont think its a resolve problem or Sony clip timecode problem. Its VEGAS Pro xml system is faulty.

I need to bring VEGAS Pro XML into Premiere Pro to "convert" the XML, and export out again the XML via premiere pro. Than only Resolve will import everything nicely 1:1 edit.

Need to use Pr to make sure VEGAS xml is working, otherwise it wont work.

And VEGAS Pro XML cant be translated to Resolve properly. I dont think its a resolve problem or Sony clip timecode problem. Its VEGAS Pro xml system is faulty.

We have had this discussion umpteen times before and I keep explaining that Vegas XML to Resolve DOES WORK, you are just doing something wrong. It almost certainly has to do with whether or not Vegas can read your Sony camera clips' source timecode. Try a different source file format to confirm this is true. Grass Valley is a good option.

If you think Vegas is incorrectly writing the XML than you need to define EXACTLY what the error is or nobody will ever be able to fix it.

I've a post about it before @Kinvermark https://www.vegascreativesoftware.info/us/forum/timecode-issue-xml-via-vegas-pro--128168/