How to Use a MIDI Controller in REAPER (Full Setup)

Most guides on how to use a MIDI controller in REAPER stop after "tick the box in Preferences", which is roughly a quarter of the job. The other three quarters are getting a track to actually make noise, understanding why the knobs do nothing until you Learn them, and knowing which bindings follow you between projects and which do not. This walkthrough goes from a controller in the box to a recorded automation pass, in order, with nothing skipped.

How do I use a MIDI controller in REAPER?

Enable the device for both input and control messages, arm a track set to accept MIDI, put an instrument on it, then bind anything else by right-clicking and choosing Learn.

Those are the four moves. Everything below is each move in detail, plus the failure mode that goes with it.

Step 1 — Make REAPER see the controller

Connect the hardware before opening REAPER. If you are using a gamepad, start Universal Controller MIDI first so its virtual MIDI port exists — a gamepad is an HID device and REAPER cannot see it directly, the bridge is what turns it into a MIDI port.

Then: Options → Preferences → Audio → MIDI Devices. Find your controller in the MIDI inputs table and right-click it twice:

• Enable input — MIDI can now reach armed tracks.
• Enable input for control messages — MIDI can now reach the Learn engine and the Actions list.

Miss the second tick and you get the most common beginner symptom in REAPER: keys play perfectly, knobs do absolutely nothing, and MIDI Learn sits there looking blank. If the device is not in the list at all, click Reset all MIDI devices — REAPER enumerates at startup and anything created afterwards needs a rescan.

Step 2 — Build a track that can make a sound

A controller with nothing to control is silent, and that silence looks exactly like a broken setup. Fix it in four clicks.

1. Track → Insert new track (or Ctrl/Cmd+T).
2. Click the track's record-arm button so it lights red.
3. Click the input button next to it and choose MIDI → All MIDI Inputs → All Channels.
4. Click the small speaker icon to turn on input monitoring (it should read Record: input / monitoring on).

Now click FX on the track and add an instrument — VSTi: ReaSynth ships with REAPER and is fine for testing. Press a key or a button on the controller. You should hear a tone and see the track meter move.

If the meter moves but you hear nothing, the issue is your audio device, not MIDI: check Preferences → Audio → Device and confirm the correct output is selected. If nothing moves at all, go back to Step 1.

Step 3 — Bind transport so you stop reaching for the keyboard

Transport belongs in the Actions list, not in MIDI Learn on a fader, because action bindings are global and permanent.

Open Actions → Show action list. In the filter box type play/stop. Select Transport: Play/stop. In the Shortcuts for selected action box click Add…. A small window appears waiting for input — press the button on your controller. REAPER shows the captured message (something like MIDI Chan 1 Note 60). Click OK.

Repeat for the actions you actually use:

Action	Good control for it	Why
Transport: Play/stop	A large, central button	You press it hundreds of times a session
Transport: Record	A button you cannot hit by accident	Accidental record overwrites takes
Transport: Toggle repeat	Any spare button	Loop practice and comping
Markers: Go to next marker	D-pad right / a nav key	Section-to-section navigation without the mouse
Options: Toggle metronome	Any spare button	The click you turn on and off constantly

One detail that matters later: right-click any action and choose Copy selected action command ID to get its numeric ID. You will need those IDs the moment you write a script or bind over OSC — and reading them out of your own install is the only reliable way to get them right.

Step 4 — Learn a plugin parameter

Open the instrument's FX window. Right-click the parameter you want on a physical control — on ReaSynth, try Filter frequency — and choose Learn. Move the knob, fader, or trigger once. REAPER fills in the device, channel and CC for you.

Before you click OK, two settings are worth getting right the first time:

• CC mode: Absolute. Correct for faders, knobs with end stops, analogue triggers and gamepad sticks. Use Toggle only for buttons that should latch a state.
• Soft takeover. Tick it. Without it, the parameter snaps to wherever your physical control happens to be sitting the moment you touch it — which is jarring on recall and genuinely destructive mid-mix.

