Vienna Symphonic Library Forum
Forum Statistics

200,562 users have contributed to 43,201 threads and 259,099 posts.

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

  • multiple midi inputs with a multi timbral instrument

    take omnisphere, I understand how to get the separate outputs back to the host software. but how do i get my midi tracks in cubase to control the different patches you can load in omnisphere simultaneously. if omnisphere were on my local machine, the channel selection on my midi track would control the different patches within omnisphere, but when omnisphere is in ensemble pro, the channel selection on my midi track seems to just select the individual instrument, such as omnisphere, kontakt, stylus, etc... Am I missing something. Couldn't find it in the manual, and played around with it for quite some time trying to figure it out.

  • I don't have omnisphere, but afaik, this is what you'd need to do: In VE Pro, make sure that the Omnisphere instance's channel strip is set to use a unique midi input (one of the 8 that VE Pro provides). Set the midi channel on the omnisphere channelstrip to Omni (or all, i don't have it in front of me right now). It should now respond to the separate midi channels the way you've described, and not interfere with any other instruments loaded in that instance of VE Pro (this is why the unique midi input is needed). kell

  • VE Pro as a vst3 instrument gives us multiple midi ports, and per advice above you'll need a separate port for a multimbral plugin instance to use more than one channel as kell describes. As vst2 or an AU, you'll have to dedicate an instance of VE Pro to Omnisphere to do this as there won't be multiple midi ports available.

    The amount of midi ports you want is a preference setting in VEP server interface, I go for 16.


  • last edited
    last edited

    @Another User said:

    The amount of midi ports you want is a preference setting in VEP server interface, I go for 16.

    i haven't required more than 8 ports thus far, so i'd never gone looking to see if there were more available. that's great to know...thanks! cheers! kell

  • I've never actually used anything but vst3 instantiated from Cubase. I just did instantiate as vst2, to verify my received idea of this, and while here are my 16 ports ['midi in' list] available in VI Pro, in Cubase assigning a midi track to this instance, there is but the one port and its 16 channels.

    "vienna ensemble pro - midi in", where with vst3 it will be "vienna ensemble pro - midi in 1-16"

    What I meant by 'ports available in vst2' rather than by what VE Pro indicates as 'midi in' (midi ports into VE Pro), is this, that the sequencer using AU protocol sees one midi port per instance only. Vst2 here has the same limitation. I don't know from vst 2.4, tho. All I know is there are two versions available to me in Cubase 5, vst2 and the one indicated in the rack by three bars, vst3.


  • ohhh, okay, that makes sense. i've only really been using this in sibelius, which doesn't seem to care too much about the ve pro interface part of the picture. i'll give it a shot in reaper or samp. i'm expecting to see similar to what you do. either way, setting up a multitimbral in its own instance is just the best bet to avoid any issues altogether (and it's easier to keep sane/organized, too)! k

  • thanks, that answered my question. the omni setup worked great! i knew there had to be a way to do that. :)