And let that be a lesson to you .... *ALWAYS SAVE* before rendering. If you're making a few weird changes for just this render that you don't want in the main project then save to a different file name, but make sure you save!

Heck, i always tell people to save their word processor documents before they print, just in case something goes haywire with the printing process and the word processor or the computer crash.

Even better: Save, then Save As, incrementing the file name by 1; e.g., Save bongo.veg, then Save As bongo1.veg. Render bongo1.veg

Doing this always gives you a file to fall back on if the render or major editing change screws things up.

Jack

Ah, I remember when there was no Unix scourge upon this planet and things were actually designed to work well. Those were nice times.

Unix was all about making things simple. Everything was a stream. Your screen is a stream of bytes. Your file is a stream of bytes. Your socket connection is a stream of bytes. Your disk is a stream of bytes. Sadly everybody copied this idea. It wasn't perfect.

Old DEC systems had a great feature built in to the file system. Versioning. Every time you saved a file it only saved the delta between your previous version and your current version. You had file commands to create new versions, branches etc. It was most excellent. If you decided you had reached Nirvana with your file, you could clean it up with a simple command.

Now wouldn't that be great? Every time you worked on a project you could go back to the version "you know the one, the nice one from Wednesday". No need for software to support it, built straight into the file system.

Damned Unix.

Everyone's forgetting about jetdv's AutoSave command.
Vegas 8 Pro required.

Mike

Hmmm... I wonder how hard it would be to port that script over to V7 for us cavemen still using that version.

I've taken advantage of the built-in Autosave feature several times, but it would be nice to be able to customize the process, as this script does.

The stupid thing is, if you look up in the help documents the autosave function clearlystates that the program autosaves and keeps the autosave files until I quote the program is shut down and then they get erased. I searched the autosave temp folder and only found two autosaved files from months back. I have autosave on and it autosaves all of the time. When the computer rebooted it asked if I wanted to resume the last edit, I did and there were no edits saved. Hell the clips weren't even in synch. I had edited for 6 hours auto saving constantly and nothing. Strange that autosave wont store the autosave files for at least a week or so, Kinda useless if they disapear after the program is shut down. Anyway, I digress and im tired of bickering about it. In the end I should have done a save as. This is the first system shutdown I have experienced in years so I got too relaxed.

L.T.

Hmmm... I wonder how hard it would be to port that script over to V7 for us cavemen still using that version.

It is IMPOSSIBLE to convert it back to Vegas 7 because it is a custom command. Custom Commands are a great new feature of Vegas Pro 8.

My understanding about Autosave is that Vegas writes a veg file to a location of your choosing and keeps re-writing that file every 5 minutes. When you manually shut Vegas down it assumes everything is under control and the Autosave file is thus not needed, so it erases it. This implies that an Autosave file will only exist if something "bad" happened to make Vegas and/or the PC crash, which makes sense. Maybe the name of the feature should be changed from Autosave to "Rescue" to make it more clear that the role is not to make a bread crumb trail of the editing process but rather an emergency recovery function.