Maybe this is my chance to re-invigorate a thread I started Dec 13. My issue then was failure to open a .veg file. The .bak file would not open either. This was, for me at least, a very large Vegas 12 project. as much as 50+ hrs of HDV footage.(maybe more) As the editing progressed, my veg file got slower and slower to open, and then finally failed to open. the veg file was 3,846kbs when it refused to open. A restore file from a few days earlier did open, but it’s size was only 3,478kbs. I reverted to that file, lost 2 days work, began editing and again made it to 3,800 kbs when the new file failed to open on the next session.
Looks like I hit a brick wall. can you say “size limit”?
so I doubled my RAM to 24GB and the performance did not change.
The vegas120.exe in task manger process window showed approx 1,200,000k when they reached the point where they would no longer open.
The fileIOsurrogate.exe32 showed showed over 700,000K at the point where the project would not open.
I got no where in my last thread about this issue. Just a “ask Sony”. They recommended I install build 486 to solve the problem. LMFAO..
After that install nothing would open, not even the old restore file. The issue there turned out to be thumbnail creation. long story.
So…. I’m not asking anyone reading this for a solution to my little problem here. Just reaffirm that either “YES” we have built Vegas 12 projects that exceed 3,846kbs, or “NO” that is the largest .veg file we have ever heard of.
i7 quad core, intel mobo, 24 GB ram, windows 7 Ultimate 64 bit, 120GB SSD system drive. 4TB raid0 media drive