VMS Crashing During Rendering

BobF wrote on 3/12/2010, 10:17 AM
Trying to re-render an old project to a file type compatible with VirtualDub so I can run it through a deflicker filter. VMS is crashing during rendering. At what point in the rendering varies. I've tried different file types and different codecs. The first few times, the program simply crashed without warning or error message. Tried creating a new project, re-importing the media and rendering, no luck. Tried uninstalling and re-installing the program, no luck. The only difference after re-installing the program was that I did get an error message. The details are pasted below.

Vegas Movie Studio Platinum 9.0
Version 9.0b (Build 92)
Exception 0xC0000005 (access violation) READ:0xFF6C6084 IP:0x6B4EEE
In Module 'VegasMovieStudioPE90.exe' at Address 0x400000 + 0x2B4EEE
Thread: ProgMan ID=0x510 Stack=0x5DAF000-0x5DB0000
Registers:
EAX=05a214c0 CS=001b EIP=006b4eee EFLGS=00010202
EBX=02a58ae8 SS=0023 ESP=05daf78c EBP=00000001
ECX=ff6c6060 DS=0023 ESI=05968138 FS=003b
EDX=0caf94d8 ES=0023 EDI=00184b78 GS=0000
Bytes at CS:EIP:
006B4EEE: 8B 41 24 FF D0 85 C0 74 .A...t
006B4EF6: 0B 83 C5 01 3B 6C 24 10 ....;l
Stack Dump:
05DAF78C: 05A214C0 058B0000 + 1714C0
05DAF790: 0CAF94D8 0C970000 + 1894D8
05DAF794: 0CAF94D8 0C970000 + 1894D8
05DAF798: 9B0A9F0D 80000000 + 1B0A9F0D
05DAF79C: 058EC348 058B0000 + 3C348
05DAF7A0: 05BAFCEC 058B0000 + 2FFCEC
05DAF7A4: 00000025
05DAF7A8: 00000006
05DAF7AC: 00000004
05DAF7B0: 00000000
05DAF7B4: 00184B84 00150000 + 34B84
05DAF7B8: 006AD58E 00400000 + 2AD58E (VegasMovieStudioPE90.exe)
05DAF7BC: 0CAF94D8 0C970000 + 1894D8
05DAF7C0: 00000000
05DAF7C4: 0CA85598 0C970000 + 115598
05DAF7C8: 058EC348 058B0000 + 3C348
> 05DAF7CC: 006AE1F6 00400000 + 2AE1F6 (VegasMovieStudioPE90.exe)
05DAF7D0: 05BAFCEC 058B0000 + 2FFCEC
05DAF7D4: 9B0A9F0D 80000000 + 1B0A9F0D
05DAF7D8: 0CA85598 0C970000 + 115598
05DAF7DC: 00000000
> 05DAF7F0: 006CA4C4 00400000 + 2CA4C4 (VegasMovieStudioPE90.exe)
05DAF7F4: 05BAFCEC 058B0000 + 2FFCEC
05DAF7F8: 9B0A9F0D 80000000 + 1B0A9F0D
05DAF7FC: FFFFFFFF
05DAF800: 0CA85530 0C970000 + 115530
> 05DAF80C: 006C34D3 00400000 + 2C34D3 (VegasMovieStudioPE90.exe)
05DAF810: 0CA85508 0C970000 + 115508
05DAF814: 00000000
05DAF818: 00000001
> 05DAF81C: 006C3EBA 00400000 + 2C3EBA (VegasMovieStudioPE90.exe)
05DAF820: 0CA85508 0C970000 + 115508
05DAF824: 021FF11C 02120000 + DF11C
> 05DAF828: 006C3E9C 00400000 + 2C3E9C (VegasMovieStudioPE90.exe)

Is this a matter that the registry entries didn't get completely cleaned out when I uninstalled and I need to do a manual delete? Is it something else entirely? I'm running an AMD 2GHz dual core processor with 4GB of RAM and the 3 gig switch turned on in boot.ini on a WindowsXP Pro SP3 system. GPU is an nVidia GeForce 7600 with 256Mb of on card RAM. I've tried changing the memory usage in VMS as well as 1 and 2 thread rendering.

As an aside, is Sony even still in the video editing game? v9 of their various apps have been out for a couple years now at least.

Comments

PNguyen wrote on 3/12/2010, 3:22 PM
Did you try the steps mentioned in any of the 'How to Fix Render..' threads?
david_f_knight wrote on 3/12/2010, 3:36 PM
I'm assuming you are running a 32-bit version of Windows XP Pro SP3. If not, then you shouldn't have the /3GB switch in your boot.ini file. Have you also set the >2GB virtual address space flag in certain executables? See this for how with 32-bit Windows XP.

I don't think your problem has anything to do with uninstalling and then reinstalling Vegas, or the Windows registry.

Yes, Sony is still in the video editing game. Vegas Pro 9 was released October 2009. The Vegas Movie Studio 9 products were derived from Vegas Pro 8 I believe, which was released September 2008. Vegas Pro is the flagship in Sony's video editing lineup, so it's going to tend to be the first out of the gate. The customers paying the premium price deserve the first shot at new features and technology. By the way, it seems that Vegas Pro 9 does work much more reliably than Vegas Pro 8 with certain codecs, so it is probably reasonable to expect that the Vegas Movie Studio 10 products will be more reliable, as well, since they will presumably be derived from Vegas Pro 9.
Eugenia wrote on 3/12/2010, 4:06 PM
What codec is your footage using out of virtualdub exactly?
BobF wrote on 3/13/2010, 5:58 AM
The file hadn't made it into VirtualDub yet. I was trying to re-render into a format that VirtualDub can use because the original files were WMV and MP4.

No, I haven't turned on the addressing of >2GB in VMS. The 3 gig switch is turned on for Photoshop to be able to access greater amounts of RAM. I noted it because it is turned on and is a part of my computer configuration. PS is not running when trying to render so shouldn't be taking memory away from VMS. I would think 2 gigs should be sufficient for VMS. And yes, it is the 32 bit version. There's no need to turn the switch on in the 64 bit version.

I was able to render in a trial version of Vegas Pro. It seems that the problem may be the way VMS handles still images (vs. video). Though not sure why it worked in the past. Maybe I got lucky.
david_f_knight wrote on 3/13/2010, 8:42 AM
The issue with the /3GB switch and the >2GB virtual address space flag isn't about the amount of RAM that an application can use, but about the allocation of its virtual address space. The render bug has absolutely nothing to do with the amount of RAM that Vegas has available to it. This isn't a performance issue. Memory allocation and usage, from the operating system point of view, is far more complex and sophisticated than what you're imagining it is. Since modifying the >2GB virtual address space flag in certain Vegas executable files is quick, simple, free, and reversible, and has been effective for a number of users, I suggest that you give it a try before deciding that it can't help you.

If the trial version of Vegas Pro that you used to render your video was Vegas Pro 9, then that isn't a fair comparison, because Vegas Movie Studio Platinum 9 is derived from Vegas Pro 8 apparently. Vegas Pro 8 has the same render bug as VMS Platinum 9, but it seems to have been fixed in Vegas Pro 9.