Vienna Ensemble Pro 5 - Unable to assign CC's within Kontakt instances

[Skotein]

Hi there! I've run into some CC issues within Vienna Ensemble Pro and could use some help. Please keep reading, as there could be cookies in it for you.

I have a master-slave setup with an up-to-date Mac Mini as my master and a PC server slave running two virtual machines, both with Vienna Ensemble Pro 5 loaded on them (one for PLAY instruments, one for Kontakt and VSL instruments). Each VST3 instance of VEP is routed to plugins in my sequencer, PreSonus Studio One 2.5.

So far I've had no luck assigning CC's to the virtual UI knobs and faders that appear on most Kontakt instrument patches. When I right-click a knob to enable MIDI Learn, it will give me the typical Kontakt dropdown menu that says 'Learn MIDI CC,' but if I jiggle any of the knobs or faders on my Oxygen 49 MIDI controller, nothing happens. Oddly, CC1 (modwheel) is the only control that is assignable in VE Pro. My PLAY instruments also suffer from the same CC routing problem. The end goal is to be able to assign whatever parameters I want to my instruments without losing all my assignable knobs/faders in the process.

Here are all the steps I've taken to troubleshoot the issue:


- Updated VE Pro software across all computer systems.
- Installed and updated Oxygen 49 MIDI controller software across all systems.
- Enabled 'MIDI Learn' within Studio One to teach it all of Oxygen 49's controls.
- Tried assigning CC presets on Kontakt instruments to newly-learned MIDI controls via Studio One's automation mapping. For example, CC21 in Berlin Woodwinds can control vibrato intensity; I manually added the corresponding parameter Dummy 1-1-21 to the automation for that patch, but after linking the CC to a control on my Oxygen 49, that physical control/knob/fader is no longer assignable for any other track.
- Tried using the automation assignment tool within the VE Pro interface, but was a bit confused as to how it works and could not map any controls to physical knobs.
- Attempted to assign CC's using VST2 versions of VE Pro instances in Studio One instead of VST3.

If I think of anything else, I'll add it later. Screenshots to come! Any help with this matter is sincerely appreciated--

At this point, I'd gladly bake A DOZEN COOKIES of your choice and ship them to you if you can help me solve this crazy dilemma. And I make some damn good cookies.

[simon5413]

any headway on this since you last posted?

[civilization 3]

@Another User said:

- Tried using the automation assignment tool within the VE Pro interface, but was a bit confused as to how it works and could not map any controls to physical knobs.

The VE Pro automation map is something else. For Kontakt there is a long numbered list with zero descriptive info that I don't know. This is not midi. In the DAW there is going to be a menu in the instrument channel that communicates with that. I have gotten Kore Controller to work with that and [via VE Pro, direct Cubase to] take something Kore had as midi but this is a kind of esoteric area to be concerned with, rather than fix your midi control issue. 

(The assignment of 'source' to a physical controller in the automation map - the use of controllers in VE Pro directly - is deemed 'experimental' and is not actually supported.)

Right-click assign one of those jobbies in Kontakt and make a mark in Studio One's controller lane (position your cursor to the right of that change) or what-have-you there, and see if it doesn't change the position of the Kontakt knob. This will show you whether midi CC  is or is not getting to Kontakt in VE Pro per se. Then you can eliminate this as an issue, which will point the finger at your Oxygen device.

[simon5413]

I've found that just dragging the midi contoller from the automation list of midi ccs works just fine, fyi