It would be totally trivial to build such a thing, if it was only a technical issue. It takes about 20 methods or so that you really can't live without, and if you split those by functionality and make the whole thing extensible, you can add the missing functionality later without breaking anything (by allowing fallback down to the minimal core).JCJR wrote:I would like a plugin SDK that is stupid-simple for both hosts and plugin devs to write against.
But the problem is that getting anyone to agree on how to do even that, and getting anyone to actually implement it.. just not going to happen. Any one of us could draft that thing into a working state (with a VST wrapper too) in about a day.. but that would be a wasted day.