Access Violation in ac3 render

2G wrote on 5/2/2004, 12:10 PM
I am trying to render a project to ac3 format. (Vegas 5.0a) It gets to 17% and I get the error below. Has anyone else experienced this problem? Workarounds? I can give additional specifics re processor, memory, tracks in the project, etc.

Sony Vegas 5.0
Version 5.0a (Build 134)
Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x104BA8C
In Module 'vegas50k.dll' at Address 0x1000000 + 0x4BA8C
Thread: ProgMan ID=0x618 Stack=0x66EC000-0x6700000
Registers:
EAX=007e3e98 CS=001b EIP=0104ba8c EFLGS=00010246
EBX=00000000 SS=0023 ESP=066ec538 EBP=007e3af0
ECX=00000000 DS=0023 ESI=007e3b50 FS=0038
EDX=007e3b58 ES=0023 EDI=007e3b58 GS=0000
Bytes at CS:EIP:
0104BA8C: 89 01 3B 06 89 46 04 75 ..;..F.u
0104BA94: 0E 8B 76 20 85 F6 74 07 ..v ..t.
Stack Dump:
066EC538: 09903C60 098B0000 + 53C60
066EC53C: 007E3E98 00400000 + 3E3E98 (vegas50.exe)
066EC540: 00603037 00400000 + 203037 (vegas50.exe)
066EC544: 007E3B50 00400000 + 3E3B50 (vegas50.exe)
066EC548: 007E3E98 00400000 + 3E3E98 (vegas50.exe)
066EC54C: 09903C60 098B0000 + 53C60
066EC550: 007E4288 00400000 + 3E4288 (vegas50.exe)
066EC554: 77E75F93 77E60000 + 15F93 (kernel32.dll)
066EC558: 0060341E 00400000 + 20341E (vegas50.exe)
066EC55C: 00000000
066EC560: 007E3AF0 00400000 + 3E3AF0 (vegas50.exe)
066EC564: 00604B8F 00400000 + 204B8F (vegas50.exe)
066EC568: 09903C60 098B0000 + 53C60
066EC56C: 0000000E
066EC570: 09B6F7F8 098B0000 + 2BF7F8
066EC574: 066EC61C 06600000 + EC61C
- - -
066FFFF0: 00000000
066FFFF4: 004FA320 00400000 + FA320 (vegas50.exe)
066FFFF8: 007DF9C8 00400000 + 3DF9C8 (vegas50.exe)
066FFFFC: 00000000

Comments

2G wrote on 5/2/2004, 7:07 PM
Just a little more data on the error. I have five audio tracks. They are all continuous media (no breaks) except one spot where a time gap is removed from all five. Just ballparking, but it looks like that is suspiciously close to the 17% into the timeline where the error occurred.

Also, very repetitive with the AC3 renderer. I changed to WAV and created a temp WAV file without problem. Then rendered the WAV to AC3. So it appears to be a bug in the AC3 renderer.

2G