Hi
Pokin around I found that Vegas 5 stores the prefs in a file called sfcdi.cfg
This file contains info on soundforge but also pointers to the dll used for bak files and retore.If you decide to look at this file make sure to open it a binary editor in read only mode.
I suspect if you have autosave checked that the entry point of the dll is faulty.
I will run spy++ and tell you more if I find anything.
Best Wishes,
Marty

Grobsie . .First thing I checked . .but thank you.

ezway - You don't know me? . . Do you? . . . "I suspect if you have autosave checked that the entry point of the dll is faulty. I will run spy++ and tell you more if I find anything." . . Now, you can tell me anything you like - ! However if it IS faulty, what happens next?

Thanks guys . .. yes? Guys?

Grazie

A bit off topic maybe but I use, and recomend, the free TortoiseCVS to save multiple versions. I have mentioned this software before because, to me anyway, having one file makes more sense than having hundreds. The autosave feature in Vegas is good, except seems lately it has been failing for people. With TortoiseCVS you just "update" a saved file with the latest one and if something goes wrong you just go in and dump out the version you want to restore.

The downside might be if you just are expecting Vegas to autosave your file every so often TortoiseCVS won't. You more or less have to do it manually. Not so much the saving part, but the updating part. But all is not lost - it is under GPL so any programmers out there (Edward?) who wanted to adapt this for Vegas use surely could, or maybe come up with a script that would interface with it. You can view update requests on the Sourceforge site. Either way Grazie I would say you have nothing to lose by taking a look. At the worst case you would use a combination of both. Off the top of my head you could set up your autosave directory as a CVS directory so each auotsave could than be updated. But you would still end up with multi files...which, for me, is the point of using TortoiseCVS to start with - to eleminate so many individual file (versions).

The time's that I've crashed/killed Vegas 5, upon restarting I get the question: The last time Vegas was run it was not shut down properly. Would you like to recover? (or something to that effect)

And yes, Edward, I should have used Excalibur to do my saving .. .


So will you start now??? (And, technically, that would be Neon) :-)

Not to stray too far here, but a related option is TortoiseSVN, built on Subversion which was designed to supercede CVS.

You can find free CVS and Subversion hosts, which add the benefit of off-site storage and the ability to pull down any version of your files to any Internet connected computer. I find these features indispensable now.

Hi Grazie,
No I don;t know you or your equiptment, but I have had the same problem, and found a logical solution.

Hiyah ezway, it was a rhetorical statement, to underline that if you DID know me you might appreciate the "depth" of my pc knowledge and abilities. And yes, I do appreciate your logical approach. However, for me, to get busy with an editor, in attempting to determine that - "the entry point of the dll is faulty." sounds way beyond my abilities and has already lost me.

So you did get a solution? Cool! - What was it? Would you think I can get Sony to issue me with a repair?

Thanks anyway,

Grazie

Hi Grazie,
Have you tried disabling the autosave option, perform a file clean up and then enabling it again?

1. Start Vegas
2. Disable autosave backup option in preferences.
3. Quit Vegas
4. Open Windows Explorer and browse to C:\Documents and Settings\YourComuterName\Application Data\Sony\Vegas\5.0
5. Delete the files in it. Minimize Explorer's window.
6. Restart Vegas and enable the autosave.option again.
9. Load a project and perform at least one edit. Don't save the project.
10. Wait five minutes. Vegas will create the ########.autosave.veg-bak file. (A veg-bak file is created or updated every five minutes if an edit-change occurs)
11. Restore Explorer's window to make sure that a new veg-bak file has been created.
Now crash Vegas using the method you mentioned in your post.

Is it working?

Some things I have noticed regarding the autosaved files:
When you quit Vegas, normally the program deletes the files in the above-mentioned folder. In some cases though, after a program crash for example, not all files are removed. IMO is a good practice to clean up any remains in this folder before starting working on a new project.

When Vegas is not the active window it won't create any veg-bak file (quite logical). A file will be created or updated as soon as Vegas window gets active again.
Depending…it will create a new veg-bak file or will update an existing one.

Vassias

Vassias -THANK you!

I've just done an analysis of the temp folder :

No. file: 297

Total Size: 61 mb

File size range: 13.3 mb > 1kb

Date range!: 19 March 2005 to 19 August 2004

BUT - some files, for example, created - 00000000.restore.veg 19-08-05 had been accessed again yesterday 19-05-05!?!?! Totally weird!

I did have an Undo/Redo Buffer issue back in September, and I think this is were it all stems from.
I've got loads of Vegas Undo and Redo Buffer *.tmp files that haven't been wiped.

So I did an experiment. I "Cut" all these files and put them in a "Pending" folder on my desktop. I then opened up V5 and WHILE keeping Windows Explorer open.

I did some brief Splits in V5 and noticed that the Undo/Redo buffer files get created - GOOD! I then went onto to "close" V5 WITHOUT saving and the newly created Undo and Redo TMP files got zapped away! - HAH! Well that appears to be working as should.

My thoughts are that since a re-invoked the Factory Defaults, thence supplying a PATH to temp folder for V5 - maybe - that at least the temp stuff had been used. BUT, there still remained a hiccup.

I'm going to keep an eye on this matter more closely. I would not like to think that as per my "normal" usage of V5 does seem to "kick-out" an issue that this too has sniffed out another too! - Anybody remember my Pan/Crop Locked Sync Cursor not allowing RAM Preview building?

I will attempt to recreate my "crash-dummy" process to force Vegas to fall over - this is when I alter the f/w supply or demand for my deck OR ext mon OR VidCap OR any combination of these 3!

Interesting . . . . but somehow a reet Royal pain in the BUTT!

Again, Vassias, thank you. I will experiment to ensure your advice is carried out:

"11. Restore Explorer's window to make sure that a new veg-bak file has been created. Now crash Vegas using the method you mentioned in your post."


Grazie