-
VEPro Metaframe File Integrity Check Failed
Hello I just lost almost all my studio settings because, somehow, my 32-bit server metaframe file got corrupted. Any fixes for this before I completely pass out from the enormous amount of work this just made for me?
-
HI Thanks for the idea. Unfortunately I always use the decouple command and so my settings don't get saved with the project. Any other ideas?
-
I guess you didn't back anything up then? The only other thing I could suggest is send the metaframe to support@vsl.co.at to see if they can unravel it for you.
BTW did the metaframe get corrupted because you used too much memory? If so then I doubt there's any way back, unless you saved viframes and/or Presets.
DG
-
darn. I back up my master computer's data files, but I never thought to back up my slave. That will teach me. I doubt it was too much memory because I have 32 gigs of ram and I was not yet using it all. Thanks though! MOH
-
@mohurwitzmusic said:
darn. I back up my master computer's data files, but I never thought to back up my slave. That will teach me. I doubt it was too much memory because I have 32 gigs of ram and I was not yet using it all. Thanks though! MOHIt could easily be a memory problem as the 32bit server can theoretically only use 4GB, and in practice less than that.
DG
-
Oh no way! I thought that one of the main reasons for VEPRo was to address all of the memory in the computer by having multiple instances-- even though these instances are within a single server application. MOH
-
-
I know this original post is a few years old, but I must say, Thank God for Time Machine. I had this very issue - I had to force-quit VEPro and it corrupted the Metaframe. I went to yesterday's backup, restored the one file and started back to work.
Time Machine is definitely worth the minor hassle and expense of getting a large-ish drive.
RW
Forum Statistics
199,030 users have contributed to 43,150 threads and 258,878 posts.
In the past 24 hours, we have 6 new thread(s), 14 new post(s) and 61 new user(s).