Thx for the immediate response.
Our intension was not to create another VST plugin where 1000s great ones exist. Our idea was to create an overall solution where existing plugins can be used. The idea was to use the great VST technology and create a solution based on MIDI. For MIDI - good or bad - all MIDI events are essential including CC events. CCs are part of the MIDI stream. E.g. the timing of CCs related to other events is important. The interrelation of MIDI events is one of the key reasons why MIDI has made it for more than 30 years.
Form our limited knowledge from VST2 we were of the opinion that MIDI events are handled including CC events for MIDIin and MIDIout in VST3, too. It is disappointing reading here that using MIDI in VST2 was a “misuse” and VST3 is just for audio. A “misuse” which is one reason why VST has become so powerful.
We can debate whether the missing MIDI capability in VST3 is a drop of support or not. The fact is that according to the link (Log In - Steinberg Developer Help) “Unlike in VST 2, MIDI is not included in VST 3.” To me this is a drop of functionality which we overlooked.
The offered alternative is not adequate for our ideas, technically as well as from the license perspective. The license can be terminated with 6/36 months notice (see §9 of the contract) which impacts significant developments.
Looks like our view what opportunities might be possible by integrating VST3 in our solution was too naive. This is the reason why we have to reconsider our plans using VST3.