Vienna Symphonic Library Forum
Forum Statistics

182,255 users have contributed to 42,214 threads and 254,731 posts.

In the past 24 hours, we have 4 new thread(s), 23 new post(s) and 47 new user(s).

  • Cubase 7 - Can't seem to see additional MIDI IN values?

    Hello gentlemen!

    I'm having an interesting issue. I have VEPro 5 all setup and it's all nice and pretty in Cubase 7. However after I connect to the slave (I don't see the instances btw, I must manually connect to the slave using it's IP which might explain this), I can't seem to use any additional MIDI IN values past the first.

    Here is a picture to illustrate what I mean.

    http://imgur.com/iDxvX7k

    So I can connect to this one and I can make good use of Kontakt's first instance in my VEPro Server. However if I make another Kontakt, I cannot get Cubase to see that extra Kontakt instance, it will read only from the first.

    Oddly enough I can make the second one make noise, it uses the same outs bus as the first instance. But I can't control the second one via midi.

    Any tips? I'm fairly new to Cubase so maybe i'm just doing something stupid. Much thanks in advance!

  • the image shows VE Pro with only one MIDI port. are you trying to use VE Pro via 'Instrument Tracks'? (instrument tracks is made to provide but the one connection, with no choice as to channel, nothing)

    Do you get a list of channels per that port? Connected to via 'VST Instruments' you should see this:

    (depending on how many ports you have enabled in the preferences) with 16 channels for each of these ports.


  • That is correct, I am using VE Pro via "Instrument Tracks (f11)". This was the only way I could find for me to be able to connect to it at all midi wise. I'm not sure how to bring up that list of channels, but I am able to use up to 16 channels in that first Kontakt instance yes. Is there no way for Cubase to utilize those extra ports?

  • double post, ignore this one please.

  • I have solved the issue, writing it here in case anybody googles it.

    If you want to use multiple midi ports in Cubase, Nuendo, or anything (other then Logic apparently, need special layer for that look at the manual for more) you need to use an Event Input plug-in. This will let you assign this plugin to an already connected server and utilize multiple ports.

    I have yet to solve how to make use of multiple channels from these event plugins but I'm certain that's not a difficult task and I will update this post when I do.

  • no, 'Instrument Tracks' is something else. F11 is the right way, 'VST Instruments'. It's confusing, I know. Additionally when you want to treat the output as audio, you have "VST Instrument Channel"; 'Instrument Tracks' is a 'Project'>'Add Track' menu item.

    To get multiple MIDI Ports, use VST3, which in the Cubase I use is indicated by three slanted dashes to the left of eg., 'Vienna Ensemble Pro'; the event plugin is a workaround for hosts that do not provide VST 3. You do not need to fool with it. (It isn't very easy in Logic and it is necessary in Logic or anything that's using VEP as AU, or VST2.)

    I don't know what's going on, what 'Cubase doesn't see Kontakt beyond the first instance' means actually. If you want to use Kontakt as a multitimbral instance, you have to make the nkm have 'omni' as the channel and individuate channels below that for its population of nkis. Then you assign Kontakt's outputs to the extent you need and open up 'inputs' - the microphone icon - in VEP and you'll have the outputs from Kontakt to select.

    If you've separate Kontakts loaded in VEP, it's just a matter of assigning them properly like anything else. 


  • Here is two instance of Kontakt assigned in VEP. In Cubase it only has to correspond: