AUTOMATION

Internal Controller Plugins

In FruityLoops 3.2 or later, you can use special internal controller plugins (they can be either effects or generators) to move the controls for you programmatically. These plugins can, for example, follow special features of a sound (like volume envelope, as in the Fruity Peak Controller) and map them to the value of a control of your choice, or provide automatic LFO for controls where otherwise that would be impossible etc.

Linking a control to internal controller

The controller plugins provide special internal controllers in FruityLoops, that are used to link a control to the plugin. To link a control to such internal controller, right-click it and from the menu that appears click Link to MIDI Controller. The MIDI Remote Control dialog appears.

MIDI Controller:

This section allows you to link a control to a MIDI controller. For more information see Live Recording Using MIDI Controller.

Internal Controller:

Here you can configure a control to be linked to internal controller that a controller plugins provide. Note that this section is NOT VISIBLE when there aren't any controller plugins added in the current FruityLoops project.

Mapping Formula:

Here you can enter a formula that is used to map the controller values to the property you link. The default formula is 'Input', Input is the variable that holds the value of the controller (1:1 mapping). Now you can enter an expression to alter the default 1:1 mapping. For example: 'Input*2' multiplies the controller value by 2. When you write an expression, press Enter. If you see message "Compiled OK" the formula was successfully compiled and you can press the OK button to apply it to the linked control. If a red text appears below, the formula is wrong (usually syntax error or unsupported variable/function was used). Correct the error and press Enter again. For a full list of supported variables and function click here.

Internal Controllers List - This combo box contains a list of controllers provided by the controller plugins. Select a controller to link the control to it.
Record Automation - This switch should be usually turned off. When turned on, all events generated by the controller plugin will be recorded during a live recording session, as if you moved the control manually. However, you may turn this switch on if you want to use the controller plugin as a tool (like you use the LFO tool) to record specific set of events that you can then further refine and edit in the Event Editor window. It also makes possible to record events from controller plugins that might use much CPU when used in real-time. Don't forget to unlink the control after you recorded the events you need, not doing so may result in unwanted behavior (due to conflict between the recorded events and those generated in same time by the plugin).

Auto Detect

Very useful option that will detect and set the MIDI controller automatically - all you need to do is just tweak the desired control on your MIDI controller.

Remove Conflicts

When this option is checked, FruityLoops will remove conflicts, like linking two wheels to the same controller (either MIDI or internal).

Linking effects

If you want to automate a FruityLoops effect, you can proceed with it's controls exactly as with any FruityLoops control - right-click it to launch a pop-up menu, from where you can display the MIDI Remote Control dialog box. The same goes for VST effects that do not have their own editor's interface. Then FruityLoops provides interface for the plugin, and all wheels can be automated as usual.

To link VST effects that have their own interface, call the FX pop-up menu (see Effects Tracks window) and select Link to MIDI controller item. From the submenu that appears, either select All to link all effect's controls at once (for example, if you select controller 8, the first control is mapped to controller 8, the next one to controller 9 etc.), or select a property name to link it alone instead. Be warned that many third-party VST effects do not report properly their settings, and might crash when trying to link them to a MIDI controller. It is highly recommended that you save your project before mapping VST settings for remote control.

Unfortunately, there is no way to link DirectX effects to MIDI controller. That limitation comes from DirectX specifications, not from FruityLoops itself. Some DirectX plugins might have MIDI remote controller functionality, but NOT through the DirectX interface (so they can not be linked right inside FruityLoops). To link such effect, follow the help instructions that come with your DirectX plugin.