Hi,
There are huge issues when it comes to saving/loading metaframes in my setup with VEP. It's the same on both my main DAW and my two slave computers. The issues are the following:
- Vienna constantly forgets it's current file path. Therefore I can _NEVER_ select just "save", because VEP will just save into "thin air". I always have to manually select the path and file name through "Save As", and it's never present in the directory where I loaded the metaframe.
- Currently I spent 4 hours yesterday intergrating a new library into my template. Opening the metaframe today reveals that the instance where I loaded the library is completely empty. The "modified" date/time stamp of the .mframe-file matches my last save. I recovered three different versions of the metaframe through Dropbox, and it was empty in all of these cases.
I can now NEVER trust VEP to ever save anything which is quite a gamble, everytime I make a modification in a .mframe I will constantly wonder if it's saved or not, because VEP doesn't ever give any warnings.
If there's an option I've checked in VEP that prevents this metaframe to ever be saved, it's ABSOLUTELY INSANE that it won't give a warning even after several hours of continous saving.
Any suggestions what might be wrong?
Best,
Andreas
System:
DAW: Macbook Pro Retina, OSX 10.8
Both slaves: PC w. Windows 7 x64