# No more Midi input on VST Plugins?

**URL:** <https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977>\
**Category:** VST Live\
**Tags:** issue\
**Created:** [June 30, 2023, 6:35pm UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977 "2023-06-30T18:35:02Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jihem](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jihem/32/201421_2.png) [@Jihem](https://forums.steinberg.net/u/Jihem)\
**Post date:** [June 30, 2023, 6:35pm UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/1 "2023-06-30T18:35:02Z")

</div>

Hi!

I can’t see no more the Midi input selector introduced on v1.1.30 on the header of audio plugins…

The stranger thing is that the Midi input I selected on a plugin on a older version of VL is still active and working when I open the project in 1.2.1…

---

<div class="post-metadata">

**Author:** ![Spork](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/spork/32/542_2.png) [@Spork](https://forums.steinberg.net/u/Spork)\
**Post date:** [July 1, 2023, 7:30am UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/2 "2023-07-01T07:30:36Z")

</div>

Hi @Jihem,

hm …

1. Start VL, New Project, Select TRACKS
2. Add an Audio Tracks
3. Load “WahWah” Plug-In as an Insert
4. Open the editor of the Plug-In

The MIDI input selector is still there. Where is it missing? Which Plug-In?

Thank you,  
Michael.

---

<div class="post-metadata">

**Author:** ![Jihem](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jihem/32/201421_2.png) [@Jihem](https://forums.steinberg.net/u/Jihem)\
**Post date:** [July 1, 2023, 12:00pm UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/3 "2023-07-01T12:00:59Z")

</div>

> [@Eventide Octavox: how to?](https://forums.steinberg.net/t/eventide-octavox-how-to/822675/13):
>
> On the global stack dedicated to my microphone, I inserted a Waves Harmony plugin, set the Midi input to Virtual Midi In 1 and my harmonies are generated!

I can’t do that anymore… Stack plugins have lost their Midi input selector.

---

<div class="post-metadata">

**Author:** ![Jihem](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jihem/32/201421_2.png) [@Jihem](https://forums.steinberg.net/u/Jihem)\
**Post date:** [July 1, 2023, 3:29pm UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/4 "2023-07-01T15:29:05Z")

</div>

To make sure of what I said before, I reinstalled an older version of VL (1.1.41) and here’s a screenshot of the panel of a plugin I inserted in a Global Stack :

 ![image](https://europe1.discourse-cdn.com/steinberg/original/3X/5/3/539e641dea2db06a1317b64362e612d59f86d79b.png)

You can see the Midi In selector on the top right. “Harmony” is the name I gave to a Virtual Midi input.

Now, the same project open in VL 1.2.1 won’t show this selector anymore :

 ![VST Live - Vocal Harmony in Global Stack 1.2.1](https://europe1.discourse-cdn.com/steinberg/original/3X/8/f/8fcba8a1683cb7e832b8ee23d39529c5366dae8e.png)

Despite this, the virtual Midi link is still working (the plugin receives Midi notes from a track), but I can’t modify it.

I’m in trouble…

Have a good week-end!

Jihem

---

<div class="post-metadata">

**Author:** ![Spork](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/spork/32/542_2.png) [@Spork](https://forums.steinberg.net/u/Spork)\
**Post date:** [July 1, 2023, 10:13pm UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/5 "2023-07-01T22:13:32Z")

</div>

… arg, the Global part. Yes, sorry. Fixed now. Next update.  
… 1.2.0 should be fine for that one.

Thank you!  
Michael.

---

<div class="post-metadata">

**Author:** ![Jihem](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jihem/32/201421_2.png) [@Jihem](https://forums.steinberg.net/u/Jihem)\
**Post date:** [July 2, 2023, 2:47am UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/6 "2023-07-02T02:47:52Z")

</div>

> [@Spork](#):
>
> 1.2.0 should be fine for that one.

Well… No 😬  
It looks just a bit different on 1.2.0, but still no Midi Input.

 ![image](https://europe1.discourse-cdn.com/steinberg/original/3X/4/4/44a467fc5d6de320e1571f9a8e6b5f5864c79ae5.png)

Now, I have to uninstall again and reinstall an old version to access this selector 😰

---

<div class="post-metadata">

**Author:** ![Jihem](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jihem/32/201421_2.png) [@Jihem](https://forums.steinberg.net/u/Jihem)\
**Post date:** [July 2, 2023, 3:39am UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/7 "2023-07-02T03:39:47Z")

</div>

The result of a series of uninstall/reinstall is that it works in 1.1.41, but not in 1.1.42 and higher.

I hope it will help you…

---

<div class="post-metadata">

**Author:** ![Spork](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/spork/32/542_2.png) [@Spork](https://forums.steinberg.net/u/Spork)\
**Post date:** [July 3, 2023, 7:15am UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/8 "2023-07-03T07:15:03Z")

</div>

Hi @Jihem,

Thank you. It’s fixed. Promised. My info “1.2.0 should be fine for that one” was simply wrong. I had a look again to the code. The bug was there for a long time. The next Friday is coming soon …

Have a nice week,  
Michael.

---

<div class="post-metadata">

**Author:** ![Jihem](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jihem/32/201421_2.png) [@Jihem](https://forums.steinberg.net/u/Jihem)\
**Post date:** [July 3, 2023, 12:27pm UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/9 "2023-07-03T12:27:34Z")

</div>

Thank you so much!

My wish is to load Guitar Rig 6 into a Global Stack and control it with a Midi foot controller. Notes and CC are ok but it seems that Program Changes are not changing the presets. Are these messages filtered somehow?

Can’t wait until Friday, this will be the longest week! 😉

Jihem

---

<div class="post-metadata">

**Author:** ![musicullum](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/musicullum/32/618_2.png) [@musicullum](https://forums.steinberg.net/u/musicullum)\
**Post date:** [July 3, 2023, 3:22pm UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/10 "2023-07-03T15:22:36Z")

</div>

> [@Jihem](#):
>
> Are these messages filtered somehow?

They would be filtered if you use it in Actions and Shortcuts. Else those should get thru like all other MIDI events, maybe Rig must be set up somehow?

---

<div class="post-metadata">

**Author:** ![Jihem](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jihem/32/201421_2.png) [@Jihem](https://forums.steinberg.net/u/Jihem)\
**Post date:** [July 3, 2023, 9:50pm UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/11 "2023-07-03T21:50:35Z")

</div>

Hi @musicullum , it seems to be a problem with VST3 protocol, as I read on this forum :

> **[MIDI Program Change forwarding for VST3](https://forum.juce.com/t/midi-program-change-forwarding-for-vst3/47161)**
>
> Hi, I get relatively frequent support questions about why the VST3 version of my plugin is not receiving MIDI program changes messages, while the VST2 gets them. Right now, JUCE uses the vst3 program change messages to switch the presets is the...

The following sentence makes me worry about the possibility to change a VST3 plugin presets by sending PC messages :

> VST3 doesn’t have raw MIDI input/output. Any messages that the plugin sends/receives must be formatted as VST3 events. It’s up to the host to convert MIDI messages into VST3 events that will be received by the plugin.

Should I look for a VST2 guitar plugin to achieve my goal?

Thank you for your advice.

Jihem

---

<div class="post-metadata">

**Author:** ![Jihem](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jihem/32/201421_2.png) [@Jihem](https://forums.steinberg.net/u/Jihem)\
**Post date:** [July 3, 2023, 10:01pm UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/12 "2023-07-03T22:01:46Z")

</div>

Another topic about how VST3 handle Midi messages :

> [@No Program Changes in VST3 - regrettable decision](https://forums.steinberg.net/t/no-program-changes-in-vst3-regrettable-decision/122202):
>
> Steinberg’s decision of making VST3 instruments unresponsive to MIDI Program Changes means that unless I install my VST3 instruments as VST2, I cannot make nor create and test my live sets in Cubase and have to take them elsewhere. I wish a plug-in or setting for program changes, CC etc. were created.

I guess it would be a tough task to code a workaround in VL…

---

<div class="post-metadata">

**Author:** ![Spork](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/spork/32/542_2.png) [@Spork](https://forums.steinberg.net/u/Spork)\
**Post date:** [July 4, 2023, 6:42am UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/13 "2023-07-04T06:42:10Z")

</div>

Hi @Jihem,

workaround? It’s like Arne said. Everything’s there and ready for VST3. It’s up to the Plug-In developer to add PC. Insert HALion Sonic, Open the Editor, Select the OPTIONS Page, activate the Prg Changes option …

![Screenshot 2023-07-04 at 08.32.41](https://europe1.discourse-cdn.com/steinberg/original/3X/3/c/3c6458f8ef71e92ff0a742883dacd0599d4acf91.png)

… now the “PGM CHG” will control slot

 ![Screenshot 2023-07-04 at 08.36.09](https://europe1.discourse-cdn.com/steinberg/original/3X/b/3/b3a43d6da8457a5c1af4e97cb11403d326110cea.png)

> [@Jihem](#):
>
> My wish is to load Guitar Rig 6 into a Global Stack and control it with a Midi foot controller. Notes and CC are ok but it seems that Program Changes are not changing the presets.

… I’ll check it later the day,  
Michael.

---

<div class="post-metadata">

**Author:** ![musicullum](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/musicullum/32/618_2.png) [@musicullum](https://forums.steinberg.net/u/musicullum)\
**Post date:** [July 4, 2023, 7:10am UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/14 "2023-07-04T07:10:30Z")

</div>

> [@Jihem](#):
>
> It’s up to the host to convert MIDI messages into VST3 events that will be received by the plugin.

Exactly, and of course we do.

> [@No Program Changes in VST3 - regrettable decision](https://forums.steinberg.net/t/no-program-changes-in-vst3-regrettable-decision/122202/1):
>
> Steinberg’s decision of making VST3 instruments unresponsive to MIDI Program Changes

That is nonsense. VST3 plugins must follow the VST3 protocol, which promotes all MIDI messages in a well defined and modern format. It is up to the plugin to support whichever MIDI messages it receives from the host. Many plugins don’t support program change in the first place, but nothing is beeing taken away, and Program Change messages are promoted to all plugins receiving MIDI just like with VST2, albeit in VST3 format. Finally, Cubase and VST Live promote all MIDI channel messages to all VST3 plugins in said format.

---

<div class="post-metadata">

**Author:** ![Spork](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/spork/32/542_2.png) [@Spork](https://forums.steinberg.net/u/Spork)\
**Post date:** [July 4, 2023, 8:36pm UTC](https://forums.steinberg.net/t/no-more-midi-input-on-vst-plugins/856977/15 "2023-07-04T20:36:58Z")

</div>

> [@Jihem](#):
>
> My wish is to load Guitar Rig 6 into a Global Stack and control it with a Midi foot controller. Notes and CC are ok but it seems that Program Changes are not changing the presets. Are these messages filtered somehow?

… how do you want to control the preset-selection with Guitar Rig 6? With your Midi foot controller? Which one is that? Which events will it send if you want to select a preset? Because I found out that Guitar Rig 6 will only select the preset if a Program Change Event only (!) will be send to the plug. Do not send any Bank LSB/MSB messages.

See you,  
Michael.
