-
Vegas 12 problem opening veg file
I’m operating SVP 12, latest version. I have been editing a project since October. It is a larger project than usual, approx 50 hrs of HDV footage + 6 mov files. The project has been opened and closed dozens of times as I worked on it, and then set it aside to work on other projects, then open it again to pick up where I left off.
The size of the veg file has grown and with it the time required for it to load. On several occasions in the last couple of weeks, the .veg file will hang while loading the project and give me an error that reads.. “An error occurred while reading the file. Make sure you have read access to the file/folder and that it is not corrupted.” My solution for this had been to try the veg.bak file and cross my fingers. And that has always worked…..until last night.
The load stops at 68% and displays that error message, same for the veg.bak file. The veg file, and the veg.bak file size is currently 3,846KB. I discovered an autorestore file from a crash 2 days ago. I can open it, so this is not actually 2 months down the drain, just 2 days down the drain. The autorestore file is 3,478KB.
So.. before I ask what’s possibly wrong with my veg file, I would like to know why my autorestore files aren’t current? When and why does Vegas decide to create an autorestore file?
The project and project media is stored on a new USB3 3TB external drive. The media also exists on a 4TB raid0. The project has run very smoothly and I doubt the drive is the problem.
The issue all seems to be tied to the longer load time of the project as the size of the veg file grew. We are talking 5 mins, at least, back when it actually loaded. Today the project will load for 4 mins 20 sec. and halt with the error at 68%.
Back when the project veg file opened, it would load for about 5 mins and then pause at 72% for a couple mins, then the thumbnails would pop up in the media bins and presto!, it’s ready.
So, any clues, work arounds, tips going forward?
i7 quad core, intel mobo, 12 GB ram, windows 7 Ultimate 64 bit, 120 GB SSD system drive.
Larry Brewer
-
18 Replies
-
The autorestore is a setting that Vegas see when it didn’t close properly, and I believe it will only show up when you open Vegas without a project. So you can load other projects by double-clicking the .veg files, then one day open Vegas without a .veg file and the autorestore will come up.
In hindsight I would make sequential saves of your project each day (or more often) so you have a more recent backup to fall on.
As for fixing your problem, you can try a few things. First, try to change the Vegas settings, like disable RAM preview and GPU acceleration. Then try booting Windows in safe-mode and try to open the project (not sure this will work at all). Then try this: rename the folder where your event assets are and open the project, and for each file it asks for, tell it but don’t say to use that new folder for the remaining, you do this one-by-one. This is time-consuming, but it may tell you what asset it causing the problem. Then you can not load that asset next time and see if you go further. Sorry for your troubles, good luck!
-Jim.
-
Here’s what I have learned. The autosave functions saves a project file every 5 mins unless you have disabled it in options preferences. If Vegas shuts down unexpectly, the last autosave will try to reopen the project the next time Vegas is started. But!!!! If Vegas is closed correctly, no crash, no lockup, etc.. the autosave file is automatically erased.
So a vegas user has 3 files to try when opening a project. The primary file- .veg, the backup file .veg.bak, and the autosave file created the last time Vegas crashed. My probelem is that Vegas actually closed correctly with no hint of a problem, hence the most recent autosave was erased.
Think of the Irony. If Vegas hadn’t crashed 2 days ago I probably would have lost all my work.
I tried your suggestions, thank you. No luck.
Can anyone explain why the error window I see when the project fails to load does not include the “DETAILS” button? All I am getting is the error message and a “OK” button. The error window always had a “DETAILS” in past and it might help me with this issue today.
-
I don’t think this will help with the current problem, but at the end of the day during a long edit project, I always do a then a save-as and timestamp the filename. This way I can never lose more than a days work.
If you want to send me your veg file, I can see if it loads here. There won’t be any media, of course, but unless you are using plugins that I don’t have, the veg file should load OK.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Steve,
Thanks for your advise. I’m pretty much resolved to losing some of my work. But should the long load times I experienced leading up to the error have tipped me off? 5-6 mins was the norm, and often the .veg file would not work so I used the .veg.bak file to start the project. I believe the issue may be BCC transition plugins that I utilized on the last version that failed. Assuming that’s the case, is there a workaround to get this to load and then discard these transitions?
Also, why do I not see the “DETAILS” button on my error window? Being able to view the DETAILS of the error would shed some light.
I guess what I’m saying is, what’s the point in picking up from the last good save if I don’t know what errors caused the issue? I could end up 2 days from now with another file that won’t open and I revert back to the point before the issue that caused the problem. And I still don’t know what caused the problem!
-
That’s where the free “Auto Save” plugin installed when you install Excalibur comes in handy. It will save to date file names at your specified interval so you can easily go back to any point in time.
Edward Troxel
-
The veg file is basically a collection of pointers to media and scripts describing the editing steps you made so far. If the veg file is truly bad, then it wouldn’t load on another system either. The most common problem with startup problems is a corrupt media file, followed with too little RAM. Not having enough scratch disk (temp folder) will do the same thing.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
You may have led me to a potential problem. Sometime in the last 3 or 4 days my RAM went from 12GB to 8 GB usable. I had not considered a link between the two problems. I’ve yet to determine the cause but it will be interesting to see if the issue remains after I find the memory glitch. I’ll try re-setting the memory sticks. Do you have any other suggestions?
-
-
One way to minimise catastrophe is edit in smaller projects, in effect treating them as sub-projects, and then combine them in a ‘master’ project.
I recently did a high school end of year formal. I created a project for each major component such as the kids arriving in their cars, interview segments, speeches, dancing etc. When each was done, I then nested (imported) each of the veg files into a new master project. Even if I made minor changes to the sub-projects, when I next opened the master they were automatically updated in the master project.
I probably only had about 12 hours of footage, but I have done an ice skating project that probably would have had close to 50 hours of raw m2t and AVCHD footage using this technique. That did take about 2 minutes to load.
Your system specs are pretty close to mine. What other software, such as antivirus/firewall is running? It is recommended that you use an isolated machine for editing so that you can shutdown the antivirus/firewall software, and manually reactivate it only when you need to apply O/S or Vegas updates/
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 11 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
Steve
Thanks for your suggestion regarding the RAM in my PC and the possibility of it being the cause of the .veg file failure to open. It turns out the 12 GB ram (8 GB usable) issue was due to Windows 7 upgrades that for some reason had refused to configure causing my PC to revert. Seriously. The downloading of 14 updates, and the following configuration had repeatedly failed and reverted. Once I got the updates to “stick” and configure, the RAM returned to 12 GB and passed the mem86 test.
The veg file will still not open. fails at 68% every time. I would like to discuss other possible causes and solutions. I’m thinking that the issue is related to work I did before the last save. I used some NewBlueFX glow effects and Boris transitions. I suspect there in lie the problem.
Question: The error window that pops up after it fails does not include the DETAILS button I’m used to seeing, so that I might learn a little more about the failure. Is that normal?
Question: Is there a way to have the veg file open and ignore the plugins?
Thanks!
Reply to this Discussion! Login or Sign Up