Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Danger: It’s Easy to Overwrite Entire Project

  • John Perez

    March 22, 2015 at 1:59 pm

    Ok save to new name before ANY changes. thanks for all the ideas and insights. I just happen to be absent-minded sometimes.

    As always thanks so much to you guys…Johnny In Orlando

  • Bob Peterson

    March 22, 2015 at 2:37 pm

    I hate to say this, but this is Computer Use 100. When you finish for a day, you BACK UP your veg file. You also BACK UP any other file that you altered during the day. Perhaps, you edited your source audio file. You can then recover from this kind of error. I hate to have to redo my work.

    I routinely back up both the veg and the bak file.

  • Edward Troxel

    March 24, 2015 at 1:11 am

    If you’ve only saved once with the mistake, the “BAK” file should still be the previous version. When saving, here’s what happens:

    1. The current file is renamed to the .BAK file
    2. The file is now saved as a VEG

    The BAK file should always be one version behind to help recover in situations such as this.

    Edward Troxel

  • Maxim Vegen

    July 23, 2015 at 2:17 pm

    how do you find the bak file on a mac?

  • Danny Hays

    July 23, 2015 at 9:22 pm

    I always save any changes to a new name .veg file. I searched my computer for .bak files and found none. I have autosave checked in my preferences too. So I did some experimenting with VP13. I made a .veg file and saved it to a new folder. At that time, the new folder only shows the one saved .veg file. I opened it and made some changes and used ctl/s to save it, not with a new name. Then the folder shows a .veg and a .veg.bak of that .veg file. I then opened the .veg.bak file with VP13 and it was one save behind. So Edward Troxel is correct here.

Page 2 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy