i have been saving under a different name on a new folder... i'm using the project as a template

Your original file should not be changing unless you are either 1) Saving it without changing the name or 2) Overwriting it with the same name

i open the project ( AWARDS TEMPLATE), i edit what i need , and save as ( rock award). when i open up again ( AWARDS TEMPLATE), it will have all the changes i made to the rock award.. very weird

>>i open the project ( AWARDS TEMPLATE), i edit what i need , and save as ( rock award).

Normally, you would want to be saving your project veg file as you go along making edits. For most of us, this is a habit. So -- you would want to do your "save as" BEFORE making any edits to the new project. This would allow you to save your new veg file under the new file name as you make edits, without changing the original file.

So -- there is some chance that you've been saving your original veg as you make changes, and then doing the "save as" AFTER all the edits are completed. This would be the reason then that the original file contains all the changes.

Seems fundamental, but could be a solution to what is otherwise a very very weird problem.

When you say you made a project a template, how did you do that? Is it just an ordinary project that you use as a starter over and over? I do this sort of thing all the time and don't have the problem you describe.

I tend to do the last thing david-tu mentions, not just in Vegas, but with all file types in all the software i use. It just seems to be the safest method. The problem that floriano-cabral is having is most likely due to Vegas' autosave feature, which kicks in every few minutes while editing.

I'm not entirely clear on what ".autosave" vs ".restored" files are doing these days. In VP14 here's what help says about it.

A backup copy of your project is automatically saved every five minutes. If your system crashes, you will be prompted to open the backup file the next time you start the application. ( Isn't this done from the .restored file, not the .autosave or .veg.bak?)

Backup files are saved in the location specified in the Temporary files folder box on the General tab of the Preferences dialog. Files are saved with the .autosave.veg extension and are deleted when you exit the application. For more information, see "Preferences - General Tab."

I don't think you really save your project until you do a save yourself. I know your .veg.bak files are created when you do a save, not when Autosave does a save.

I'm pretty sure it does save to the original project file at some point. I've had Vegas crash on me (rarely), and when i open up the .veg file again all but my most recent changes are there.

I agree Kelly, when you crash Vegas the .restored file may have your most recent changes -- That file has saved me in the past - - but I meant if you don't crash and you close the file. If you don't do a save before closing Vegas, nothing gets saved. This has helped me too when I've gotten things so messed up I don't want to save. I would not expect autosave, at some unknown point, to save my original .veg.

So if you do save and close Vegas, then find later that your file will not open again, there's no .autosave since it was deleted when you closed Vegas, and there's no .restored file since you didn't crash. You will have a veg.bak file and that should save you -- but in the case of the OP, it did not. This could mean that Vegas does not prevent you from saving a file that will not reopen later because of some fatal error. -Paul

"xberk wrote on 01/21/2017, 12:11 PM

>>i open the project ( AWARDS TEMPLATE), i edit what i need , and save as ( rock award).

Normally, you would want to be saving your project veg file as you go along making edits. For most of us, this is a habit. So -- you would want to do your "save as" BEFORE making any edits to the new project. This would allow you to save your new veg file under the new file name as you make edits, without changing the original file.

So -- there is some chance that you've been saving your original veg as you make changes, and then doing the "save as" AFTER all the edits are completed. This would be the reason then that the original file contains all the changes.

Seems fundamental, but could be a solution to what is otherwise a very very weird problem."

i tried, what u suggested, and it did not work... very weird, i even copy to a different folder on a different drive... oh well... more work thank you guys for trying to help

>>i tried, what u suggested, and it did not work

If doing a save as using a different file name does not work, then this is truly "spooky action" .. No disrespect intended, but It's like your describing the quantum world where we have "entanglement" between pairs. I assume, the rest of us here live in the world of classic physics where a "save as" creates a new file that does not KNOW about any other file and cannot change it. Seriously, something else has to be going on here. From my view, you must being doing something else to cause this . It would be very worth knowing if you are experiencing this and we can then reproduce it. The entire premise of doing multilevel incremental backups is at stake.

Can you post one this template file (no media) that behaves this way after it is "saved as" something else?