The main consideration is that user experience would match that of using the VST plugins, as closely as technically possible.
Specifically, the requirements would include:
- unlimited numbers of instances of the wrapper in a DAW project (as many as CPU can handle), with reasonable CPU overhead
- all automatable parameters of the wrapped FLfx/FLi automatically published to the host through the wrapper (no need to manually pick which parameters of wrapped FL plugin are visible to host)
- UI of wrapped plugin maximizable in the wrapper, so that user sees primarily the plugin GUI (with perhaps small bar from the wrapper to access possible options etc.)
- VST plugin name reported by the wrapper to the DAW is/includes the name of wrapped FL plugin (if technically possible)
- VST presets save-able through the wrapper and perfectly recalled
- wrapper + FL plugin combination copy/pasteable as a single entity in DAWs (likely to be so by default, but worth mentioning here)
- resizeable GUI of the wrapper + FL plugin combination
- if possible, the format of the wrapper as VST3, with per-note expression support for synths
Thanks for reading!