VMS 8.0b dies a horrible death...

ProRauder wrote on 10/2/2007, 7:49 AM
First let me say thanks to everyone that has helped me get past my last two problems with VMS and in both cases they were easy configuration options changes. And to be fair, there are a LOT of options!

Now the current problem.

I have started putting together my DVD for the footage I recorded during HOT ROD Magazine's Drag Week 2007 in which I participated. My problem is that VMS freaks out and crashes when I drag all of the video clips to the Video Bar. I probably have somewhere around 230 clips totalling 11.3 GB of MPEG2 footage I am adding.

I suspect that it is a memory issue. I have 2GB of memory in my Dual Core Dell and watch the Physical memory climb in the Windows Task Manager to 1.8GB and hang there for a long time.

And while we're talking about memory usage in VMS 8.0b, why does it seem to allocate so much memory to the project (relative to the number/size of the clips and then free that memory when the window loses focus, then have to rescan and reallocate again when it again focused? For example, I have half of the 320 clips in there and while I type this message in the browser, my memory sits at 668MB. I click on the VMS window and it takes 96 seconds to remove the hourglass while the memory pegs out at 1.99GB During that time it is totally unresponsive. As soon as I click back in the browser to continue typing this message, the entire block of memory is freed. If I go back to VMS I then have to wait that 96 seconds before I can do anything.

Also, it appears not to accept more than 255 clips at one time. Anything over this number just appears as (media offline) when it is not. What is the magic cure for this, do I merge clips together?

There, enough ramblings while I search for solutions.

John

Comments

ProRauder wrote on 10/2/2007, 8:13 AM
And here is the horrible msg:

An error occurred during the current operation.

An Exception has occurred.

Sony Vegas Movie Studio Platinum 8.0
Version 8.0b (Build 122)
Exception 0xC0000005 (access violation) READ:0x8 IP:0x738DE8
In Module 'VegasMovieStudioPE80.exe' at Address 0x400000 + 0x338DE8
Thread: GUI ID=0x2FEC Stack=0x12D000-0x130000
Registers:
EAX=2842dc48 CS=001b EIP=00738de8 EFLGS=00050206
EBX=287a5d88 SS=0023 ESP=0012d324 EBP=105c9934
ECX=29b37a10 DS=0023 ESI=29b37a10 FS=003b
EDX=00000000 ES=0023 EDI=00000000 GS=0000
Bytes at CS:EIP:
00738DE8: 8B 42 08 FF D0 89 BE A0 .B......
00738DF0: 00 00 00 8B 86 A8 00 00 ........
Stack Dump:
0012D324: 2842DC48 27AF0000 + 93DC48
0012D328: 00000002
0012D32C: 00000000
0012D330: 00730311 00400000 + 330311 (VegasMovieStudioPE80.exe)
0012D334: 09973C60 09620000 + 353C60
0012D338: 287A5D88 27AF0000 + CB5D88
0012D33C: 00000000
0012D340: 00732AC6 00400000 + 332AC6 (VegasMovieStudioPE80.exe)
0012D344: 00000000
0012D348: 287A5D88 27AF0000 + CB5D88
0012D34C: 287A5D88 27AF0000 + CB5D88
0012D350: 0072C5DD 00400000 + 32C5DD (VegasMovieStudioPE80.exe)
0012D354: 09973C60 09620000 + 353C60
0012D358: 105C9934 10460000 + 169934
0012D35C: 2841F6B4 27AF0000 + 92F6B4
0012D360: 00000000
> 0012D36C: 0072C809 00400000 + 32C809 (VegasMovieStudioPE80.exe)
0012D370: 0966E764 09620000 + 4E764
0012D374: 105C9934 10460000 + 169934
0012D378: 00000000
0012D37C: 105C9934 10460000 + 169934
> 0012D384: 0072BCF4 00400000 + 32BCF4 (VegasMovieStudioPE80.exe)
0012D388: 2841F6B4 27AF0000 + 92F6B4
0012D38C: 00000000
0012D390: 00000000
0012D394: 00000001
> 0012D3A4: 0044AEE9 00400000 + 4AEE9 (VegasMovieStudioPE80.exe)
- - -
0012FFF0: 00000000
0012FFF4: 0093A2EB 00400000 + 53A2EB (VegasMovieStudioPE80.exe)
0012FFF8: 7FFD4000 7FFD4000 + 0
0012FFFC: 00000000
Ivan Lietaert wrote on 10/2/2007, 10:49 AM
Yesterday I dragged 7GB of files to the timeline, with only 512MB ram on board, and VMS works just fine. So ram is not the issue here. My guess is you must make sure that the partition you work in has enough free space for VMS to cash. Make sure you check the paths in preference, esp the temp path to go to the right partition with enough free space. You find it at 'preferences' <General (at the bottom).
routerguy99 wrote on 10/2/2007, 1:48 PM
Applications that attempt to violate DEP will receive an exception with status code STATUS_ACCESS_VIOLATION (0xC0000005).

If an application requires executable memory, it must explicitly set this attribute on the appropriate memory by specifying PAGE_EXECUTE, PAGE_EXECUTE_READ, PAGE_EXECUTE_READWRITE or PAGE_EXECUTE_WRITECOPY in the memory protection argument of the Virtual* memory allocation functions.

It is possible to "Turn Off" DEP in the boot.ini file
/NOEXECUTE