Please not that topic from 2019 again. A lot has changed since, including full midi 2.0 support amongst other things. Since then many synths migrated to vst3. And also, most midi plugins went vst3 too, which would be kinda impossible if vst3 didn't support midi.adamtrance wrote: Sun Jun 11, 2023 10:02 am You just mentioned that you are no developer, so you probably didnt read this yet: https://forums.steinberg.net/t/vst3-and ... all/201879
Lots of devs had issued with VST3 and Midi as you can read through that thread. If you use a VST3 plugin which has midi they used some hacks or something to get it working, but I dont know, I dont understand the VST SDK, I can only use codes that are available in FlowStone. I will ofcourse try to help the dev as much as I can so they can add it. I obviously had two choice: hold back the VST3 version until midi is implemented properly (and when will that happen?) or release the VST3 now and let people play with it already. Which is better?
And yes, many devs had issues. Which is not crazy considering the complexity of vst3, and the lack of proper documentation from Steinberg (which they solved for a big part). But there is a big difference between 'having issues' and what you said, and i quote :
"Midi CC does not work with the VST3 version yet, because Steinberg removed it from their VST3 specification", which is simply not the case.
By now almost all my synths and midi plugins are vst3. None of them have issues with midi cc's. You are the last one to go vst3, and the only one that has these problems. And i know that you are depending on Flowstone. Which is unfortunate in this case as Viper is an awesome synth and deserves so much more. Just like JP6K btw.
Anyways, i won't bother you further. For now i just keep using the vst2, and keep living with Flowstone's quirks.
