Page 4 of 4

Re: VST3 and MIDI CC pitfall

Posted: Wed Oct 07, 2020 5:56 am
by Summer65
We have just signed the license agreement of VST3 and have started our work. But now reading about this issue here and in other forums is frustrating. IMHO dropping such a support is a big step backwards. We have to reconsider our plans whether to use VST3 at all.

Re: VST3 and MIDI CC pitfall

Posted: Wed Oct 07, 2020 9:09 am
by Arne Scheffler
I'm not sure what you mean by dropping support. Please read https://developer.steinberg.help/displa ... I+in+VST+3 for information regarding which concepts are used in VST3. The good thing is, with VST3 support you get automatic support for MIDI 2 when the host supports it, you just have nothing to do as a plug-in developer all the burden has to be done by the host developer.

Re: VST3 and MIDI CC pitfall

Posted: Thu Oct 08, 2020 7:03 am
by Summer65
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 (https://developer.steinberg.help/displa ... I+in+VST+3) "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.

Re: VST3 and MIDI CC pitfall

Posted: Thu Oct 08, 2020 7:19 am
by Arne Scheffler
Why don't you use the MIDI API of the system if you need to communicate with MIDI as a transport layer? Then you can make sure that you send and receive raw MIDI the way you want. The host was always able to mangle the MIDI stream to its liking so that a plug-in eventually did not receive the raw MIDI stream from a device.

Re: VST3 and MIDI CC pitfall

Posted: Thu Oct 08, 2020 8:23 am
by Summer65
Thanks for the hint. We are going to check it.