It's now 7:45. I rebooted the computer and manually started Vegas.

It reported, "Vegas didn't close correctly! Want to open a backup copy and resave?"

So I did.

The backup is frozen also, at 56% loading. So far I've wasted about an hour, and am nowhere near opening my project. I have one more backup copy of the project on another drive, but something tells me this won't open, either.

If there is a corrupted piece of media, wouldn't it be nice for Vegas to tell me which piece I need to fix or remove?

But nooooooooooo. It just sits there with that maddening blue "wait" circle spinning in perpetual circles while at the top of the monitor Vegas says, "(Not Responding)."

What kind of program doesn't "respond?" More importantly, why?

Use Resmon to see what Vegas is waiting for.

When the Windows Operating system can not kill a running task chance is that something is badly wrong in Windows - or in a device driver.

Have seen this with faulty usb devices hanging up programs that seemingly do not even use the device.

Don't trust a lot with "UNDO", this is usual for me in previous versions too (although I feel it is much better now in VP12?).

If you need to UNDO, the best thing is save or save as first, and don't do it too many times.

4hr edit with LOTS of undoing (client sitting over my shoulder - grrr). no problems at all.

m2t / wav / jpg

*just to add, i have edwards autosave on and before doing anything 'messy', ALWAYS save a new 'version'.

i have a rule. "Save" before undo.

i believe 5% of my "undo's" result in crash or freeze. so i avoid it like the plague.

I also have some rules.

Save progressive saves. If Vegas bombs out then save the backup as a new save.

I have run into a few disastrous crashes during an undo operation, and after looking at event and file timings started to suspect that undos that happened when an autobackup was taking place may have been the issue. No hard evidence, but since turning off Timeline Tools' incremental backup and just manually saving before undoing, have not had a crash on undo in several weeks. I had Timeline Tools set to backup every five minutes (yes, paranoia) which was probably overkill.

Still it's only anecdotal evidence and I still love Timeline Tools.

atom12, very interesting. I'm not sure how the Timeline Tools Autosave could be at fault unless Vegas itself allows the user to perform an "Undo" action simultaneously with saving a Project.

This is how the Timeline Tools Autosave behaves.

1. When the Autosave timer is fired, it checks the Vegas "dirty" flag to see if any changes have been made to the Project since the last time interval expired.
2. If no changes were made it does nothing. If changes have been made it proceeds with the backup.
3. it performs a programmatic Save of your project ( the same as if you pressed the Save button )
4. Then It then makes a copy of the newly saved project file with the current Date & Time appended to the name of the Project file copy.

If Vegas really does allow the user to perform an Undo action while saving the Project file, this problem could occur with any Autosave function in any Vegas Extension. Maybe the frequency of your autosave combined with the frequency with your "Undo" actions created the perfect storm of simultaneous Saving and Undoing. At least you had the backup from the previous 5 minutes to fall back on.

Hi Gary,
As I said, this is purely anecdotal, and even if it is occurring I certainly don't fault TT. So many of the oddities and unreproducible crashes with Vegas I am almost certain have to do with memory handling - perhaps RAM not being flushed/refreshed at the precise time expected or multi-threaded instructions falling out of order. This could be the case with an issue like this one, and it could be specific to RAM timings on the user side, I guess. I'm not smart enough to even speculate further.