FL Studio's right-click → Link to controller dialog is the most flexible mapping system in any DAW. It does not care if your controller is a Push 3, a $20 nanoKEY, or a PS5 DualSense — it just needs MIDI. This guide turns a DualSense into an FL Studio MIDI controller in under ten minutes, with a default preset that covers channel rack steps, plugin knobs, mixer sends, and a touchpad XY pad ready for the Patcher.

TL;DR

What you do: bridge the DualSense to virtual MIDI, enable it under FL's MIDI Settings, right-click Link to controller on anything.
What you need: FL Studio 21+, Windows 10+ or macOS 12+, a DualSense, Universal Controller MIDI v1.0+.
Time: 8–10 minutes from cold install to a stick driving a Sytrus filter.
Cost: the controller you already own. Bridge free to try, $49 for Pro.

Why use a gamepad in FL Studio

FL Studio's interface is built around tactile workflow — step sequencer, channel rack, mixer racks, piano roll. A mouse is fine; a DualSense gives you a second set of hands. Sixteen tactile inputs, two clickable analog sticks for four continuous knobs, two analog triggers for filter or send rides, and a clickable touchpad for XY automation. That stacks up against a $300 mid-tier MIDI controller, with a form factor that fits on your lap.

The Image-Line crowd has been remapping gamepads to FL for years via JoyToKey-style hacks. The clean version is a real virtual MIDI bridge — what Universal Controller MIDI does — so the controller appears as a first-class MIDI device, not a fake keyboard.

What you'll need

Universal Controller MIDI v1.0 or later (download)
FL Studio 21.0+ — any edition that includes MIDI input (Producer and above)
Windows 10+ or macOS 12+
A PS5 DualSense or DualSense Edge — wired USB-C strongly recommended for any tracking
A USB-C data cable (charge-only cables will pair but not enumerate)

Step-by-step setup

1. Install and plug in

Run the installer. On Windows the bridge registers its own kernel-level virtual MIDI driver during install — accept the driver-signing prompt. On macOS drag the app to Applications and launch. Plug the DualSense in over USB-C and confirm the status pill is green.

2. Enable the virtual MIDI port (macOS only)

On macOS open Audio MIDI Setup, Window → Show MIDI Studio, double-click IAC Driver, tick Device is online, and ensure at least one port exists. On Windows skip this step entirely — the bridge ships its own port.

3. Load the FL Studio preset

In the bridge UI pick Presets → FL Studio (default). Buttons map to channel rack steps 1–8 on a Shift layer, sticks drive plugin knobs as CCs 3–6, triggers ride CC 1/2, touchpad sends CC 16/17.

4. Enable the controller inside FL Studio

Launch FL Studio. Options → MIDI Settings (or hit F10). In the Input list find Universal Controller MIDI, click it, hit Enable, and set the Controller type to Generic Controller. The activity LED next to the port should flicker as you move sticks.

5. Link anything with right-click → Link to controller

Find any control in FL Studio — channel volume, plugin knob, mixer send, automation clip target — right-click it, pick Link to controller…, then move the gamepad input you want to bind. Tick Auto detect in the link dialog so FL captures the CC automatically.

Liking the workflow? Get Pro for $49 — one-time, owned forever. Pro unlocks unlimited preset slots, FL-specific Shift layers, and adaptive trigger output for haptic feedback.

Mapping ideas that ship

Face buttons as channel rack mute/solo on a Shift layer. Hold L1, then cross/circle/square/triangle toggle mute on channels 1–4. Release L1, the same buttons trigger pattern launch.
Triggers ride the selected mixer track's parametric EQ 2. L2 sweeps low cut, R2 sweeps high cut. Best mixing experience you can have with one hand on a coffee.
Right stick is the Pitcher chord input. Map X to pitch, Y to formant — instant vocal harmoniser via thumb.
Touchpad XY into the Patcher. Drop CC 16/17 into a Patcher chain driving Fruity Filter cutoff + Fruity Reverb 2 dry/wet. Two-finger sweeps from clean to wash.
D-pad navigates the playlist. Bind to FL's Move time marker commands for hands-off arrangement scrubbing.

Mapping snippet — Patcher XY routing

{`# Inside the bridge preset editor, FL Studio Patcher block
{
  "name": "Touchpad → Patcher XY",
  "bindings": [
    { "input": "touchpad.x", "midi": { "type": "cc", "channel": 1, "cc": 16 } },
    { "input": "touchpad.y", "midi": { "type": "cc", "channel": 1, "cc": 17 } },
    { "input": "touchpad.click", "midi": { "type": "note", "channel": 1, "note": 90 } }
  ]
}`}

Gotchas

FL Studio caches MIDI ports at startup. Launch the bridge first, then FL. Re-enumerating mid-session requires a restart.
Link to controller grabs the wrong input. If FL is also seeing keyboard noise on another port, disable everything except UCMIDI in the MIDI Settings Input list before learning.
Touchpad jitter when the finger lifts. Drop the touchpad smoothing in Settings → Touchpad from 0.15 to 0.08.
FL freezes on Bluetooth dropout. Known FL quirk with stale MIDI ports — keep the controller wired for any session you cannot afford to lose.

Wrap-up

FL Studio's mapping engine plus a DualSense covers ninety per cent of what most producers use a $300 controller for, and the bridge takes ten minutes to wire up. The FL Studio MIDI Settings manual is worth a skim if you want to push into Live Mode or remote scripts.

Download Universal Controller MIDI and the DualSense in your drawer becomes the FL Studio surface you never bought.

FL Studio + PS5 DualSense MIDI Controller Setup