I really really would not worry about "transfer their Kontakt Libraries" - all of us who build pro libraries would gladly trade a little rework on an existing product for more usable space in the interface. Of course there has to be some limit to how big a VST interface should be, and setting the width to some silly big number seems, well, silly. But in the end if you just set the vertical limit to (say) 650 and allow that to be the dimension that can be programatically changed then setting the width to the kontkat 633 should be fine…

OK, good I guess I'm just trying to confirm that when you say "multiple presets you designed" this is samples and fx routing.

..and MULTI functionality…meeeh, never used them myself, but I know lots of people do...

Incomplete documentation? Clearly complete documentation EVENTUALLY would be nice, but not during this phase, no one should expect that.

Yeah, there are only two, but since you can morph a panel into a button with just a few lines of code I'd like to keep the button rather simple.

For the record, the API calls are merged into one method.

Engine.browseForFile(bool browseForFileToSave);

Thanks. I wanted to add this feature for a long time because the onTimer callback is not perfectly accurate (it gets executed at the start of the buffer, so you don't have sample accurate timing).

You can write them anywhere (outside of the other callbacks of course), but I would suggest adding them in the onInit page - the script processor checks if the other callback pages are empty and skips the callback to save overhead and if you add the onClock callback on the onNoteOn page, an empty callback will be executed for every incoming note on event.