How to Use a MIDI Controller: Plug In, Pick the Input, Then Play
You plug in a new keyboard, its lights come on, and the piano in your software stays silent, which is when you start searching for how to use a MIDI controller.
The reason is that most controllers make no sound of their own, so nothing plays until the software has been told to listen.
This guide follows one first session in order, using the setup steps in Ableton’s, FL Studio’s, Apple’s and Microsoft’s own documents and in the Novation, Akai and Korg manuals.
You’ll see what a controller sends, how to connect it, how each program picks it up, what the pads and knobs do, and what to check when nothing plays.
Start with the five steps, because they fix most first sessions.
How to Use a MIDI Controller in Five Steps
Those five steps hold on nearly every brand and in nearly every program. You use a MIDI controller by connecting its USB cable, switching it on as a MIDI input in your software, loading an instrument on a track, arming that track and then playing.
| Step | What you do | How you know it worked |
|---|---|---|
| 1. Connect | Plug the USB cable into the controller and straight into the computer | The controller’s lights come on, since a USB bus-powered unit gets its power from the cable |
| 2. Pick the input | Open the program’s MIDI settings and switch the controller on as an input | An activity light blinks when you press a key, such as Ableton Live’s MIDI indicator or FL Studio’s MIDI activity light |
| 3. Load an instrument | Add a software piano or synth on a new track | The track shows the instrument’s name |
| 4. Arm the track | Press the track’s arm or record-enable button | The track is ready to listen, and in Live the default monitoring turns on while it’s armed |
| 5. Play | Press keys, hit pads and turn knobs | You hear the instrument through the computer’s headphones or speakers |
If a step fails, the troubleshooting table further down matches each symptom to a fix.
What Does a MIDI Controller Actually Send?
That order works because a controller sends instructions, not sound. FL Studio’s manual calls MIDI a control-data connection that carries keyboard notes, knob movements and sound changes rather than audio (FL Studio).

The MIDI Association’s message list says each key press sends a Note On message with a key number and a velocity value, and releasing the key sends a Note Off (MIDI Association). Knobs, faders and pedals send Control Change messages with a controller number and a value from 0 to 127, and all of it travels on one of 16 channels.
The same association’s controller table gives number 1 to the mod wheel, 7 to channel volume, 10 to pan, 11 to expression and 64 to the sustain pedal, where values of 64 and above mean the pedal is down (MIDI Association). The list also covers aftertouch, which is extra pressure on a key after it bottoms out, program changes that switch patches, and pitch bend, which uses a finer 14-bit value.
| Control | What it sends | Where you notice it |
|---|---|---|
| Keys | Note On and Note Off, with velocity | Which note plays and how hard |
| Pads | Notes, with velocity | Drum hits or samples |
| Pitch wheel | Pitch bend | Notes sliding up or down |
| Mod wheel | Control Change 1 | Vibrato or whatever the instrument assigns |
| Knobs and faders | Control Change numbers, with values from 0 to 127 | Volume, filter or any parameter you map |
| Sustain pedal | Control Change 64 | Notes holding after you let go |
Because the controller only sends data, the instrument that receives it decides what you hear, so the same keys can play a piano on one track and a bass on the next.
Get Studio Tips Weekly
Join 5,000+ creators getting acoustic treatment advice every week.
No spam. Unsubscribe anytime.What Do You Need Before You Start?
Those messages need three things to become music: a cable to carry them, a program that understands them and an instrument that makes the sound. The cable is almost always USB, and the port differs by model: Novation’s Launchkey Mini 37 has a USB-C port (Novation), while Akai’s MPK mini Plus and Korg’s microKEY2 use USB Type-B (Akai, Korg).
The program can be a full music program such as Ableton Live or FL Studio, or GarageBand on a Mac, and many makers bundle a starter program, such as Ableton Live Lite with Novation’s Launchkey or MPC Beats with Akai’s MPK mini Plus. The sound comes from the computer rather than the controller, since Akai’s setup steps end with hearing the instrument through headphones or speakers connected to the computer.
Power usually rides on the same cable, since Novation’s Launchkey and Korg’s microKEY2 are USB bus-powered and Korg lists the microKEY2’s draw at under 100 mA (Korg).
How Do You Connect a MIDI Controller to a Computer?
Those pieces meet at the USB port, which carries the data and the power. You connect a MIDI controller by plugging its cable into a port on the computer and letting the system detect it.
On Windows, Microsoft says most USB MIDI 1.0 devices are class-compliant and work without third-party drivers, and it advises against installing extra ones unless they’re needed (Microsoft). Windows 11 25H2 and later with updates turned on already includes Windows MIDI Services, which Microsoft says lets several apps use the same MIDI device at the same time.
On a Mac, Apple’s Audio MIDI Setup guide says a MIDI interface connected by USB is usually detected automatically and shown in the MIDI Studio window (Apple). Our walkthroughs for plugging a MIDI keyboard into a MacBook and setting one up on a Windows PC go further on each system.
Korg’s page for the microKEY2 says a bus-powered keyboard needs one USB cable on a Mac or Windows PC and no driver (Korg). Some makers add a first-run step: Novation’s guide says the Launchkey first appears as a USB drive holding a link to its Easy Start guide, and that the firmware should be updated through Novation Components right away because many features won’t work without it (Novation).
FL Studio’s manual advises connecting the controller before opening the program and plugging it straight into the computer instead of a USB hub (FL Studio). Akai’s guide says a hub must be powered if you use one, and FL Studio adds that Windows users should switch off the “USB selective suspend” setting, which puts idle ports to sleep and can cause intermittent connection failures.
A keyboard with only 5-pin MIDI sockets will probably need a USB-to-MIDI adapter, and FL Studio’s manual says you need two MIDI cables for two-way communication and one for one-way. The MIDI Association notes that MIDI 1.0 was first published in 1983 with a serial transport on 5-pin DIN connectors (MIDI Association).
Where Do You Switch a Controller On in Your Software?
That detection happens in the operating system, and each program still needs the controller switched on as an input. You switch a controller on in the program’s MIDI settings by enabling it as an input.

