Vienna Symphonic Library Forum
Forum Statistics

195,002 users have contributed to 42,953 threads and 258,083 posts.

In the past 24 hours, we have 12 new thread(s), 42 new post(s) and 66 new user(s).

  • VEP7 Ableton Live 12 Integration: How to set specific VEP instance plugin MIDI port in Live External Instrument?

    Hello everybody,

    For my musical productions I often switch from DAW to DAW depending on the musical genre I am to use for my compositions.

    I have been using my VEP7 orchestral templates successfully in Nuendo and Digital Performer, both of them allowing me to easily route my tracks to the specific MIDI ports I set up for the several plugins I have added to the VEP template instances, an example of which is shown hereunder:

    In the example, two VEP7 plugin entries (containing two Kontakt 7 multis, specifically) for a template instance are shown, with the necessary input channel entries mapped to the different patches in the Kontakt multi and their relative output channels. The kontakt 7 multi routed by MIDI port 5 looks like the example herunder:

    OK.

    That Said, recently I tried to use the same templates in Live 12 as well and - with my surprise and disappointment - I was not able to address the different MIDI ports in Live 12 External Instrument, as I normally do in Nuendo or Digital Performer, due to it allowing me to only select first the VEP7 server instance, secondly a plugin input channel and then its associated output channel, as shown in the example hereunder:

    In order to work around this apparent limitation, I would need to amend all my templates by creating separate VEP7 server instances for each instance plugin available in the template and then map a different Live 12 external instrument to each of these instances!

    Honestly, I cannot reasonably believe this is not possible in Live 12, as it is in other DAWs.

    Hence, my question here is: how can I route my tracks in Live 12 to the correct VEP7 instance plugin's MIDI port in my templates, without having to create a specific version of them in order to make them usable in Live 12 projects?


  • Unfortunately, I've found that this is the only way to setup my template using VEPRO and ABLETON LIVE 12. I really wish there was an easy solve for this as it would REALLY help my workflow/setup. As it stands now, I'm using a very paired down VEPRO template (about 20 instances) and routing them through external instruments as you have outlined above.


  • I only just purchases VEP7 yesterday and already knew about this limitation (on abletons side)

    Not sure how most route audio using live ? but if you have submixes in VEP (probably the way I will do it) then this (may)be a workaround.

    On windows using LoopMidi, could work on mac with IAC.

    Use the first VEP midi port then create as many loopmidi ports as needed and enable them in the server external midi page.

    So ie: Vienna Ensemble Pro port channels 1-16

    Then create loopmidi ports, I use names

    LM-VEP1 (16 channels)

    LM-VEP2 (16 channels)

    I hope this helps someone untill ableton get past the input port limit.

    Cheers 😉


  • After much messing and much frustration it seems loading VE inside a modular host like bidule or element

    exposes a new midi input channel on each new instance of VE inside each sub host instance.

    Its a workaround but better than being stuck with 16 midi channels with 1 instance.