Vienna Symphonic Library Forum
Forum Statistics

181,970 users have contributed to 42,196 threads and 254,641 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Can you set up Kontakt to receive 4 ports while working inside of VEP?

  • Can you set up Kontakt to receive 4 ports while working inside of VEP?

    I
    I
    Hey guys, I'm trying to setup Kontak to receive more than 1 port in VEP, but the ports 2,3 & 4 are disabled, even when I set the MIDI ins as OMNI. Anyway to setup this or do I have to create a Kontakt instance for each 16 MIDI tracks I use? Thanks!
  • C
    C

    No, the Kontakt ports don't do anything in the plugin beyond 'Port A from host'. Essentially [B, C, D] provides for multiple inputs for control in the standalone.

    If you have the Kontakt multi's channel set to omni, you can have 16 channels under that.
  • B
    B

    the only thing you can do is add another kontakt plugin in the VE PRO instance and set the incoming midi port to VE PRO Midi input 2. (up to 8 with vst3)
  • C
    C

    With the VST3 version, in fact there are up to 48 ports available.

    Just think of VE Pro as the multitimbral plugin, there is no need for Kontakt to have multiple ports in it (unless you believe you are conserving resources by making giant multis rather than instantiating anew, which is pretty negligible and at this level not real meaningful). You can get 16 channels in a multi. As a regular plugin one port is awfully limited, I remember moving from Giga to Kontakt and having the same question.

    I'll still put a family of instruments in a multi, but I'm not finding multis to be more efficient than single instances.
  • I
    I
    Not being able to receive more than 1 port in Kontakt is actually less efficient and pretty messy when working with a big pallet.

    The main problem is that if you are working with a big library (lets say a brass collection) and want to setup the Kontakt mixer with more than one output (high brass, low brass, brass fxs, etc) you are gonna have to be splitting it several instances and when you add your other libraries you end up with a very large horizontal pallet. Also, since you are limited to 16 channels for instance you will have to create multiple outputs of the same kind of stem (e.g long brass) and then grouping them together in one VEP bus instead of sending them directly to your DAW, so you are actually using more resources too.

    When you add other libraries to the same vframe you end up with a big mess, especially if you are using a multiport DAW like Cubase...

    Having each library in one Kontakt instance would be much more modular too. You can just load it when you need it, or if you want to move it to another it vframe is super easy since you just load one Kontakt instance.
  • C
    C
    last edited
    last edited

    @imzadim said:

    Not being able to receive more than 1 port in Kontakt is actually less efficient and pretty messy when working with a big pallet.

      since you are limited to 16 channels for instance you will have to create multiple outputs of the same kind of stem (e.g long brass) and then grouping them together in one VEP bus instead of sending them directly to your DAW, so you are actually using more resources too.

    This seems to conflate things that aren't the same thing. I don't know how the limitation of sixteen channels does anything through itself to rule how you assign the outputs of Kontakt. To be concrete about this, you could have 64 parts on 16 MIDI channels, assuming here is some doubling, but you are outputting 64 mono to VE Pro in terms of mixing. And one bus returning to Cubase. Before full automation in VE Pro, I made a lot of stems. Now I make 4 or 5 busses, usually, doing most of the mixing in VE Pro, so Cubase is not at all cluttered. There are quite some automation lanes.

    Making a lot of stems is one way to work, and some people must do. Technically you are using a little more of your computer for each instance. I forget, but for me it's negligible. But returning one stereo bus to Cubase is definitely using less than a whole slew of outputs,

    I shouldn't have said there is *no* reason, that's just my modus operandi & my opinion. I have adjusted to having the one port. It is larger in the horizontal, rather than larger vertically in Kontakt. We prefer a different way to tidiness.
  • I
    I
    It really doesn't really have anything to do with whether you mix in Cubase or in VEP. You can always send the stems to a VEP bus and mix in VEP if you wish.

    Most patches don't really share the same MIDI part, so most of the time you are stuck with 16 and every time you ran out of a port you need to create a Kontakt instance and possibly a new audio bus. With a big orchestral palette it adds up to way too many of them...
    Even if you have a fast CPU and the difference is not too much, it's a pain in the ass when you want to add or remove libraries. You have to add Kontakt Instances (or VEP channels) and set the channels for each one. With only one instance or 2 the whole thing would be so much faster.
    It's also very useful for moving thing around different vFrames and creating new pallets. And the horizontal scrolling IS a pain :(

    In any case, it's not the end of the world, but kind of weird it doesn't work
  • W
    W

    Sorry to pop into this...

    So it is true that you cannot handle multible inputs/outputs in just one instance of Kontakt or Play. Wow... what a lack...

    One instance for one instrument only follows the VI integration architecture but should be improved asap.

    Just my two cents... ;)
  • C
    C

    To be clear, you can't do more than one port into the plugin. You can do 16 channels, and I don't know the amount of .nkis in a multi. It seems like Kontakt 1 was limited to 64 instruments in a multi. The number of Kontakt outputs is 64 mono or whatever combination of mono, stereo and surround amounts to 64 mono, ie., 32 stereo outputs.