ANSWER: use VST (do not use vst3)
How to use Foot Controller for KONTAKT Volume?
Trying to get Roland EV-5 Pedal to control the Volume of a Kontakt Piano patch.
also tried using BBC Symphony as shown in this vid: MIDI Guitar 2 & Expression Pedals
Ive tried several CC 1, 11, 64, …so something else is not connected yet not sure what.
In MG2 you can’t control it in the standalone version, but in MG3.
~ thank you…Can anything in MG2 be CC controlled?
Theoretically you can try to control the Gain of MG2, but you can’t control anything inside Kontakt.
In addition to the control parameters offered by Midi Learn, it is also possible to control all the parameters of the Midi Machines offering a knob in their interface. (bassline, sustain, etc).
As said, in MG2, the Instrument Gain is the only workaround to control the volume of Kontakt or any other instrument and is simpler to use.
Did you try loading the KONTAKT VST and not the VST3?
I can get it to work both with my VST and my AU (Mac) formats, but for some reason not with VST3.
It should be a s simple as choosing a controller you know is sending CC7 (for the Volume in KONTAKT) in the MIDI INTERFACE/CONTROL slot.
I use my USB-Pedal interface to change CCs, and you seem to have a similar software in the MIDI Expressor.
I am using the EV-5 for this setup, so yes, I works. But again, is this a Mac thing? I don’t think so, but I can’t be sure of anything anymore.
It works with my EV-5 (CC number 54) mapped in the MIDI automation window of Kontakt VST2 to the volume (but not in VST3 tested before).
I had first tried in the Host automation window out of habit acquired in Gig Performer but it didn’t work… bad habits are quickly acquired… 
In MG2 you can’t control it in the standalone version, but in MG3.
~ That is factually incorrect.
The KONTAKT 6 VST will absolutely work in the Stand Alone version of MIDI Guitar 2.
~ Thank You.
Tested using VST and works as expected.
Now the question is WHY?
why the F*K does VST 3 not work, when VST 3 is suppose to be the newest and more updated version.
There are some other issues with the VST3 format that is causing issues with MG3. But I don’t know really where the problem lies. So we are going to have to see this out I believe. Keep testing all formats if someting is off for now.
Many VST3 plugins only implement a subset of the VST3 specifications. VST3 developers only test their plugins on a subset of available hosts, and they only test what they have implemented (assuming that they do comprehensive testing). If a host developer (like Jam Origin) requires a certain feature in a plugin and that feature isn’t implemented in the VST3 version, it fails. The VST2 spec is less complicated, has been around a LONG time, and is well understood and supported by hosts.
Some hosts, like Band in a Box, still don’t support VST3 plugins, so you are screwed if you bought a plugin from a new developer that doesn’t have access to the VST2 SDK and only ships a VST3 version.
Well, I’ve tried Kontakt 7 VST3. I didn’t install the VST2 drivers of most of my NI stuff when I set up my Win laptop this June as I felt they were outdated and replaced by VST3. It has bothered me in the past that everything was listed twice and I didn’t see the point in it.
Looks like they still have a reason to exist!
i do not believe that any single company has the resources to develop a technology like vst3. and if that company also has a track record of unfairly using its position to suppress competition (as they did w/the initial vst3 licensing and by shutting down vst2) then they surely cannot be expected to focus on user satisfaction.
i don’t recall which mpe/midi protocol subset vst3 left out, that came up earlier. it was kind of astonishing to me (mentioned elsewhere on the forum, couldn’t find it).
for my money, the sooner we release ourselves from steinberg’s grasp the better.
their focus will never be to optimize vst3 and fix the missing/non-working items. their focus is to optimize the profit they can make from vst3.
