I am seeing some strange behavior with Cubase 7.
I have a slave PC (I7 3960 64 gigs of Ram all SSD 6gbs)running my heaviest samples (EWQL Diamond) and I do not have many issues there.
On my main Mac Pro 2012 12 core 32 gigs of ram I am having issues.
When VEPro is connected to Cubase 7 it reports 99.9% in the CPU monitor in VEPro (bottom right).
This is not even during playback. Just connected. When I preserve the instance and disconnect it goes to zero. Reconnect and it is back to 99.9%.
I only have one instance open with about 5 instances of Kontakt 5 running Cineperc, a little Cinebrass and LA Strings. And 2 instances of Play 3, I do not have much running in Play just Choir and I few woodwinds.
I set 24 threads per instance in the main preferences.
The solution might be just to run all samples on the slave but I was trying to split them up.
I find it hard to believe that I can run very little on the very latest loaded Mac Pro. (albeit Apple has not updated the Mac Pro in a long long time. Which is should be cause for a major revolt on the now "Toy maker with a short memory".)
This seems to happen after I have been working for a while if I reboot I can work for another couple of hours. However, I prefer not to spend 25% of my day waiting for the computer to reboot!
Is there an better setup maybe more servers running with less instances etc....
thanks
-
VEPro Cubase 7
-
My slave machine sporadically jumps to 99% CPU as well (using VE Pro & Play). I got through a few hours of normal functioning yesterday though, so I don't know what the cause is.
-
Does anyone know if it's safe to use the Vienna update with Cubase 7? I was having the same issues with instruments loading twice and all sort of other weirdnesses!