Comments

TheHappyFriar wrote on 1/22/2009, 6:46 AM
render to DV AVI. When it crash's it won't erase the AVI, then you know where it stopped & you can look @ that area.
ritsmer wrote on 1/22/2009, 6:54 AM
It's not liking Windows :-)

If you Google this error message you will see that the "Memory could not be read" is an old, sporadic Windows error that has survived several attacs to kill it.

I have 5 PC's and see the error regularly, about 1-3 times per month - and in any program.
Brad C. wrote on 1/22/2009, 1:49 PM
So thats it?

Thats all?

haha
TheHappyFriar wrote on 1/22/2009, 6:42 PM
balking @ getting no answer when you asked a question with no content is pretty lame.
Brad C. wrote on 1/22/2009, 7:45 PM
TheUnHappyFriar"balking @ getting no answer when you asked a question with no content is pretty lame"

Relax man. I thought my question had plenty of content, just obviously not up to your standards.
Vegas stopped working......again. Imagine that. I get guys like you who typically help out by telling me to post what the messages said when it happened.

I did.

What more do you want?
fldave wrote on 1/22/2009, 8:12 PM
I see you have several .veg files in what I can assume is the project file list? So nested veg? HD or HDV also. Hmmm

I got away from large size nested veg files, memory management was not exact. I may have one in a project and just use less than a minute of footage now. GREAT idea, though.

Render the nested veg files to Cineform intermediate, replace in a copy of your project, and see if that fixes it.
Steve Mann wrote on 1/22/2009, 9:28 PM
Putting the program name in the error message is Windows' way to tell you that While running Sony Vegas, WINDOWS encountered this error.....

It does NOT mean that Vegas itself is crashing.

OTOH - I have noticed that nested projects in Vegas are very sensitive to any simple issues in the nested veg files. For example, a marker on the timeline past the end of the media will cause weird things to happen in the parent project.
Brad C. wrote on 1/23/2009, 5:08 AM
Here is the latest stoppage and this is after putting PNG's in place of the JPEG's:

http://i224.photobucket.com/albums/dd173/brizzad79/VegCrash-2.jpg

I'm going to try and render AVI to see exactly where its stopping so I can work on it.

Also, to address some comments above, I really don't know what "nesting" is yet to be honest. What you're seeing is my explorer tab and the .veg files are just other projects that I'm working on. (Don't know if that helps)
Brad C. wrote on 1/24/2009, 11:41 AM
UPDATE: Ok, so over the past couple days I've been trying to get this 3rd segment (.veg) to go through and no luck. Keeps shutting down @ 71%.

- I sent it through as an AVI file and it went right through and did not stop in the "problem" area. So that didn't really help me. I didn't like how the avi came out.
- I tried making tweaks anyway to some areas that I thought might have been tripping Vegas up. DIdn't matter......71% and done.
- I've tried png's instead of jpeg's.
- I've tried lower bitrates.
- I've tried shutting down other apps, etc.
- I even tried rendering sections of the project that might have been in the 70% area and they all went through without a hiccup.

This last time, when it reached 71%......Vegas just altogether disappeared. No messages, no freezing, no nothing. Just gone.

I remember someone stating before that one of my messages was eluding to the fact that it wasn't really a Vegas problem per-say, but a Windows/Vista issue shutting Vegas down. What else can I do to try and get through this? Is it timing out or something? Maybe a computer setting I should change?

Any other feasible work-arounds that won't compromise the footage and it blending with the rest of the video?