I've been using VEPro for a while without issue…The current feature film I'm working on has a smaller template than I've used previously on this machine, yet I'm running into problems with both Protools and VEPro quitting.
There are so many variables and options I was wondering if anyone could give some insight?
I'm running the latest version of VEPro, and Protools 10.3.8 on a Mac 6 core Westmere with 24GB RAM, on 10.8.5. VEPro and Protools are hosted on the one machine, and CPU usage rarely goes above 25-30%.
Mostly what is loaded in VEPro is Kontakt instruments, but I also run Dimension Brass and Omnisphere, and the occasional other synth. I run the 64bit VEPro server with KMS not enabled, and Omnisphere set to 'streaming'.
The version of Protools I've installed was a clean install. I've also done the usual PT troubleshooting (trashing databases and preferences), and I've also done a clean install of VEPro and trashed the preferences I could locate!
I run Disk Cache set to 'normal' in PT, and assign 5 cores.
As I say I've run much larger templates on this machine (albeit on Lion with an older version of VEPRo), without issue.
Most of the crashes seem to come when closing PT and opening another session. Either PT goes, or VEPro goes.. Either way they both have to be restarted as VEPro shows as busy unless they are both restarted.
I'm happy to post crash logs if that helps, but I wondered if there was a good place to start for general troubleshooting for VEPro? Maybe there are preferences I haven't properly trashed..?
It would also be useful to have some insight as what best to set the number of threads to in VEPro? 12 are available on my machine, but clearly some will be in use for PT.
Thanks for your help in advance.