hangup during render

Widetrack wrote on 2/28/2006, 11:50 PM

Help.

I have a one-hour program in a veg made up of nine nested vegs that won’t render.

I’ve tried increasing the virtual memory to 3000 MB, using the same disk the vegs are on for the page file. This trick worked a few months ago when I had the same problem, but now my render (to DV NTSC) hangs up repeatedly after about 3 minutes.

Win XP Pro V. 2002 Service pack 1
P4, 2.8 GHz
1 GB RAM
74 GB disk with OS, 25 GB free
200 GB disk for media, 39 GB free.

De-fragged both disks before this project.

Can anyone help?

I got this from “Details,” but I can’t interpret it

Sony Vegas 6.0
Version 6.0d (Build 210)
Exception 0x80000003 (breakpoint) IP:0x5C003F
In Module 'vegas60.exe' at Address 0x400000 + 0x1C003F
Thread: ProgMan ID=0x4B0 Stack=0x603E000-0x6040000
Registers:
EAX=1789af70 CS=001b EIP=005c003f EFLGS=00000206
EBX=01b90ea0 SS=0023 ESP=0603eec4 EBP=0603f408
ECX=067dd628 DS=0023 ESI=067dd628 FS=003b
EDX=0603eeec ES=0023 EDI=00000000 GS=0000
Bytes at CS:EIP:
005C003F: CC 33 C0 C2 08 00 CC CC .3......
005C0047: CC CC CC CC CC CC CC CC ........
Stack Dump:
0603EEC4: 006E51CD 00400000 + 2E51CD (vegas60.exe)
0603EEC8: 067DD628 06790000 + 4D628
0603EECC: 07A4E3A0 07890000 + 1BE3A0
0603EED0: 00000000
0603EED4: 17639810 163C0000 + 1279810
0603EED8: 006661D7 00400000 + 2661D7 (vegas60.exe)
0603EEDC: 0603EEEC 05F40000 + FEEEC
0603EEE0: 07A4E3A0 07890000 + 1BE3A0
0603EEE4: 17639800 163C0000 + 1279800
0603EEE8: 804733F0
0603EEEC: 067DD628 06790000 + 4D628
0603EEF0: 00000000
0603EEF4: 00000000
0603EEF8: 00000000
0603EEFC: 01B90EA0 01B20000 + 70EA0
0603EF00: 00000000
> 0603EF68: 77F7583E 77F50000 + 2583E (ntdll.dll)
> 0603EF6C: 77F56887 77F50000 + 6887 (ntdll.dll)
> 0603EF80: 77F5676E 77F50000 + 676E (ntdll.dll)
> 0603EF94: 77F7583E 77F50000 + 2583E (ntdll.dll)
> 0603EF98: 77F56887 77F50000 + 6887 (ntdll.dll)
> 0603EFAC: 77F5676E 77F50000 + 676E (ntdll.dll)
> 0603EFD0: 77F569DE 77F50000 + 69DE (ntdll.dll)
> 0603F004: 77F626D1 77F50000 + 126D1 (ntdll.dll)
> 0603F008: 77F62738 77F50000 + 12738 (ntdll.dll)
> 0603F00C: 77F627C7 77F50000 + 127C7 (ntdll.dll)
> 0603F02C: 77F628E9 77F50000 + 128E9 (ntdll.dll)
> 0603F030: 77F62738 77F50000 + 12738 (ntdll.dll)
> 0603F034: 77F627C7 77F50000 + 127C7 (ntdll.dll)
> 0603F06C: 01016F3D 01000000 + 16F3D (vegas60k.dll)
0603F070: 0603F160 05F40000 + FF160
0603F074: 0603F088 05F40000 + FF088
0603F078: 0603F798 05F40000 + FF798
0603F07C: 17641DF8 163C0000 + 1281DF8
> 0603F0A0: 7C34240D 7C340000 + 240D (MSVCR71.dll)
> 0603F0A4: 7C382358 7C340000 + 42358 (MSVCR71.dll)
> 0603F0B0: 7C36C289 7C340000 + 2C289 (MSVCR71.dll)
> 0603F0B8: 012456BE 01000000 + 2456BE (vegas60k.dll)
0603F0BC: 0603F0F8 05F40000 + FF0F8
0603F0C0: 0603F11C 05F40000 + FF11C
0603F0C4: 0603F138 05F40000 + FF138
0603F0C8: FFFFFFFE
> 0603F0E0: 77E7DD90 77E60000 + 1DD90 (kernel32.dll)
> 0603F0E8: 0107B4F7 01000000 + 7B4F7 (vegas60k.dll)
0603F0EC: 0603F11C 05F40000 + FF11C
> 0603F0F0: 012456A0 01000000 + 2456A0 (vegas60k.dll)
- - -
0603FFF0: 00000000
0603FFF4: 005024B0 00400000 + 1024B0 (vegas60.exe)
0603FFF8: 0098CDE8 00400000 + 58CDE8 (vegas60.exe)
0603FFFC: 00000000

Comments

Widetrack wrote on 3/1/2006, 10:45 AM

Can anyone please help me on this problem?

I posted it last night and got no replies. I'm trying to deliver it to a tv station for an april broadcast, but cannot get Vegad (6.0d) to render it.

Any suggestions on how to get a full render?

dat5150 wrote on 3/1/2006, 10:50 AM

Everytime I've had a render issue similar to yours, I trace it back to an overheated CPU. I upgraded the CPU fan/device and it went away. This is more likely to happen if you overclock.

johnmeyer wrote on 3/1/2006, 11:39 AM

My guess is that it is a bug in Vegas. I would recommend contacting Sony support (see link at the top of this page).

kdm wrote on 3/1/2006, 12:03 PM

I had a similar problem and it turned out to be a corrupt image file. Vegas would hang when rendering. May not be the same problem, but it's worth looking into.

Some of image files (digital photos) showed red error frames when putting them in the project, but only randomly, and infrequently, so I dismissed it as a fluke or misread on Vegas' part. I ended up editing and resaving all the image files to new filenames, replaced and all was well.

Widetrack wrote on 3/1/2006, 2:32 PM

Thanks for the suggestions. I'm not overclocked and it's preetty darm cold in my studio. I don't think a file is corrupt, since all the nested vegs render. I'll probably have to render each one separately, then put them together in a new project and Print from that. that's what I was doingf when changing the virtual memory worked last time. A pain, but it works.

Reporting it to Sony has to be worth a try.

Meantime, if anyone has an idea, please let me know.

thanks to all.

WT

rs170a wrote on 3/1/2006, 3:56 PM

FWIW, I had a similar problem recently (only bringing in one nested veg though, not nine) and the project would crash at various points during the render. A few emails with Sony later and my fix turned out to be an increase the number of render threads (originally set to 1). It's worth a shot.

Mike

Widetrack wrote on 3/1/2006, 4:15 PM

so you're saying I should increase the number of render threads to...what? as many as i have nested vegs?

rs170a wrote on 3/1/2006, 5:02 PM

I bumped mine up to 2 and it worked. For the heck of it, I tried it at 3 & 4 and those worked as well.

Mike

Paul Mead wrote on 3/9/2006, 11:57 AM

Personally, I would regard changing the number of threads a workaround, not a fix. The product still has a bug that needs to be fixed.

Steve Mann wrote on 3/9/2006, 2:56 PM

Probably not related but worth mentioning. If I have unused media in the "Project Media" window, my renders will sometimes stop at 99%. Not always, but enough to get into the habit of hitting the "Remove Unused Media" button before rendering.