There is also Enable only when track is selected, which is the single most useful checkbox in the dialog. Tick it and that control becomes "the filter of whatever track I have selected" rather than "the filter of track 3". The full behaviour of every option in this dialog is broken down in the complete MIDI Learn guide.

Step 5 — Record what you play, and what you move

Notes and controller movements record differently in REAPER, and knowing which is which saves a confusing half-hour.

Recording notes

With the track armed and set to a MIDI input, hit record. REAPER writes a MIDI item. Double-click it to open the MIDI editor and quantise, edit, or redraw. Nothing special is needed — if you can hear the instrument while playing, you can record it.

Recording controller movements as automation

Parameter movements are not written into the MIDI item. They are written into an automation envelope. Click the Env button on the track (or Trim/Read/Touch/Latch/Write in the mixer) and set the mode to Latch or Write. Then record or simply play back while moving the control — REAPER draws the envelope live.

Set it back to Read afterwards. Leaving a track in Write mode is how people accidentally flatten a good automation pass on the next playback.

Can I use a games controller instead of a MIDI controller?

Yes. If you do not own a MIDI controller, you probably own a gamepad, and everything above applies unchanged once a bridge publishes it as a MIDI port — the PS5 DualSense route is the most common starting point, and the from-scratch REAPER setup covers the device list in more depth.

The mapping that works best for a first session:

• Face buttons → notes, for drum-rack style playing, or action bindings for transport.
• D-pad → navigation actions (next marker, previous marker, next track, previous track).
• Analogue triggers → absolute CCs on the two parameters you ride most. Triggers have real throw, so they behave like small faders.
• Sticks → two-axis parameters, with the bridge's deadzone raised enough that a resting stick sends nothing.

Save that as a preset in the bridge so the CC numbers never move under your bindings. The free tier stores three presets, which is enough for a tracking layout, a mixing layout and an editing layout; Pro removes the cap and adds curves, latch behaviour and conditional layers if you start building per-project maps. Download the bridge, or get Pro for $89 one-time.

What breaks first, and how do you fix it?

• No sound. Track not armed, input not set to MIDI, monitoring off, or no instrument on the track. Check in that order.
• Notes work, knobs do not. Control messages not enabled in Preferences.
• Learn grabs the wrong control. Something else is sending idle MIDI. Disable other inputs while you learn.
• Bindings gone after reopening REAPER. They were FX or track learns, which live in the project. Save a project template.
• Double notes. The same device exposed on two ports, both enabled. Disable the duplicate.
• A parameter twitches on its own. A worn pot or a drifting stick at rest. Raise the deadzone at the source — see the drift compensation guide.

FAQ

How do I use a MIDI controller in REAPER?

Enable the device in Options → Preferences → Audio → MIDI Devices with both Enable input and Enable input for control messages, arm a track with All MIDI inputs selected, then bind controls by right-clicking them and choosing MIDI/OSC Learn.

Why can I hear nothing when I press keys on my controller?

The track needs three things: record-arm on, the input set to a MIDI source, and input monitoring enabled. Without an instrument plugin on the track there is also nothing generating sound.

What does All MIDI inputs mean in the track input menu?

It accepts MIDI from every device you enabled in Preferences, rather than one specific port. It is the simplest choice when you have a single controller and the right choice when you swap controllers often.

How do I record what I play from a MIDI controller?

Arm the track, set the record mode to MIDI (the track record-mode button cycles through audio and MIDI options), press record, and play. REAPER writes a MIDI item you can open in the MIDI editor.

Can a games console controller be used as a MIDI controller in REAPER?

Yes, with bridge software that converts the controller's HID output into a virtual MIDI port. REAPER then treats it exactly like any other MIDI controller.

Do I have to remap my controller in every project?

No. Transport and navigation bound through the Actions list are global. Only FX and track bindings are per-project, and a project template carries those into every new session.

Wrap-up

The order matters more than the settings: see the device, make a sound, bind transport globally, bind parameters locally, then save a template. Done in that sequence, a controller goes from box to useful in a quarter of an hour. The REAPER user guide is the reference once you want to go further.

Download Universal Controller MIDI if the controller you want to use is a gamepad — same workflow, no new hardware.