AAF import to Vegas 8.0 error/crash

JMacSTL wrote on 2/9/2009, 12:59 PM

When attempting to import an AAf which was exported from an Avid (Media Composer 2.8.4) I usually get an "Exception" and then a list of error(s). It expands most, but not all, of the associated embedded wav files.

If I import this same AAF into ProTools LE 7.x, it opens just fine. Then I can select ALL, export as a NEW AAF, save, and then import this NEW AAF into Vegas 8.0 with no problems (except for loss of clip names.)

I'm guessing that ProTools is stripping out something that the Avid put in, or putting in something that Vegas needs to see. I have a dual boot system, and it takes several minutes to reboot into ProTools, do the re-save, and reboot back into Vegas on the same computer.

Anybody else see this? Here is a list of the actual error message:

Sony Vegas Pro 8.0
Version 8.0c (Build 260)
Exception 0xC0000005 (access violation) READ:0xCFAB00EE IP:0x6DC3D2
In Module 'vegas80.exe' at Address 0x400000 + 0x2DC3D2
Thread: GUI ID=0xEB4 Stack=0x133000-0x140000
Registers:
EAX=cfab00d6 CS=001b EIP=006dc3d2 EFLGS=00010282
EBX=0e3c77d0 SS=0023 ESP=00133adc EBP=00133bc4
ECX=cfab00d6 DS=0023 ESI=0e3c7c9e FS=003b
EDX=00000004 ES=0023 EDI=11223518 GS=0000
Bytes at CS:EIP:
006DC3D2: 8B 48 18 85 C9 74 15 8B .H...t..
006DC3DA: 50 04 85 D2 74 0E 8B 40 P...t..@
Stack Dump:
00133ADC: 006FA437 00400000 + 2FA437 (vegas80.exe)
00133AE0: 00000000
00133AE4: 11096BD8 11020000 + 76BD8
00133AE8: 05970060 05970000 + 60
00133AEC: 00133B28 00040000 + F3B28
00133AF0: CFAB00D6
00133AF4: CFAB00D6
00133AF8: 0000002C
00133AFC: 0E3C77D0 0E0CB000 + 2FC7D0
00133B00: 0F3B8060 0F190000 + 228060
00133B04: 00000001
00133B08: 00C1B67F 00400000 + 81B67F (vegas80.exe)
00133B0C: 00C1B67F 00400000 + 81B67F (vegas80.exe)
00133B10: 0000001F
00133B14: 0F294E60 0F190000 + 104E60
00133B18: 407EC9E1
> 00133B40: 7C90D950 7C900000 + D950 (ntdll.dll)
> 00133B70: 7C90F648 7C900000 + F648 (ntdll.dll)
> 00133BC8: 006E6E68 00400000 + 2E6E68 (vegas80.exe)
00133BCC: 11096BD8 11020000 + 76BD8
00133BD0: 00000000
00133BD4: 00000000
00133BD8: 0A6A5DB8 0A4F0000 + 1B5DB8
> 00133C64: 004914CD 00400000 + 914CD (vegas80.exe)
00133C68: 05970060 05970000 + 60
00133C6C: 00000000
00133C70: 00000001
> 00133C74: 7801168E 78000000 + 1168E (iertutil.dll)
> 00133C7C: 77F15B70 77F10000 + 5B70 (GDI32.dll)
> 00133C9C: 0047987A 00400000 + 7987A (vegas80.exe)
- - -
0013FFF0: 00000000
0013FFF4: 00000000
0013FFF8: 0084963B 00400000 + 44963B (vegas80.exe)
0013FFFC: 00000000

jmm in STL

Vegas 8.0c build 260
Custom built PC; Intel Quad Core
4GB RAM
Windows XP Pro

Comments

newhope wrote on 3/9/2009, 5:02 PM

Have you tried importing AAFs with referenced media, that is not embedded but all the media in a separate folder.

Even when dealing with AAFs from AVID in ProTools I use this method as it tends to produce less errors.

I don't usually import AAFs into Vegas but I happen to have one with referenced media here so I'll give it a try and post the results.

New Hope Media

newhope wrote on 3/9/2009, 5:48 PM

I experienced the same type of crash trying to import a referenced AAF.

Here is the report.

