
Mapping the parameters of Lié to the MIDI CCs it expects from Touché (SE) MIDI CC #81 (General purpose controller 6) MIDI CC #80 (General purpose controller 5) MIDI CC #19 (General purpose controller 4) MIDI CC #18 (General purpose controller 3)

MIDI CC #17 (General purpose controller 2) MIDI CC #16 (General purpose controller 1) Scroll down until you find these six entries:

Therefore, we have to manually map the MIDI CCs that Lié needs to function to the Touché (SE) hardware. Unfortunately, by default, FL Studio does not forward the MIDI CCs that come from Touché to our companion app Lié. Open FL Studio's Plugin Manager to manage the directories that are scanned via Options -> Manage Plugins.įor more information on the subject, please refer to Image-Line's online manual.Ĭreating the missing CC link between Touché and Lié This is among the standard folders that FL Studio expects your VST2 plug-ins to be in. In Windows, if you haven't made any changes during installation, the Lié.dll (plug-in file in VST2 format) is placed inside C:\Program Files\Vstplugins. In macOS, Live will scan the default folder for VST and AU plug-ins, which contain Lié. Scanning Lié inside FL StudioįL Studio scans its plug-in database on every launch. This article explains how to set up Touché or Touché SE to work within Image-Line FL Studio 20.
