Mac OS 10.5.8, Mac Pro 3,1, 18 GB RAM (all thoroughly checked, working perfectly), MOTU 828 Mk2, DP 7.24
Having a real problem with VEP5. I did a project in DP a couple of months ago using VEP4. No problems or weirdness.
In the meantime, I've installed VEP5. Now, when I return to the project, it won't load. Here's what happens:
- Instantiate VEP5 64-bit server
- Start up DP 7.24
- Load project
- Instances of VE inside the DP project start to populate, samples start to load
- CRASH, error report, bad RAM access message
Here are solutions I've tried:
- Reboot
- Make a copy of DP project, try loading that
- Repair Mac permissions
- Uninstall VEP5, reinstall
- Trash VEP5 preferences
- Do all of the above a second time
None of my attempts to resolve the problem have been successful. The same thing happens every time I try to load the project.
I'm able to create a new DP project and load things into VEP5, close, and re-open the project, without any problem. What I can't do is make the VE instances that I need in order to edit the older project, load successfully. They won't even stay open long enough for me to save them so that I can re-create them, and I haven't saved the instances in the form of .viframe64 files that I could attempt to open with new instances of VE.
So I'm really screwed here.
I'm really quite concerned that there's some kind of terrible backward-incompatibility bug which has somehow escaped the VSL engineers. I hate the thought that I may have quite a few un-openable projects, and I'm concerned about trusting this software with my work.
Can anyone shed any light on this problem and what I can do about it? Thanks!
--Chuck