Sony Vegas Pro 8.0
Version 8.0c (Build 260)
Exception 0xC0000005 (access violation) READ:0x8B3A0FA IP:0x6FA0E7
In Module 'vegas80.exe' at Address 0x400000 + 0x2FA0E7
Thread: GUI ID=0x81C Stack=0x125000-0x130000
Registers:
EAX=0000001e CS=001b EIP=006fa0e7 EFLGS=00010206
EBX=00000000 SS=0023 ESP=00125d88 EBP=00125e68
ECX=001e4dd0 DS=0023 ESI=095e5030 FS=003b
EDX=08b3a0e2 ES=0023 EDI=00000000 GS=0000
Bytes at CS:EIP:
006FA0E7: 8B 42 18 8B 4A 20 8B 7A .B..J .z
006FA0EF: 1C 03 C8 89 44 24 28 8B ....D$(.
Stack Dump:
00125D88: 00000000
00125D8C: 06A9AE50 068F0000 + 1AAE50
00125D90: 068F0060 068F0000 + 60
00125D94: 01010070 00400000 + C10070 (vegas80.exe)
00125D98: 7C8CC400 7C800000 + CC400 (kernel32.dll)
00125D9C: 00000000
00125DA0: 00000037
00125DA4: 00000000
00125DA8: 00000000
00125DAC: 00000000
00125DB0: FFFFFFFF
00125DB4: 7FFFFFFF
00125DB8: 0000001D
00125DBC: 09631BC0 094C0000 + 171BC0
00125DC0: BF800AF2
00125DC4: 00000001
> 00125DD0: 7D255A80 7D1E0000 + 75A80 (msi.dll)
> 00125DD8: 0043608F 00400000 + 3608F (vegas80.exe)
00125DDC: 30010100
> 00125DE0: 00989680 00400000 + 589680 (vegas80.exe)
00125DE4: 00000000
> 00125DE8: 00435FC0 00400000 + 35FC0 (vegas80.exe)
00125DEC: 40012CEA
00125DF0: 000186A0
00125DF4: 00000000
> 00125DF8: 7D255A80 7D1E0000 + 75A80 (msi.dll)
> 00125E1C: 7E418E78 7E410000 + 8E78 (USER32.dll)
> 00125E34: 7E418E78 7E410000 + 8E78 (USER32.dll)
> 00125E40: 7C8CC400 7C800000 + CC400 (kernel32.dll)
> 00125E4C: 006EC9A1 00400000 + 2EC9A1 (vegas80.exe)
00125E50: 068F0060 068F0000 + 60
00125E54: 00000000
00125E58: 02714C30 025D0000 + 144C30
00125E5C: 068F0060 068F0000 + 60
> 00125E6C: 006E6E68 00400000 + 2E6E68 (vegas80.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 0084963B 00400000 + 44963B (vegas80.exe)
0012FFFC: 00000000

I'll import it into ProTools and do an export but I suspect it's just another case of SCS's poor implementation of AAF in Vegas that is to blame here. Another reason I don't try to do this regularly in Vegas.

I had another AAF problem with Vegas and a 5.1 project I was mixing.
I was delivered some ADR for inclusion in the project. The ADR had been done in ProTools as a stereo (well really mono) session. When I imported the AAF it reset my whole 5.1 project back to stereo. The only fix was to UNDO the import and output the ADR in ProTools as broadcast waves and import the BWFs into Vegas.

Another nasty glitch in the AAF implemntation in Vegas.

I'll post again when I have time to convert my AAF via ProTools and import it into Vegas.

New Hope Media

rraud wrote on 3/10/2009, 10:44 AM

I could only get one AAF to load properly from an Avid and never from FCP (via Automatic Duck) in numerous projects and finally gave up. I use to use an OMF conversion utility (now almost not affordable) and subsequently went to Sonar. Hopefully SCS will see the light and support OMF as well as BWF export in the next version of Vegas.. if there is one.

newhope wrote on 3/10/2009, 3:45 PM

Yep, like I said SCS have supplied a fairly useless implementation of AAF in Vegas.

By the way the AAF I am trying to import was exported from AVID specifically for audio post production. It's a referenced AAF with the media in a separate folder. I've opened it correctly in ProTools LE with a Mojo video interface at the broadcast facility where it was produced.

It contains a single video track in AVID MXF format which requires correct codecs for AVID video but, in ProTools, if the codec doesn't exist, as it doesn't in my studio, the program indicates that the video can't be imported BUT still imports the audio correctly.

As you can see from my previous post Vegas just fails to open the file at all and crashes... not impressive and another reason I can't in all honesty call Vegas a Professional application... it's great in what it can do but falls short in the professional arena.

New Hope Media

Geoff_Wood wrote on 3/11/2009, 9:27 PM

I guess it's not slightly possible that the app *writing* the AAF may be at fault ?

I've never had problems with open AAFs (embedded media or otherwise) exported from PT ( with ??? applet to export).

More than OMF and BWF, I reckon it would be a smart move to implement as fully as possible direct import/export ( or open/save-as) of Avid, PT , and other project files. Surely most of the stuff ( media files, timestamps, levels, plugs, fx, and other settings) are 'simply' translating a lookup table, or something like that ;-?

geoff

newhope wrote on 3/12/2009, 1:45 AM

I guess it's not slightly possible that the app *writing* the AAF may be at fault ?

No one could ever accuse me of being an AVID supporter and anyone who knows me would attest to that BUT...

As AVID are the originators of both OMF and AAF one would think that they may actually have the AAF format writing correct, not that they didn't change the goal posts for other NLE developers back in 90's when formalizing OMF. In fact I seem to remember that it took a few threats of legal redress from SMPTE before they released a usable format to other manufacturers.

Still if ProTools, another AVID product I confess, can open the AAF, I can't understand why Vegas can't do the same.

As far as opening a PT project, well EDL Convert does that and Convert Pro can do the latest versions. AVID is a different kettle of fish as their video format, OMF and MXF requires proprietary codecs which all cost money...

New Hope Media