So what do you guys think? Is it just my machine or are my saved Metaframes somehow faulty?
Is no one else seeing these crashes?
Would you like me to send a Metaframe?
I'd really like to solve this problem.
200,331 users have contributed to 43,195 threads and 259,071 posts.
In the past 24 hours, we have 1 new thread(s), 9 new post(s) and 69 new user(s).
Phil,
Did you ever resolve this?
I am able to reproduce this now, using build 5436.
mac OS 10.6.3
The channels of the viframe were:
1 instance of Kontakt 3.5, routed to 8 outputs
3 input channels (source: outputs 3-8 of Kontakt)
1 Bus
1 VSL VI with a 6 cell matrix - maybe 600megs of ram in use
If I select the instance of Kontakt and the 3 input channels, I can crash the viframe consistently.
WHAT IS DIFFERENT NOW (as compared to before?) - the VSL VI !
When I tested this last month, I did not yet own any VSL instruments -- now that I have 8 big libraries, I am pushing VEP much harder. So yes, I can reproduce this. Did you find resolution?
Thanks,
Jeremy
Hi Jeremy, I have become used to not deleting anything in VEPro so I have avoided the problem.
After reading your post I opened up some of the metaframes from the start of the year...........all with Kontakt 4 present. It won't crash. As far as I can remember I have changed nothing.
I've opened 4 metaframes now from different times of the year and none will crash.
If I was going to point the finger I would point directly at Kontakt. The only crashes I have with VEPro are when I'm doodling inside Kontakt.
Not that I can reproduce it.
Oh!!! I just remembered that the guys at Vienna told me to turn off multi threading in both Kontakt AND VEPro. So in the preferences in VEPRo I only have 1 thread chosen. And in the prefs of Kontakt you can turn off the option that mentions threading.
It seems to make no difference to the CPU usage at all.
Maybe that's the solution?
Good luck.