AAF - No volume information

newhope wrote on 4/18/2005, 7:15 PM
I have just tried outputting an AAF file from Vegas and then reimporting it, as I don't have any other software to try it with that will open AAFs.

Every piece of media was back in place and the stereo audio was stereo interleaved ... yahooo ... BUT I didn't get any of the volume information that I would normally get from an OMF imported using EDL Convert via a Vegas script.

I thought AAF was going to support volume and pan information.

While I won't be exporting or importing AAFs with other Vegas users I had intended using it with other NLEs and DAWS like FCP, AVID and ProTools, where I currently use OMF and EDL Convert

Is there something I am missing because I've tried the Edit Protocol Compliant AAF, the AVID Legacy AAF and even embedded audio in the AAF all with the same result - no volume (level automation) info.

Steve

Comments

newhope wrote on 4/28/2005, 12:25 AM
Well Sony certainly have been silent about this post so far.

However I've now had the opportunity to test the 'wonderful' AAF import feature from another system. Specifically I tried outputting an AAF from a ProTools HD 6.4 system on which I had tracked and mixed a half hour doco for television.

I output the AAF from ProTools with AVID compatibility checked to make sure it conformed to frame boundaries.

NOTE this was an AUDIO ONLY AAF (no vision files as the vision was in AVID format and not compatible with Vegas)

I exported the media with 5sec handles from ProTools.

It imported into Vegas but supplied me with NO Volume information.
Yes it was on the tracks in the correct time and place, yes stereo was now dual mono (damn), but that I blame on ProTools but NO there wasn't any automation info.

If I export from ProTools as an OMF 2.0 file and convert it with EDL Convert Pro I get volume info which will automate in Vegas.
If I save the ProTools session as a ProTools 5.0 session I can open it with EDL Convert and export it as a Vegas Script. When I import the script into Vegas I get the media, volume and pan automation and keyframe levels.

I thought AAF was going to offer volume levels as part of the format. It certainly is meant to be able to do it.

Why is this important to me?

Because I want to be able to use Vegas for audio post on programs edited by other editors on other NLEs.

AAF was a potential way of exporting and importing the media directly.
However I find editors prefer to send the edit with their version of the mix in place using keyframe info. This allows me to play the tracks, when loaded into my DAW, and get an idea of what they intended. Certainly I'll change it during tracking and mixing but it gives the editors a way of demonstrating their intent for the audio.
AAF import and export not offering this basic facility makes it less than useful.

What has happened to it in Vegas?

Anyone from Sony care to comment?

Steve
SonyEPM wrote on 4/28/2005, 9:35 AM
The scope of what is supported in our first AAF implementation is discussed here:

http://mediasoftware.sonypictures.com/forums/ShowMessage.asp?ForumID=4&MessageID=383308

Your posts is helpful as we look toward next step implementations of project interchange, and hopefully other will post with their specific needs.
BrianStanding wrote on 4/28/2005, 10:08 AM
Sony:

Is Sony planning on doing a White Paper on AAF support, and other V6 New Features, like they have with new features in the past?

Or at a minimum, can you make posts that include this kind of info a sticky?
jlafferty wrote on 4/28/2005, 10:33 AM
Good suggestions. A white paper would be great -- especially if it was clearly laid out, showing side-by-side Vegas and Avid screenshots to demonstrate "typical" projects across platforms, and to highlight the various "wills and won'ts" of AAF.

Not saying this has to happen yesterday -- but to know it will be coming in a month or so would be nice...

- jim
newhope wrote on 4/28/2005, 4:56 PM
Sony
Thanks for making that clearer.

My interpretation of AAF in Vegas is that it is about the equivalent of OMF 1.0 (not OMF 2.0) and not particularly useful to me.

That being the case I'll stick with EDL Convert Pro and import/export OMF 2.0 for generic NLEs and ProTools 5.0 et al for the specific DAWS that EDL Convert supports directly.

It's a shame that the Vegas implementation of AAF left out some of the basic features that OMF 2.0 supports. I can only hope we won't have to wait for Vegas 7.0 for this to be rectified.

Steve
vitalforce2 wrote on 6/5/2005, 2:05 PM
Sorry about the extremely late reply to earlier answer on my comments about sending a Vegas project to an Avid/ProTools editor. The answer to "why do that?" was that I have no bargaining power with a particular 'Big Name' editor and so am trying to make the interface between my Dell XP/Vegas?SF8 system and his ProTools setup as painless as possible.

Also, his partner (a film editor who is coaching me through the final cut) recentlyy asked me if I can "send him an OMF file." I assume I can't but guess I'll have to look into some software like OMF and EDL Convert.