In Ableton Live, open Settings with Ctrl+, on Windows or Cmd+, on a Mac, choose the Link, Tempo & MIDI tab and switch Track on for the controller’s input port (Ableton). Ableton says Track lets Live receive the notes and control changes that play instruments and record clips, and the Control Bar’s MIDI indicators flash when a message arrives.
In FL Studio, choose Options, then MIDI settings, or press F10, click the controller in the Input list and press Enable. The MIDI activity light on the Main Panel blinks when a note or knob move arrives, and the manual says the “Enable MIDI remote control” option in the Options menu must be on or MIDI input stays disabled.
In GarageBand, Apple says to choose GarageBand, then Settings, and click Audio/MIDI, where the MIDI Controller line shows the last connected controller and lets you choose one when several are connected (Apple). Akai’s guide tells users of other programs to pick the controller in Preferences, Options or Device Setup (Akai).
If a Mac doesn’t show the device, Apple says to open Audio MIDI Setup, choose Window, then Show MIDI Studio, and click Rescan MIDI (Apple). GarageBand’s Audio/MIDI settings also have a Reset MIDI Drivers button that reloads devices when you’ve lost the connection to them.
| Program | Where to look | Sign it’s working |
|---|---|---|
| Ableton Live | Settings, Link, Tempo & MIDI, then Track on the controller’s input | The Control Bar’s MIDI indicator flashes |
| FL Studio | Options, MIDI settings (F10), select the device, press Enable | The MIDI activity light blinks |
| GarageBand | GarageBand, Settings, Audio/MIDI | The MIDI Controller line shows your controller |
| Other programs | Preferences, Options or Device Setup | See the program’s manual |
| macOS | Audio MIDI Setup, Window, Show MIDI Studio | The device appears, or Rescan MIDI finds it |
What Turns the Notes Into Sound?
That switch delivers notes, but sound only comes when an instrument receives them. An instrument on an armed track turns the notes into sound, and you hear it through headphones or speakers connected to the computer.
In Live, the default Auto monitoring setting turns monitoring on while a track is armed, so an armed MIDI track with an instrument plays as soon as notes arrive (Ableton). Novation adds that its Launchkey soft-arms the track you select with the Track buttons in Live so you can play it straight away (Novation).
If the controller is a keyboard with its own sound engine, Ableton’s manual says to check its Local Off function so the keys play only what the software sends, and that Track only needs switching on for its output port when it has a built-in sound generator. The MIDI Association describes Local Control Off as making a device respond only to MIDI data it receives and ignore what’s played on its own keys (MIDI Association).
If you played something good before pressing record, Live’s Capture MIDI button turns the notes you just played into a clip. FL Studio’s manual says it stores the last 3 minutes of controller notes, and its “Dump score log to selected pattern” command sends them to the piano roll (FL Studio).
A gap between key and sound usually comes from the audio buffer, and Ableton’s manual recommends the lowest buffer size your audio hardware allows, set in the Audio tab of Settings, plus an ASIO driver on Windows. Our guide to cutting MIDI keyboard latency covers the fixes in order.
What Do the Keys, Pads, Knobs and Wheels Do?
Once sound comes out, each part of the controller is worth learning one at a time. The keys play notes, the pads trigger drums and samples, the knobs and faders move whatever they’re mapped to, and the wheels bend pitch or add modulation.

