The Impact LX FL Studio Integration is compatible with Fl Studio 11.1.1 RC3 or later.
FL Studio Performance Mode Demo - Sacco. February 28, 2016 Sacco demonstrating FL Studio's Performance Mode at Dancefair 2016.
- In FL MIDI settings set a Performance mode MIDI channel. Say you set this to 10. Then when you set your controller keyboard to output on MIDI channel 10 it will trigger clips in Performance mode. Set it back to a different MIDI channel to play notes instead.
- Many stock FL Studio plugins have oversampling options built in, Sytrus f.e. Has two: one for render and one for the live preview. Try to keep oversampling to a minimum as it often more than doubles the CPU a plugin will use. If the plugin has a draft or economy quality mode, use it.
Fl Studio Performance Mode Midi Mapping
These instructions assumes you have FL Studio installed running on Windows or OS X. There are no files you need to download, only follow the instructions below.
- Plug-in your Impact and make sure to switch it on (if you didn’t do so already)
- Launch FL Studio and go to Options/MIDI Settings (image 1 for Windows, image 2 for OS X)
- The Impact ports should now appear in the FL Studio window as per Image 1 and 2. If you don’t see them, click ‘Rescan devices’ at the bottom of the window.
- The Output port Impact LX** should be set to port ‘155’
- Enable input port ‘Impact LX**’ (in Windows) or ‘Impact LX** MIDI1’ (in OS X) and set Controller Type to ‘(generic controller)’
- Enable input port ‘MIDIIN2 (Impact LX**)’ (in Windows) or ‘Impact LX** MIDI2’ (in OS X) and set Controller Type to ‘Nektar Impact series’
- Set ‘MIDIIN2 (Impact LX**)’ (in Windows) or ‘Impact LX** MIDI2’ (in OS X) to port ‘155’
- Exit MIDI settings
That’s it, setup is now complete and you can move on to the fun part, learning how it all works.
Image 1) Windows
Image 1) Impacts MIDI ports should be configured as per the above in Windows
Image 2) OS X
Image 2) Impacts MIDI ports should be configured as per the above in OS X
Fl Studio Performance Mode Tutorial
Patch Changes
If you find that the [< Patch] and [Patch >] buttons don’t work when controlling a third-party plug-in, it’s likely because the plug-in uses it’s own patch browser. The Patch buttons on the Impact series control the patch navigation functions of the DAW, so you may need to save the plug-ins presets in your DAWs patch format, before you can use the Patch buttons on the Impact controller for patch navigation. You can find more information about saving patches in your DAW, in the documentation for that program.