Hi,

I've been doing some interesting side by side comparisons using the sample VE Pro template with Logic Pro 9 and Cubase 5.

So this is using the exact same VE Pro Template (decoupled) and will each VE Pro instance loaded as a multi out plug in within the host. The cpu use shown here is at an idle state (i.e. nothing playing back). How come Cubase is using so much more CPU? AND making VE Pro use so much more cpu? Is it something to do with the inefficiency of the VST VE Pro plug in compared to the AU plug in?

Any thoughts/comments Vienna team?

thanks so much!

this is because Cubase is not coded for Core Audio but for the windows audio I/O ASIO; it runs this fundamental service under the wrap CoreAudio2ASIO.bundle.

In addition, when we have AU components installed on the same machine as .vst, Cubase fetches the former and wraps it as the latter.

Which means crappy performance.

I don't know what the activity monitor percentages mean. I do know that Cubase requires around 4 times the buffers to run the same instrument, generally than Logic will, all else being equal. I am using Cubase because VST3 allows for multiple midi ports (AU protocol appears to have a limit of 16 channels into Logic sequencer, period), ie., I'm using it because of VE Pro. VE Pro is the only thing that makes running virtual instruments in Cubase on a Mac at all viable for me, so it's a kind of circle.