Mouse & Controller Recording
The following section shows how to record the movement of FL Studio and plugin interface controls. Movements can be made with either your mouse or any linked
external hardware controller. Once movements are recorded they will play back as part of the project performance, perfect for automating mixes and synthesizer controls.
Mouse or external controller movements can be recorded and played back as part of the project. To record the mouse movements simply move the target control while the project is
playing in record mode. In order to record an external controller it needs to be linked to an automatable parameter in FL Studio (e.g. knobs, sliders, LCDs, switches).
- Select the target control/s: For mouse control you will simply click on any target control/s and move them while FL Studio is recording. External hardware controllers must first be
linked to the interface target/s.
Any number of links can be made, limited only by the number of unique controls on your hardware.
- Select the Pattern: The automation will be recorded into the selected Pattern. If you automate more than one control during the session all automation
will be recorded into the same pattern. The Event Editor allows you to independently select and edit the all the automation data associated with the pattern.
- Turn on the Automation recording filter: Right-click the Record button and make sure 'Automation' is selected as a recording type (all data types with a tick will be
- Arm for Recording: Click the record button in the Transport Panel, it will turn red to show FL Studio is ready to record.
- Press Play. FL Studio will play the project and record any movement of controls animated by your mouse or controller keyboard.
- Press stop.
Where is my automation data stored?
Automation data recorded from live mouse or controller movements is recorded into the Event Editor associated with the pattern that was selected
during the recording session. You will find all automation in the current project listed in the Current project > Patterns folder in the Browser. You have two choices after recording the automation how it should be stored:
- Patterns: Automation Event data remains associated with the pattern it was recorded into. This Event data can be further edited using the
Event Editor. When you place the pattern in a Clip Track the automation data will remain synced to its pattern.
Event data shows as a background image in the Pattern Clip. Also note that Event Automation remains active in either Pattern or Song mode.
- Automation clips: Event data can be converted into Automation Clips. The conversion is initiated from the Event
Editor (Main menu > Turn into Automation Clip). Note that Automation Clips must be placed in the Clip Track area of the Playlist to become active in the
song and you may need to manually align them with the correct part of the Project. In other words, the sync between the original Pattern the automation data was recorded into is lost, and the Automation Clip must now
be synced to the Playlist time-line. Reestablishing the relationship is not difficult, just start the related Pattern and Automation Clip on the same bar in the Playlist.
Recording score/note data
See the section on score/note recording.
Cancelling a recording session
You can cancel a recording session (so it does not apply the recorded notes
and automation events) in two ways. The first one is to choose Cancel
Current Recording command from Help menu,
but note that you should do this while recording, BEFORE pressing the Stop
button. If you press it, you can still undo the whole recording session by choosing
Undo from the Edit Menu. If you had recorded mixer tracks during the last session, you will be prompted if you agree that the files are erased (i.e. undone). Be careful, because once you undo audio recording, the files can not be restored and you will have to record them again if needed.