Serial .VEG Saves + (Safe) Faster AutoSave?

Soniclight wrote on 4/22/2013, 7:20 PM
System: Win7 Home Premium
Sony Version: 10.x

At a recent thread I languished in the woes of two .veg that got corrupted during a system crash. I'm slogging through all the obvious and not-so-obvious remedies and have so far saved one (with some help from one of the veterans here...) But as Bob/Farss pointed out at that thread, time for me to do do incremental backups from now on. Live and learn.

So here is the plan:



Meaning, "TheBestVideoEver. veg" followed by "My BestVideoEver_01.veg, etc. etc.

I used to have a script from JetDV/Edward that did just that, naming each consecutive .veg numerically. At the time I didn't like the miles of .veg this created, but now I'd prefer to be save rather than sorry. I left a post at his forum but the participation seems up and down and I don't even know if he's around anymore.

So..

Q: What is that single script and where can I find it? I know it came or comes with Excalibur. But way-back-when I had briefly installed Vegas 6 or 8) it seemed like a freebie or a left-over one could keep. Too far back to recall.

Speed Up In-Vegas Autosaves

I found out that one can also tweak the Vegas internals to have the autosave .bak files happen more often. The default is 300,000. I set it too 30,000.

Q: Is that OK, dangerous or ? What is a good but faster/more often setting?

And last, a weird and probably no-go option:

Q: Is there a way to have "serial" .bak files made instead of .veg ones? If so, how?

Thanks.

~ Phil

Comments

riredale wrote on 4/22/2013, 7:59 PM
Perhaps simpler is better.

In my case, I do a veg save manually (ABCD26mar13 v07.veg, ABCD26mar13 v08.veg, etc.) whenever I've done a great deal of work and would scream if it was lost. Maybe twice in a 4-hour session.

Then I just leave the autosave at 300 sec (5 minutes). I think if you change the interval to every 30 seconds the program will be using significant resources just in saving itself over and over and over and over.
rs170a wrote on 4/22/2013, 8:50 PM
Phil, the autosave script is a part of Excalibur and, as I recall, Edward still recommends installing the trial version of Excalibur to get it as it remains active even after the trial version expires.
There's also Timeline Tools (free) and Vegasaur (paid) as discussed in the Sony...please enable autosave controls thread.

Mike
musicvid10 wrote on 4/22/2013, 9:00 PM
I support the feature request, and also have my own "autosave" feature.

Still running on an older system, when timeline editing begins to get sluggish (2 hrs. or so), I save my project, close Vegas, and reopen the project and continue.

For those who don't have a built-in clock as I do, configurable autosave would be a nice feature.
Soniclight wrote on 4/22/2013, 9:12 PM
Thanks for replies.

As to JetDV/Edward's script, I'll try the Excalibur trial route. I found the Vegas 8 version (AutoSave1-0-0.exe) in my bag of backup progs, plugins, scripts, etc.) -- not that it would do me much good since I don't use 8 anymore (installed but dormant and all my important .veg are v10-saved.)
riredale wrote on 4/22/2013, 10:50 PM
What makes the timeline get sluggish? Never seen that effect with V7 or V9.
johnmeyer wrote on 4/23/2013, 11:15 AM
What makes the timeline get sluggish? Never seen that effect with V7 or V9. I would have said the same thing, but over the past few years, I have become more sensitive to this issue, and I think it has been there for a long time (at least back to Vegas 7, which is still my workhorse -- although I use Vegas 8 about 25% of the time, Vegas 10 about 2% of the time, and Vegas 11 about 0.1% of the time. I never upgraded to Vegas 12).

In my case, I have tracked down the slowdowns to one of three situations:

1. I navigate away from Vegas and then return. This is only a problem if I have the preference set to allow other applications to modify media when Vegas does not have focus.

2. When the computer goes into standby.

3. I also think I have seen the problem when connecting/disconnecting external (USB) media drives. I've gone mostly to caddy-based plug-in SATA storage, so I see this less often.

Obviously all three of these scenarios involves releasing and then re-acquiring the file handles for each file in the project. Once the timeline performance slows down, as already noted, it simply won't speed up again, no matter what. Fortunately, as pointed out above, simply quitting Vegas and then re-opening the same project is all that is required.



As I've read all the posts the past few years about VEG corruption and media replacement, I've wondered if all of these things are related.
jetdv wrote on 4/23/2013, 12:29 PM
SonicLight - you're better off just installing Excalibur. Even if you never use Excalibur, the Auto Save option will continue to work. The current version has a much newer version of AutoSave than the old installer you have.