Generating MIDI messages within a VST plugin and passing them to the host

[stephenk]

@1gn4ci0

In AudioPluginHost, unlike Reaper, all my plugins pass along incoming CC messages.

Does it have something to do with the macro JUCE_VST3_EMULATE_MIDI_CC_WITH_PARAMETERS:

What is the intention of macro JUCE VST3 EMULATE MIDI CC WITH PARAMETERS

My doubt about the meaning of the JUCE_VST3_EMULATE_MIDI_CC_WITH_PARAMETERS macro is which “direction” it applies to: when enabled, does it mean that… a) Every CC received by the plug-in as MIDI input, will be interpreted as if the corresponding automated parameter were moved by the host, and the plug-in setParameter() is called accordingly or b) That for every automated parameter that is moved (i.e. every call to setParameter()) a corresponding CC is sent from the plug-in as MIDI output ? P…

@1gn4ci0

However, controller messages generated within a plugin are still not passed along.

This is because of the lack of support for LegacyMIDICCOutEvent, as I mentioned before:

VST3 (midi) and JUCE

I was looking into this recently. The fact is, I was able to modify the JUCE AudioPluginHost to send CC Output from VST3’s, using the kLegacyMIDICCOutEvent. The problem is, it seems, is this: the modifications do not have anything to do with your plugin itself, but only the host. So fixing this in JUCE’s host does nothing to fix your VST3 plugin’s ability to send CCs in Reaper, Digital Performer, or any other host. It seems nobody supports this. Here’s the completely unfinished hack (two modifi…