As long as Maschine etc. doesn't suddenly expect NKS to tie to the VST3 protocol, I'm fine. I just don't really want to spend more months on platform issues this year.EvilDragon wrote: ↑Tue Apr 20, 2021 11:16 am I would hope not! NKS itself should stay as is, and I suppose it'd only be a matter of adding the same vendor-specific opcodes that were in VST2 to VST3 too. I'll ask around
Maybe NI could adopt LV2 instead or something open source to prevent any of this from happening again.
Or, they simply could contribute an open source plug-in SDK that is compatible to VST2...