INSTRUMENT PLUGINS / EFFECT PLUGINS / CHANNEL SETTINGS
The Fruity Wrapper is a software interface/layer between instrument / effect plugins and FL Studio. The control options (1, 3 & 4) are common to all plugins (FL native, VST & DX format), while the plugin options (2) only appear on Wrappers that are hosting VST & DX format plugins. The Wrapper provides compatibility with the VST and DX plugin standards (the screenshot below demonstrates the Fruity Wrapper hosting a fictitious 'Poi Poi' VSTi plugin). More information on plugin formats can be found here. For more information on installing and using 3rd party VST/DX plugins, click here.
There are two versions of the Fruity Wrapper, Effect & Generator. FL Studio will select the appropriate wrapper depending on the plugin type loaded. There are several control options:
Click on the screenshot Settings, Processing or Info tabs below to see the help for that tab.
See help for tab: Settings, [Processing], Presets, Info
NOTE: If you are troubleshooting plugins, see the section on 'Plugins behaving badly' for more tips.
These two options are only to be used if the default 2 ms 'Fixed sized buffers' does not work. In general, both these options should be off.
1. Memory management - Bridging opens the plugin in a separate process removing the plugins memory allocation from FL Studio's memory space. Bridging is particularly beneficial for sampler and ROMpler plugins that consume large amounts of memory loading samples. The maximum memory available to the bridged plugin will be at least 2 Gb for 32 Bit Windows and at least 4 Gb depending on your version of 64 Bit Windows (see 2). To reduce the memory burden of Audio Clips and Sampler Channels use the 'Keep on disk' option.
2. 64 Bit plugins - Bridging allows 64 Bit VST plugins to be used in FL Studio regardless of the Windows version (32 or 64 Bit). 64 Bit plugins are auto-detected and the Bridged mode will be set accordingly. The memory available to the plugin depends on the Windows bit-depth as described above. NOTES: 1. 64 Bit plugins running on 64 Bit windows will have access to the maximum memory available under your Windows version. 2. We recommend using 32 Bit plugins in the 32 Bit version of FL Studio, where possible, since the bridging process introduces an additional layer of processing and so a small CPU overhead.
3. Protect FL Studio from crashing plugins - If a plugin crashes while in Bridged mode then it is far less likely to bring down FL Studio at the same time. Try using Bridged mode with plugins that are unstable or crash.
These options determine audio input and/or output routing for the plugin and are necessary only for multi-input or multi-output plugins such as a compressor that accepts side-chain inputs or a sampler with multiple outputs for separate effects processing.
If you need to reassign these mappings see the section below on 'Manual assignment of plugins loaded in effects slots'.
NOTE: Always name the Mixer tracks being used by the plugin. This ensures FL Studio knows they are being used by a plugin which can be important for PDC calculations, split-mixer track rendering and automatic track assignment.
Plugin Credits: Frederic Vanmol, Didier Dambrin