Comments

dtudela wrote on 1/9/2007, 9:50 AM
I am also having the same issue from time to time since I installed 7.0 (c) and haven't figured out the cause. The same series of events take place, 1st lose the transport function and Vegas stops responding and task managers indicates CPU usage 50% or better. The only way out for me is to end task and re-start Vegas. I also save my veg file often as not to lose too much. Sorry, I couldn't help!
Darrell
teaktart wrote on 1/9/2007, 10:04 AM
You are not alone!
I closed V7c the other night and the window stayed in chunks on the screen, yet didn't even show up on task mgr. Had to do a "push the button" to close the machine and reboot.
What type of files were you editing with at the time?

Teaktart
dtudela wrote on 1/9/2007, 10:24 AM
My edits were and are in most cases very simple with cuts, fades, generated media and minor color correction--nothing heavy duty. A few days ago I added another gig of ram on top of the 1 gig already installed and I did not experience the problem the last few times I used Vegas even though there were times I had three instances of Vegas open with one instance of Vegas rendering in the background. It's too soon for me to tell if the added memory did anything at all to fix the problem or if I have just been lucky the last few times I used Vegas.
jaydeeee wrote on 1/9/2007, 11:53 AM
fix: vegas 6d
dtudela wrote on 1/9/2007, 12:29 PM
Good idea jaydeee, except I jumped from V5 to V7. Glad I did.
Cooldraft wrote on 1/10/2007, 5:56 AM
I am usually editing avi files that are captured from scenalyzer.
Cooldraft wrote on 1/10/2007, 6:02 AM
This reminds me, I have 3 GIGS but I have seen "The memory cannor be read" when I exit Vegas on that system sometimes."
But wait this happened on my notebook also yesterday.
Cooldraft wrote on 1/10/2007, 6:04 AM
jaydee. No going back now! compatibility issues with down vegging. :)