VV Crashes?

eopco wrote on 6/22/2002, 9:58 PM
Hello All:
I am currently working on my first project on VV 3.0 It is a 4 minute music video with tons of FX's. I am nearly finished and have started to experiance problems. When opening the file, it crashes when I try to zoom all the way out. Is this a problem with my systems capacity? I have a PIII with 800 mgz, and 250 ram. As in JAWS, do I need a bigger boat? Any help would be appreciated.

Also, thanks Sonic Dennis for your help the other day. I rendered to a new track and got really smooth playback on the external monitor.

Later

Rich Krents
EOP Recording Co.

Comments

shaunn wrote on 6/23/2002, 6:58 AM
VV3 can crash? wwwowww I didn't know that! :) it's rare but apparently it can happen.
I don't think the crashes is cause by the CPU "slowness". Does it happen with that paticular file? or all projects you have work with?
What kind of OS you are running?

eopco wrote on 6/23/2002, 10:22 AM
It is happening with a paticular project file. I am using Win 98 SE. The problem is happening when I try to zoom out full. I have been able to render the file, but I would like to go in and make changes. I have also tried to save as a new file name and the same problem occurs.

Thanks for the help.

Rich
Chienworks wrote on 6/23/2002, 10:31 AM
Just as an experiment ... load the project and remove the first event (DO NOT SAVE!), then see if you can zoom out without crashing. If it crashes, reload and remove the second event .... repeat until it doens't crash (assuming that at some point removing an event keeps it from crashing).

If you find an even you can remove and have Vegas not crash, then probably that event was corrupted. Can you recapture/recreate that event?
eopco wrote on 6/23/2002, 10:57 AM
Thanks Chienworks, I will give that a try and see if it works.

eopco wrote on 6/23/2002, 12:46 PM
I tried removing tracks and it still crashes. The good news is that I have a saved file from the night before. The bad news is that I think I may have lost all of yesterdays work. Is there any way to retrieve yesterdays work. Also, what do you think may have caused this. This happened without warning. This is a major concern of mine, for I will have paying clients comming in and it will be very difficult and costly to loose projects like this. I was lucky on this one for this was an in house test run on music video's. Any help would be greatly appreciated.

Thanks:

Rich Krents
EOP Recording Co.
SonyDennis wrote on 6/23/2002, 3:07 PM
I've never heard of that happening. Are all of the media the same format?

Perhaps it is a driver bug with the video card? There is a known problem with some video cards in the "placement" tab of the text generator, for example. The fix for that is to turn off (or down) the hardware acceleration for your video card. Perhaps the same fix would help this problem. Good luck.

///d@
BillyBoy wrote on 6/23/2002, 3:17 PM
L o n g response...

I had a couple weird "corrupt" events in a project once. I have a fast system, huge hard drive capacity and lots of RAM, and otherwise Windows XP and Vegas Video are rock solid. So hardware, OS wise not likely what happened.

Instead of deleting events one after the other, not a option in my case, I'm talking hundreds of events, I isolated the "corrupt" events by identifying which ones they were. I doubt this is a "bug" in the true sense of the word by when I'm working on a unsually complex project where I have several video tracks and a half a dozen or more audio tracks with envelopes where I've added a considerable number of points to the events I discovered that during playback every once in a great while VV will hang after generating the can't mix audio... message.

If that happens it seems the TRACK not necessarially a particular event somehow gets corrupt. In my situation I had the audio on one track go way out of synch. I mean minutes out of synch! I found the "bad" track by one at a time muting the other tracks until I found the one that went bad.

The fix was actually simple. I just created a new audio track, dropped the entire contents of the bad track on to it and bang, no more out of synch or errors reported.

Don't know if it will work for you, still passing along what I ran this only once and it was only once. Go figure.
vitalforce2 wrote on 6/23/2002, 4:57 PM
Only way I've accidentally crashed VV3 was by capturing DV video through firewire, with external monitor (also through the firewire), then turning them both off after capturing, while still editing in VV3. When I closed VV3 it seems to have generated a Kernel32 crash--possibly I created a driver problem by interrupting the flow of IEEE data. But started right up again. Isn't it fine, though, being able to trade in an old NLE hot rod for JET WINGS?