Fl Studio Performance Mode

Fans of Ableton Live or Bitwig are going to like this one, as well as anyone that does live performance.

I’ll be covering FLStudio’s “Performance Mode”, which is similar to Live/Bitwig’s session mode, and I’ll be discussing the Video FX in FL.

Other posts in this series:

  • Performance Mode

In this step-by-step guide Arlo Giunchi explores the process of beat juggling in FL Studio’s performance mode 1: In a new project use Tools Macros Prepare for performance mode. The project will be adapted for use with markers corresponding to 16 pad zones. Use F4 to create a new empty pattern. 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’. The Playlist - Performance Mode Performance Mode is saved per-project and lets you trigger Clips from the Playlist to play in any order. When the project is playing use a mouse or touch on the Playlist, the typing keyboard or a controller to trigger Clips. The purpose is to create 'remixes' of a projects Clip content (Audio, Pattern & Automation). FL Studio does not allow for native use of VST instruments however, FL Studio has a built-in VST wrapper which does allow for the inclusion of third-party VST instruments. Because of the use of this wrapper, Hybrid 3 can open and be used in FL Studio, however the MPK mini MKII series controller will not automatically map to the various. The Playlist - Performance Mode Performance Mode is saved per-project and lets you trigger Clips from the Playlist to play in any order. When the project is playing use a mouse or touch on the Playlist, the typing keyboard or a controller to trigger Clips. The purpose is to create 'remixes' of a projects Clip content (Audio, Pattern & Automation).

What is Performance Mode

Fl Studio Live Mode

When clips are triggered is configurable, so you can set up the trigger sync to quantize your triggering to the next bar, beat divisions, clip length, or a neat ‘tolerant’ mode. Tolerant mode lets you miss triggering a clip on time and will trigger it anyway in sync rather than waiting for the next quantized time.

If you are used to Live or Bitwig there’s some things that you may find particularly interesting:

  • Each cell can have multiple clips (sub-clips), and you can cycle through these.
  • There’s more “time freedom”, so you can visually setup your clips in a manner that makes the most sense to you. Since your tracks are defined horizontally, and scene starts can be flexibly positioned, you can do some neat things with organization.
  • You can group clips to make them play together, even across scenes.
  • There is a default computer-keyboard launching method. This gives you 5 scenes and 8 tracks of easy clip launching without messing with a controller.
  • FL’s routing flexibility still applies. Since a playlist track does not determine routing you can have multiple clips on a single playlist track that go to separate mixer tracks. Read more about this here
    • REALLY this is a big deal. It greatly improves the flexibility of what you can do. This means you can have different clips/synths/effects on a single trigger scene that are sent to different mixer tracks. You could have all of your basses on a single playlist track, but each clip going to a different mixer track to help you seamlessly blend them and add clip-specific FX to them to add flair to your performance.

How is Performance Mode?

It’s great.

Nfs most wanted 2005 full version

I toured playing drums and percussion with a band, and using an APC 40 with Ableton Live I triggered clips and handled lighting. I have spent 100s of hours with Live and a pad controller on stage.

Let me tell you right now: I wish I had FLStudio back then. The flexibility of routing is a joy. The sub-clips (clips that trigger on next press of the cell) functionality is useful.

The main downsides are:

  • The limited number of tracks/scenes. You just get 12x10 by default via MIDI, and setting up more is a hacky experience unless you have a supported controller. I was unable to find any ‘banks’ or ways to move around a grid larger than 16x16 unless using a specific controller, and this appears to be hit-or-miss.
    • The upside here is that some controllers have fantastic mapping. check out the launchpad mapping, it’s really fantastic. Faders, XY control, multiple plugin controllers, tempo control, project commands and more. Unfortunately not everything has this, and setting this up yourself… well, good luck.
  • Launch settings are per track, not per clip. If you want clips to have different launch modes or their ‘play next’ type behaviour to change, too bad. It’s per playlist track.
  • No follow actions, which are a powerful part of a well-designed live set.
  • Tools->Macros->Prepare for performance mode is not undoable. If you want to try something out or test some ideas, it’s not nearly as simple as Live or Bitwig for clip launching. However, if you start your project in a ‘performance mode’ setup then this is no longer an issue. It requires some forethought.
  • FLStudio needs to be playing for performance mode to work. This can cause some issues with any modulation you have or automation you want to keep on a per-clip basis.

Fl Studio Performance Mode Midi Keyboard

The counterpoint to that last point is that automation clips are clips. You can trigger automation like it’s any other clip, so you can create effects breaks or transitions or turn on/off effects or anything you can think of! It’s surprising how awesome this can be.

Mode

The clip grouping feature is fantastic too. No matter where two clips are on a track or scene, you can group them together and they will play when any of them is triggered. This lets you create more thematic elements in your performance that can be reused elsewhere.