Vegas v6.0b - AAF still exhibits problems

norgeworks wrote on 5/26/2005, 10:25 PM

Checked the changelog and AAF didn't seem to be addressed in this go around. Fair enough, but I just want to reiterate how important AAF would / could be to me--and others. I haven't heard anything back from the Sony tech's I was dealing with, so I'm hoping this is still a priority.

The issue(s) are:

-incorrect .dll is still used--package should be updated to include the working .dll
-importing "linked to" AAFs from Avid results in some media appearing offline for no reason, and most of the others are the correct clip, but the wrong in/out points.

Still unusable. =(

Hoping this gets addressed in v6.0c...it *is* bullet-point number four after all.

Comments

beugnet wrote on 5/27/2005, 12:58 AM

I second that.
AAF export is pretty much useless to me as it is.
It would be an awsome asset if it worked...

Beugnet

PlanBlue wrote on 5/27/2005, 2:14 AM

..me too!

AAF could be a very usefull point for integrating vegas in the production line - but not like is it handled now.

- AAF import imports no Clip-Names, no Clip-Gain, no Fades
- the packaged AAF-dll is 1.0.2. Current AAF-SDK is 1.1.0; since the file format has changed slightly that means, that you can NOT read AAF files created by systems using AAF 1.1.0

hopefully
Michael Feller

B_JM wrote on 5/27/2005, 5:49 AM

yes - since it was a simple fix i found for that - i'm not sure why it was not included in this last go around.. but even then , it needs some work ... then again- it doesnt even work properly between different avid systems and such either ..