# Plan on implementing and porting VST3 getMidiControllerAssignment()?

**URL:** <https://forum.juce.com/t/plan-on-implementing-and-porting-vst3-getmidicontrollerassignment/14489>\
**Category:** Audio Plugins\
**Created:** [March 19, 2015, 2:18am UTC](https://forum.juce.com/t/plan-on-implementing-and-porting-vst3-getmidicontrollerassignment/14489 "2015-03-19T02:18:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xsd121](https://avatars.discourse-cdn.com/v4/letter/x/ebca7d/32.png) [@xsd121](https://forum.juce.com/u/xsd121)\
**Post date:** [March 19, 2015, 2:18am UTC](https://forum.juce.com/t/plan-on-implementing-and-porting-vst3-getmidicontrollerassignment/14489/1 "2015-03-19T02:18:14Z")

</div>

Hi jules,

&nbsp;

Any plan on porting the VST3 API&nbsp;getMidiControllerAssignment() to audio processor class in VST3 wrapper cpp?

So that we can make the midi cc to parameter mapping easily..

Or do you have any suggestion that we could elegantly override and implement this in our audioprocesser subclass for the moment?

&nbsp;

Thanks.

```
The current codes in vst3 wrapper cpp 
//==============================================================================

    tresult PLUGIN_API getMidiControllerAssignment (Steinberg::int32 busIndex, Steinberg::int16,

                                                    Vst::CtrlNumber midiControllerNumber,

                                                    Vst::ParamID& id) override

    {

        //TODO

        id = 0;

        return kNotImplemented;

    }
```

---

<div class="post-metadata">

**Author:** ![jrlanglois](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jrlanglois/32/21372_2.png) [@jrlanglois](https://forum.juce.com/u/jrlanglois)\
**Post date:** [March 19, 2015, 4:40pm UTC](https://forum.juce.com/t/plan-on-implementing-and-porting-vst3-getmidicontrollerassignment/14489/2 "2015-03-19T16:40:10Z")

</div>

VST3 requires the MIDI CC stuff to be transmitted as **parameters** &nbsp;(hence the ParamID parameter in that function).&nbsp;This is no easy feat!

---

<div class="post-metadata">

**Author:** ![xsd121](https://avatars.discourse-cdn.com/v4/letter/x/ebca7d/32.png) [@xsd121](https://forum.juce.com/u/xsd121)\
**Post date:** [March 21, 2015, 8:38am UTC](https://forum.juce.com/t/plan-on-implementing-and-porting-vst3-getmidicontrollerassignment/14489/3 "2015-03-21T08:38:50Z")

</div>

Yes, jules has already overridden it, but left a TODO comment.. which is where to do the mapping.

---

<div class="post-metadata">

**Author:** ![jrlanglois](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jrlanglois/32/21372_2.png) [@jrlanglois](https://forum.juce.com/u/jrlanglois)\
**Post date:** [March 21, 2015, 4:58pm UTC](https://forum.juce.com/t/plan-on-implementing-and-porting-vst3-getmidicontrollerassignment/14489/4 "2015-03-21T16:58:52Z")

</div>

I’m well aware!

The issue is how to go about it without messing anyone’s plugin up. There has been a lot of demand for it on the forums; if I ever get a spare moment I might go and implement it.

---

<div class="post-metadata">

**Author:** ![ujam](https://avatars.discourse-cdn.com/v4/letter/u/2bfe46/32.png) [@ujam](https://forum.juce.com/u/ujam)\
**Post date:** [September 4, 2015, 7:48am UTC](https://forum.juce.com/t/plan-on-implementing-and-porting-vst3-getmidicontrollerassignment/14489/5 "2015-09-04T07:48:09Z")

</div>

How about an option where extra parameters are created for all MIDI CCs, pitch bend and aftertouch, and the VST3 wrapper converts those incoming parameters to MIDI and sends them to the&nbsp;pluginInstance? &nbsp;Then the plug-in would&nbsp;receive&nbsp;CCs as usual. &nbsp;Would that work or is there something I'm missing?
