Fruity Wrapper brings compatibility with Steinberg's VST2/VSTi plugins and DXi2 plugins (the screenshot above demonstrates Fruity Wrapper hosting Audio Simulation's DreamStation DXi2 plugin). For more information on those plugins formats. For more information on installing and using 3rd party VST/DX plugins.


The Fruity wrapper comes in 2 versions: effect & generator. While the effect version provides a complete support for both effects and generators, the generator version is more intuitive and fast to use as it doesn't require (but still supports) a MIDI Out channel to send note messages to the plugin.

Parameters

  1. Input/Output Port - Allows you to set the input/output MIDI port mapping for the hosted plugin (depending on the selection in the Additional Settings Menu, see below).
  2. Additional Settings Menu - Additional menu with plugin specific commands. This menu differs for VST2/VSTi and DXi plugins. See Additional Settings Menu below.
  3. Context Menu - The standard FL Studio plugin menu.
  4. Select a Plugin - This button allows you to replace the hosted plugin with another one.

Additional Settings Menu

The menu contains various plugin specific commands such as preset management, MIDI mapping and service functions. The commands are different depending on the type of plugin loaded in the wrapper.

Common commands

The following items appear for all plugins:

  • Show MIDI In Port / Show MIDI Out Port - These menu items let you display either the assigned MIDI input or output port (1) assigned to the plugin.
  • Reload Current Plugin - A quick way to reset the plugin to its initial state.

VSTi/VST2 commands

Most of the VST plugins come with a bank of factory presets called programs. Programs are defined inside the plugin, unlike presets saved as physical files (similar to the FL Studio state file (FST)), however they can still be redistributed in the form of Cubase FXB files (full program banks) and Cubase FXP files (separate programs saved as presets).

The default program bank is loaded with each instance of the plugin and its programs can be modified and renamed in the span of that specific plugin instance. Any changes to the plugin instance's programs or banks are saved in the FL Studio state files (FST) and FL Studio project files (FLP). Resetting the plugin (via using Reload Current Plugin) restores the original "factory" program bank defined for the plugin.

The commands in this section deal with managing plugin's bank of programs.

  • Allow Program Editing - The default behavior of FL Studio is to treat the plugin programs as "read-only", meaning that loading a program, modifying the plugin settings further and reloading the same program will not keep the custom modifications. Enable this option to allow program modifications for the current plugin instance much like how many other VSTi hosts operate.
  • Rename Program - Allows you to rename to currently active program. Allow Program Editing needs to be turned on for this command to be enabled.
  • Copy Program - Copies to currently active program to the clipboard. Allow Program Editing needs to be turned on for this command to be enabled.
  • Paste Program - Overwrites the settings of the active program with the program in the clipboard. Allow Program Editing needs to be turned on for this command to be enabled. The command will be disabled in the clipboard is empty (you need to copy a program first).
  • Import Cubase Bank/Preset - Allows you to import a standard Cubase bank (FXB) or preset (FXP) in the currently hosted plugin instance. A bank replaces all of the the programs for this plugin instance, while loading a preset replaces only the currently active program.
  • Export Cubase Preset - Allows you to export the current program as a Cubase preset (FXP).
  • Export Cubase Bank - Allows you to export the entire program library (including any additional loaded or modified programs in it) as a Cubase bank (FXB).

DXi commands

  • Use Big Buffers - FL Studio optimizes data flow and processing via using very small variable sized buffers. While the majority of plugins are completely compatible with such processing, some DXi plugins might cause problem. In this case enable this option so the wrapper provides a compatibility mode for the plugin