VST (and perhaps AU) wrapper/bridge for FL Studio native plugins

Post your ideas and suggestions here

Return to “To Do”

[You can only see part of this thread as you are not logged in to the forums]
N_K
Sat Aug 08, 2020 1:51 pm

x

VST (and perhaps AU) wrapper/bridge for FL Studio native plugins

This idea came after using Minihost VST and remembering all the threads asking for VST updates and Mac ports of Image-Line plugins.
In those threads, FL Studio VSTi is often suggested to serve as a "wrapper" or "bridge" between FL Studio native plugins and other DAWs, but that is not practical for situations when one needs to use many (30+) plugins - both instruments and effects - in different tracks [in another DAW].

It has been stated by Image-Line staff that porting internal plugins to VST and AU (and updating/supporting them) requires significant effort and is not currenty of high priority. This is understandable due to multitude of hosts and platforms on the market, and requirements of testing each and every plugin on each combination.

Perhaps expanding Minihost - or making a custom wrapper plugin - to bridge FL Studio native plugins to other plugin formats might be a solution to this. That way, only the wrapper's compatibility on different hosts and platforms would need to be tested. Regarding user experience, Minihost already provides a good example: especially when used in "View Plugin Only" view it can function effectively as a single-plugin wrapper.

The benefits of this to users are obvious: they could potentially use any FL Studio native plugin in another DAW. Ideally, if such wrapper/bridge was realized as VST3 plugin, this might even allow VST Note Expression to be translated to per-note parameters of plugins of FL Studio native format.

The benefits of this to Image-Line could be ability to sell any internal plugins, perhaps for extra price, to be used via such wrapper in other DAWs, without the need to port and support [each format version of] each plugin separately.

Return to “To Do”