This only happens if my Cubase 7.5 project has VEPro running.... and it doesn' matter if I am triggering midi for a local VEPro or a slave computer instrument. Just moving the mod wheel up and down causes asio spikes! Not all instruments exhibit this behavior and after rebooting the computer, the instrument(s) tracks affected can change. But, if not using the modwheel, I remain at 10-15% cpu load.
Anyone else have this issue, or a solution? I'm near the end of my demo period and if I can't solve this, I can't really justify purchaing the VE Pro 5 program. I can't find anything unusual in my midi setup in the tracks, and I have filtered sysex messages in Cubase trying to find the problem, but that didn't help.
My system is a PC i7 3770K, 16GB ram (about 13.5GB loaded with Hollywood Brass on the DAW), RME Fireface 800, Cubase 7.5 and just updated to 7.5.1
Thanks,
Paul