Each key sends a velocity value that rises with how hard you press it. FL Studio’s Velocity Curve button reshapes that response, Novation’s Launchkey offers Soft, Normal, Hard and Fixed key curves, and Korg’s KONTROL Editor adjusts the microKEY2’s curve.
Octave buttons shift the whole range: Novation’s Octave + and Octave − buttons transpose the Launchkey Mini by octaves and pressing both resets it (Novation), Akai says its buttons and keys reach a ten-octave range, and Korg lists a shift of −4 to +4 on the microKEY-37.
Pads are velocity-sensitive too, and Akai says its eight pads trigger drum hits or other samples in two banks, while the Launchkey Mini’s 16 pads switch between Drum, Chord and DAW modes. Knobs and encoders control whatever the maker or you assign, and on the Launchkey Mini the eight encoders follow Plugin, Mixer, Sends and Transport modes that you choose by holding Shift and pressing a top-row pad.
The pitch wheel bends notes and the mod wheel adds variation such as vibrato, Akai’s four-axis thumbstick can send pitch bend or control changes, and the Launchkey Mini uses touch strips instead of wheels. A sustain jack takes a foot pedal, though Novation’s supports only sustain pedals and momentary foot switches, not expression, soft or sostenuto pedals.
How Do You Map a Knob or Fader to a Control?
Those knobs do what the maker’s scripts say at first, and each program lets you change that. You map a knob by telling the program which parameter to move and then turning the knob once.
If your controller appears in Live’s Control Surface chooser, Ableton says Live assigns its knobs to the selected device automatically through “instant mappings” (Ableton). To assign your own, enable Remote for the controller’s input port, press the MIDI switch in Live’s upper right corner, click a parameter and turn the knob, then press the switch again to exit.
The catch is that keys or pads mapped this way stop playing notes, because Live uses mapped MIDI messages for remote control instead of passing them to MIDI tracks. Ableton calls that a common cause of confusion and points to the Control Bar’s indicators, and a Backspace or Delete press on a mapping in the Mapping Browser removes it.
In FL Studio, right-click the knob or slider, choose Link to Controller and move the knob on your hardware; for several at once, press Ctrl+J, move the targets on screen, then move the hardware controls in the same order (FL Studio). Our page on linking a knob to an FL Studio control walks through it, and Novation says the Launchkey’s FL Studio plugin mappings are fixed presets, with the Custom encoder mode as the way to build your own for third-party plugins.
Knobs that send absolute values from 0 to 127 can make a parameter jump if the knob and the software disagree, and Ableton’s manual describes relative knobs, which only say a little more or a little less, as the way to avoid that.
What Can Go Wrong the First Time?
These problems show up most often, and each has a first thing to check.
| What you see | Likely cause | What to check |
|---|---|---|
| No lights on the controller | It isn’t getting power | Use a port directly on the computer, since FL Studio’s manual warns that hubs can cause connection and power problems and Akai says a hub must be powered |
| Lights on, but the program lists no device | The computer or program missed it | Close the program, reconnect the controller, wait for the computer to detect it and reopen the program, as FL Studio’s manual says; on a Mac, use Rescan MIDI in MIDI Studio |
| Device listed, but no notes arrive | The input isn’t switched on | Ableton needs Track on, FL Studio needs Enable and “Enable MIDI remote control”, and GarageBand’s Audio/MIDI settings can reset the MIDI drivers |
| Notes arrive, but nothing plays | No instrument on the armed track | Load an instrument, arm the track and check the computer’s headphones or speakers |
| Keys trigger buttons or clips instead of notes | A remote mapping has taken them | In Live, leave MIDI Map Mode and delete the mapping in the Mapping Browser |
| The sustain pedal works backwards | The pedal’s polarity is reversed | Check your manual, since Arturia’s KeyStep manual says to power the unit off and on so it senses the polarity and also offers Normal, Inverted and AutoDetect settings |
| Sound lags behind the keys | The audio buffer is large | Lower the buffer in the Audio settings, and use an ASIO driver on Windows |
| A second program can’t see the controller | The first program may have it open | Close the first program and reopen the second, or use Windows 11 25H2 or later, where Microsoft says several apps can share a device |
Check the table from the top, because the first two rows rule out power and detection before you touch any settings.
Can You Use a MIDI Controller Without a Computer?
Those fixes all assume a computer, but a controller with MIDI sockets can play hardware directly. You can use a MIDI controller without a computer by connecting its MIDI out to a hardware synth, if it has a MIDI out socket and a power source.
Novation’s Launchkey 37 has a 5-pin DIN MIDI out, while the Launchkey Mini 37’s out is a 3.5 mm TRS jack, so a 5-pin synth needs an adapter cable that isn’t in the box. Akai’s guide shows the MPK mini Plus connected to a synthesizer, a sustain pedal, an external MIDI device and a computer, and says that when a wall adapter powers it, MIDI data goes to the 5-pin out by default.
Power is the other half, and Arturia’s KeyStep 37 mk2 manual says a standard USB mobile phone charger rated at least 5 V and 100 mA can run it without a computer present. Korg’s microKEY2 page says an iPad or iPhone works through Apple’s Lightning to USB camera adaptor, which is sold separately, and our guide to playing a MIDI keyboard without a computer covers the options.
Which Controller Is Easiest to Set Up First?
Those setup details show that the first controller matters less for key count than for how little it asks of you on day one. For the least setup, the Korg microKEY2-37 asks for a single cable and adds only wheels, octave buttons and a pedal jack.

