Handling MIDI CC data

[yfede]

Is this the VST3 format?

I am aware that in VST3 the plug-in can only receive CCs through a set of special parameters that are explicitly mapped to a corresponding CC.

In JUCE the VST3 wrapper takes care of that, and that could explain why this happens only in SONAR or Cubase (which both support VST3) while it does not happen in Logic which only opens AUs: it’s possible that, if you “move” that parameter internally, then it does translate in the generation of CCs that are then sent to the host?

More about this subject has been discussed here: (unfortunately I don’t remember much of the discussion there, even if I took part in it. Ah, my memory…)

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…