Hi!
Not sure where to post this.
I’ve had this problem since building my big template. I’m using Cubase 7.5.30 (same issue with 6.5, 7.0…7.5.2) and have VEPro 5 load all of my instruments and Cubase only the MIDI tracks. Something I’ve noticed is if my audio device is connected and I connect my VEPro 5 instance, the CPU usage jumps to around 35-40% and stays there, jumping around ±5%. Playing back my piece will then easily give me 100% CPU usage, seeing that I only have 60% left. Thus I have to push my audio buffer way up (1024 or more) to compensate, which increases the latency extremely…
I’m using VSL MIR in VEPro 5, which is a CPU killer already so I need every bit of CPU power I can get out of my Intel Xeon E3-1230 v2, 32GB RAM (Win 7 x64). I’ve been in contact with VSL and they believe it has to do with the whole re-routing of audio and that Cubase doesn’t like that. I don’t know what causes this problem, let alone how to fix it. I use a Creative X-Fi Platinum soundcard with the 2.11 Asio4All drivers. However, I just got a new Steinberg UR22 and installed the latest drivers and tried it out. Result? Exactly the same, so its not an audio device or driver issue but somehow a Cubase <-> VEPro issue.
Side-note: All VEPro instances are decoupled. I’m using Audio Input Plugins to re-route my instruments from a secondary PC which also uses VEPro (re-routed from Slave PC to Cubase to the main VEPro instance for MIRing). I tried deleting every one of these plugins and my CPU usage went down from 35-40% to 25-30%. An improvement, but still far from optimal. My main VEPro uses 32-40 MIDI and audio in/outputs. However, I also tried pushing them down to 8 only and the CPU usage didn’t really change, maybe a few % less…
Does anyone know what the cause could be? Or if there is a possible solution or workaround, other than getting a big 6 or 8 Core CPU?
Thanks in advance.
Regards