VST3 plugins have unwanted "MIDI CC parameters"

[plugin_ninja]

Hello, everybody,

I have the following problem with a VST3 audio (fx) plugIn.

The PlugIn has 23 correct parameters and 2080 (16 * 130??) unwanted Midi CC parameters.
(displayed in Steinberg test host and Samplitude host display)

In my audioprocessor, the methods

acceptsMidi() and producesMidi() return false.

All regular parameters are created with VTree->createAndAddParameter(. . . ).

It seems that the JUCE_VST3_EMULATE_MIDI_CC_WITH_PARAMETERS macro described in the following link is active, but it is not.

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…

I am happy about ideas. . . . .

[plugin_ninja]

got it

#define JUCE_VST3_EMULATE_MIDI_CC_WITH_PARAMETERS 0

in AppConfig.h