I am running VEPro 6 and Cubase 10. I have a very large template of 17 VEPro instances that I run with Cubase. When I do not have any instruments enabled on VEPro and I connect my template with Cubase, everything runs fine. Everything also runs fine when I have a small amount of instruments enabled in VEPro and am connected with Cubase.
However, recently I was running a project with 7 VEPro instances activated and a large number of instruments enabled on them. All the instances were decoupled. Before connecting to Cubase, VEPro was running perfectly with no hicups. However, after connecting with Cubase, VEPro would freeze. My CPU was consistently at 50%, my RAM at 80%, and my disk at about 0%, so I thought there shouldn't be a problem. Cubase was also able to send MIDI to VEPro and get audio back with no pops, major latency, or any percievable problems. However, whenever I needed to go to VEPro to edit something, VEPro would be frozen and would not let me click on anything.
I was able to deal with this, except for one major problem. Whenever trying to save my Cubase project, Cubase would try to communicate with VEPro to save and was unable to do so. This resulted in Cubase freezing and me needing to force quit it. This was only a problem when trying to save.
I have a Windows 10 PC with an Intel i7 Quad-core 4.0GHz processor and 32 GB of RAM, with three SSD's, one for the system, one for my projects, and one for sample libraries.
How do I get VEPro to stop freezing like this? I do not know why this is happening since my CPU usage and RAM were both at manageable levels with no CPU spikes or anything. When I disabled an instance and was then only using 6 VEPro instances, the problem would sometimes go away but it did not seem to be resulting from disabling any specific istrument or instance. Thank you.