the Korg microKEY2-37
For hands-on control of your program, the Novation Launchkey Mini 37 MK4 adds 16 pads and eight encoders, and Novation says it works with Ableton Live, Logic Pro, FL Studio, Cubase, Reaper, Reason and Ardour with no set-up required, though its guide says to update the firmware first.

the Novation Launchkey Mini 37 MK4
For drums and hardware, the Akai MPK Mini Plus adds eight pads in two banks and 5-pin MIDI in and out, and its guide gives the GarageBand and MPC Beats steps.

the Akai MPK Mini Plus
The Bottom Line
Plug the controller straight into the computer, switch it on as a MIDI input in your program, load an instrument on an armed track and play, and the rest of the controller is a matter of mapping.
If nothing plays, check power and detection first, then the input switch, then the instrument and arming, in that order.
Frequently Asked Questions
How do I use a MIDI controller for the first time?
Connect it by USB, switch it on as a MIDI input in your program’s settings, load an instrument on a new track, arm the track and press a key. If the program’s MIDI light blinks but you hear nothing, the instrument or the arming is the missing piece.
Do I need drivers for a MIDI controller?
Usually not. Microsoft says most USB MIDI 1.0 devices are class-compliant and work without third-party drivers on Windows, and Korg says its microKEY2 needs no driver on a Mac or Windows PC, though Apple’s GarageBand guide tells you to follow the keyboard’s own instructions because some need a driver.
Why does my MIDI controller light up but make no sound?
Most controllers send notes and make no sound of their own, so the sound has to come from an instrument in your software. Check that the controller is enabled as an input, that a track holds an instrument and that the track is armed.
How do I play MIDI on a MIDI controller?
You play it like any keyboard or pad set: the keys, pads and wheels send notes and controls to the instrument you’ve loaded, and the computer makes the sound. The same keys play a different sound when you change the instrument.
Can a MIDI controller make sound by itself?
Most can’t, but a keyboard with a built-in sound generator can, and Ableton says to check its Local Off function if you also route the keys through software.
How do I record with a MIDI controller?
Arm a MIDI track that holds an instrument, press the program’s record button and play. If you forgot to record, Live’s Capture MIDI button and FL Studio’s score log can recover the notes you just played.
What do the knobs on a MIDI controller do?
They send Control Change values from 0 to 127 to whatever parameter is mapped to them. Novation’s Launchkey Mini switches its eight encoders between Plugin, Mixer, Sends and Transport modes, and you can map your own in Live or FL Studio.
How do I use a MIDI controller with FL Studio?
Press F10, click the controller in the Input list and press Enable, and make sure “Enable MIDI remote control” is on in the Options menu. The MIDI activity light on the Main Panel blinks when a note arrives.
Can I use a MIDI controller with an iPad or iPhone?
Often, with the right adapter. Korg says its microKEY2 supports iPad and iPhone through Apple’s Lightning to USB camera adaptor, sold separately, and Arturia says its KeyStep 37 mk2 can be powered by a phone or a tablet.
Can two programs use one MIDI controller at once?
On Windows 11 25H2 and later, Microsoft says Windows MIDI Services lets several apps use the same MIDI device at the same time, and its own example is a controller app running while your DAW has a connection open. If a second program can’t see the controller on another setup, closing the first program and reopening the second is the simplest test.