Vienna Symphonic Library Forum
Forum Statistics

180,809 users have contributed to 42,142 threads and 254,365 posts.

In the past 24 hours, we have 2 new thread(s), 8 new post(s) and 70 new user(s).

  • VE Pro Cubase Performance on a Mac

    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!


  • could it be possible that VE Pro somehow "reserves" Porcessing power when working with cubase and doesn't do that in conjunction with logic? This would result in a similar performance though showing those radical different performance hits in the Activity Monitor. I'm still thinking much about using Cubase or Logic. So it's a very relevant question I think (for cubase on Mac useres general of course)

  • 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.


  • Oh thank you for that explanation. This is a really relevant thing to consider for the "Cubase vs Logic-on-Mac-Brainer"!

  • 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.