Vienna Symphonic Library Forum
Forum Statistics

181,965 users have contributed to 42,196 threads and 254,639 posts.

In the past 24 hours, we have 5 new thread(s), 9 new post(s) and 52 new user(s).

  • VI or VE?

    Just starting work on building a template, and am wondering how best to load stuff. On my slave machines there's obviously no question - I'll be using VEPro to load instruments into. But on my main DAW I'm wondering what's going to work best. Should I simply load tonnes of instances of VIPro onto Cubase instrument channels? Or should I run VEPro on the machine, and host the instruments in that. A lot of people seem to do the latter, but I can't imagine what the advantage is - in fact it seems to me that this must add to the processing load.

    On a related note, I'm looking to run fairly big instances of VEPro on the slaves, which I believe is better than lots of small ones. I read that, when using the VST3 plugin, the number of MIDI inputs appearing in Cubase would automatically match the inputs per instance on each machine - but this doesn't seem to be the case. No matter how many MIDI inputs I set per instance, on the slaves, in Cubase I can only see 8 inputs per connection. Am I doing something numbskulled?


  • The advantages of VEP on the main DAW are better CPU efficiency and not having to load all those instruments when you open each piece.


    Dorico, Notion, Sibelius, StudioOne, Cubase, Staffpad VE Pro, Synchon, VI, Kontakt Win11 x64, 64GB RAM, Focusrite Scarlett 18i20, August Forster 190