FL Studio 
To connect a MIDI keyboard to FL Studio, plug it in before opening the app, then go to Options > MIDI settings or press F10. Select the keyboard in the Input list, click Enable, choose its supported Controller type, or a generic controller when no named profile exists, and play a key. The MIDI activity light should blink.
That blink is the dividing line. If the device is not listed, the computer has not handed it to FL Studio. If it is listed but the light stays dark, the input is disabled, the wrong port is selected or the controller is sending on an unexpected route. If the light blinks but there is no sound, MIDI already works; check the selected instrument and audio path instead.
Start with the exact MIDI symptom
A controller can light up and still send no usable MIDI. Before reinstalling anything, press a key and watch the Main Panel while an instrument channel is selected. Then match the result below.
| What you can prove | Where the signal stops | Next branch |
|---|---|---|
| Controller is absent from the Input list | Cable, power, driver or operating-system detection | Fix the connection before FL Studio |
| Device is listed, but no activity light appears | Disabled or wrong FL Studio MIDI input | Enable and test the correct Input |
| Activity light blinks, but there is no sound | Selected instrument or audio output | Leave the driver alone and check the sound path |
| Keys work, but pads, knobs or transport do not | Controller profile, script, DAW port or mapping | Use the device-specific control branch |
| Instrument plays, but notes are not recorded | Record filter, Pattern or selected channel | Fix the recording path |
This is also the cannibalization boundary for the site: this page owns both connection and no-input repair. Noticeable delay after notes already play belongs in the FL Studio audio settings guide, not in a second MIDI article.
Use the connection your keyboard actually provides
A USB controller normally connects directly to the computer and carries MIDI data over that cable. A keyboard with only round five-pin MIDI sockets needs a MIDI interface: connect the keyboard’s MIDI OUT to the interface’s MIDI IN. If you also want FL Studio to play the hardware keyboard, add the return direction from the interface’s MIDI OUT to the keyboard’s MIDI IN.
The current Image-Line MIDI Setup Wizard makes one distinction worth keeping visible: MIDI sends notes, knob movements and program changes, not audio. A hardware synth needs a separate audio connection to an audio interface if you want to hear or record its own sounds. A USB controller with no internal sound produces nothing by itself; it plays the instrument selected inside FL Studio.
For a first diagnosis, connect USB hardware to a direct computer port rather than a passive hub. This is a power and connection test, not a claim that every powered hub is bad. If the direct connection works, add the hub back later and prove it separately.
Let the operating system detect the controller before FL Studio
Install the manufacturer’s current driver only when that model requires one; many keyboards are class-compliant and use the operating system’s built-in MIDI driver. Connect the keyboard, turn it on and wait for Windows or macOS to finish recognizing it. Open FL Studio after that.
Image-Line’s setup sequence matters because the Input list is built from devices detected by the operating system. If you connected the keyboard after FL Studio opened, use Refresh device list. If it remains absent, close FL Studio, disconnect and reconnect the controller, wait for OS detection and reopen the app.
On macOS, open Applications > Utilities > Audio MIDI Setup and use Window > Show MIDI Studio to see whether the computer has a MIDI device to offer. On Windows, check Device Manager and the controller vendor’s current setup page. A lit screen proves power, not a valid driver session.
Connect the MIDI keyboard in four moves
Open Options > MIDI settings or press F10. In the lower Input area:
- Select the keyboard or the MIDI interface receiving its five-pin cable.
- Click Enable for that selected input.
- Choose the exact supported Controller type or script when the manufacturer documents one; otherwise use the available generic-controller option.
- Select an instrument in the Channel Rack, play a key and watch the MIDI activity light.
The current Image-Line MIDI Settings manual, checked September 4, 2026, uses this same Input → Enable → Controller type → activity sequence. Do not begin by enabling every entry in both Input and Output. A controller can expose several ports with different jobs, and a wrong DAW-control port can turn notes into commands.
Generic controller is not a failure
Image-Line says FL Studio supports generic USB/MIDI controllers. A keyboard missing from the named Controller type list can still play instruments and send standard notes or control-change messages. “Generic” means FL Studio does not have a preconfigured map for that device’s special behavior; it does not mean the keys are unsupported.
A named profile or MIDI Script adds the clever parts: transport buttons, jog wheels, pad colors, relative encoders, motorized faders or automatic focused-plugin mapping. The official preconfigured controller reference makes the same boundary: a device without preconfigured support may lose non-standard controls while ordinary MIDI input still works.
Start with notes. Once keys reliably play a selected instrument, install or update the documented script and select it under Controller type. If the profile requires a newer FL Studio build, use the official update path in the FL Studio installation guide. This order prevents a script problem from being mistaken for a dead USB connection.
Use the activity light and Debug log as proof
Play one key, one pad and one knob while watching the MIDI activity light. A blink means FL Studio received some controller data. For a more precise check, open the FL Studio Debug log and repeat the movement. Image-Line documents the log as a way to see received MIDI data and learn which controls are arriving.
Do not invent meaning the log does not contain. One received note proves the note path, not the transport buttons. A knob message proves that control reached FL Studio, not that it is linked to the target you expected. Test one physical control at a time and write down which category arrives.
- No light and no log event: stay with connection, Input and Enable.
- Light and note event, no sound: move to the instrument/audio branch.
- Notes arrive, controls do not: check profile, script, mode and DAW port.
- Controls arrive but move nothing: check the actual link or focused target.
If the MIDI controller is missing from Input
When nothing appears in the Input list, FL Studio has no device to enable. Work from the cable upward:
- Power the controller and use a known data-capable USB cable; some charging cables carry power only.
- Remove passive hubs and adapters for one direct-port test.
- Confirm the operating system lists the MIDI device.
- Install or remove a vendor driver only according to the current guide for that exact model.
- Close and reopen FL Studio after OS detection, then click Refresh device list.
A powered keyboard can be visible in Windows yet absent from FL Studio when the driver or device-enumeration layer is stuck. Use that as a symptom boundary, not as a universal instruction to uninstall a particular brand’s driver. The model and its current vendor documentation decide whether the correct fix is a class-compliant driver, firmware update or supported vendor package.
If FL Studio itself freezes or closes only when the controller is connected, stop treating it as ordinary no-input repair. Preserve the project and use the FL Studio crash recovery guide before changing drivers broadly.
If the device is listed but the activity light stays dark
Select the exact row under Input, not the similarly named device under Output, and confirm Enable is on. Also confirm Options > Enable MIDI remote control is selected. Click Refresh device list, then retest one key.
Controllers with several entries may expose a normal MIDI port, a DAW-control port and sometimes a legacy or virtual port. Begin with the port the vendor identifies for keys. Do not assign a random profile to every entry. If a controller has a hardware DAW/Preset switch, make sure it is in the mode specified by the current FL Studio setup guide for that device.
If the row remains unresponsive, close any standalone editor, synth or second DAW that may have opened the same MIDI port exclusively, then refresh. Change one condition and retest; closing six apps and reinstalling two drivers at once leaves no useful result.
If MIDI activity appears but the keyboard makes no sound
The controller connection is working. Add a stock instrument, select its Channel Rack button and play again. The current Image-Line note-recording workflow says the selected Instrument Channel receives the note data and responds to the controller.
If the activity light blinks but the selected instrument stays silent, check the plugin preset, channel mute and Master output. Confirm FL Studio itself can play an existing pattern. If all MIDI notes arrive but every sound path is silent, follow the audio driver and output checks in the Audio Settings guide instead of reinstalling the keyboard.
MIDI does not choose your headphones or speakers. That separation is why “my MIDI keyboard has no sound” can describe a fully working controller and a broken audio route at the same time.
If keys work but pads, knobs or transport do not
Working keys prove the basic note port. Special controls may depend on a named Controller type, an updated MIDI Script, the controller’s DAW mode, or a second input/output pair. Image-Line notes that specially supported controllers may need matching Input and Output port numbers, while different devices should not reuse a port in a way that creates conflicts.
There is no universal magic port number. Follow the current guide for your model. For example, Akai’s current MPK mini IV setup documents separate MIDI and DAW ports, matching Input/Output numbers within each pair, a controller script and a hardware DAW preset. That is a useful pattern, not an instruction for every keyboard.
For one ordinary knob, right-click the FL Studio control and choose Link to controller, then move the hardware knob. For deeper mapping, continue with the FL Studio automation guide. Remember that project-level links can override global links, and changing the MIDI channel used by a global link can make that mapping appear dead.
If the instrument plays but notes are not recorded
Monitoring and recording are separate results. Right-click the Record button and make sure Note is selected in the recording filter. Choose a Pattern, select the Instrument Channel you want to play, arm Record and press Play.
Image-Line’s current Note/MIDI Recording manual explains that Pattern mode records into the selected Pattern and its Piano roll, while Song mode can place the resulting Pattern Clip in the Playlist after recording stops. If you hear the instrument but see no notes, check the filter and selected Pattern before revisiting drivers.
If this is your first complete recording, continue with the FL Studio beginner project. This page stops once controller input is proven and the notes reach the correct Piano roll.
Fix velocity, sustain, pitch bend and mod controls separately
Do not group every expression problem under “MIDI not working.” Velocity is note data, sustain normally uses CC64, pitch bend uses its own message and a linked knob may send a control-change value through a script or custom mapping.
| Control | Proof to collect | FL Studio branch |
|---|---|---|
| Velocity | Different key strikes arrive with different values | Check Link note on velocity and adjust the velocity curve |
| Sustain pedal | CC64 changes when pedal is pressed/released | Check Foot pedal controls note off and plugin behavior |
| Pitch bend / mod wheel | Debug log shows the wheel message | Check plugin support, controller mode and mapping |
| Knob or fader | A control message arrives | Check Controller type, script or Link to controller |
Image-Line documents that Foot pedal controls note off captures CC64 inside FL Studio; a plugin that needs the sustain message for itself may require that option off. Test the pedal with one stock instrument before rewriting mappings for every plugin.
Keep multiple MIDI devices from colliding
Enable each controller separately and name its job in your notes: keys, pads, transport or external synth. FL Studio can use multiple controllers, but special profiles may rely on unique MIDI channels or port assignments. Avoid copying one controller’s port map onto another simply because it worked in a video.
For basic instrument playing, the selected Channel Rack instrument is the cleanest first test. For special feedback and transport, match Input and Output only where the supported profile asks for it. If adding a second controller breaks the first, disable the new entries, restore the known working map and introduce one port at a time.
Use this MIDI keyboard recovery order
- Identify whether the device is absent, silent, partly working or only failing to record.
- Connect with a known data cable and test one direct USB port or the correct five-pin MIDI path.
- Let Windows or macOS detect the controller before opening FL Studio.
- Open Options > MIDI settings, select the correct Input and click Enable.
- Choose the documented Controller type or a generic controller for basic note input.
- Select an instrument and use the activity light plus Debug log to prove received data.
- If the device is absent, refresh the list and follow only the current driver/firmware guide for that model.
- If notes work but controls do not, configure the supported script, mode and DAW port separately.
- If sound works but recording does not, enable the Note filter and select the target Pattern and instrument.
- Save the working port, mode and script choices before adding another controller or custom link.
Stop when the failed boundary starts working. A clean, written setup is worth more than a screenshot of ten enabled ports you cannot explain.
Frequently asked questions
How do I connect a MIDI keyboard to FL Studio?
Connect and power the keyboard before opening FL Studio. Open Options > MIDI settings, select it under Input, click Enable, choose the documented Controller type or a generic controller, select an instrument and play a key. The MIDI activity light should blink.
Why is my MIDI controller not showing in FL Studio?
The Input list contains devices already detected by the operating system. Test a data-capable cable and direct USB port, confirm Windows or macOS sees the controller, then reopen FL Studio or click Refresh device list. Install a vendor driver only when the exact model requires it.
Why does my MIDI keyboard light up but not work?
Power does not prove a valid MIDI connection. Select the exact device under Input, click Enable and watch the MIDI activity light while playing. If there is no activity, check the cable, OS detection, correct port and controller mode.
Why does FL Studio receive MIDI but make no sound?
If the activity light blinks, MIDI input works. Select an Instrument Channel and confirm FL Studio can play that instrument through the current audio device. Fix the instrument or audio path instead of reinstalling the controller.
Why do the keys work but transport buttons or knobs do not?
Keys can use generic note input while special controls require a named profile, MIDI Script, DAW mode or separate control port. Follow the current setup guide for that model and do not enable every port as a generic controller.
Why can I play notes but not record them?
Right-click Record and make sure Note is enabled in the recording filter. Select the target Pattern and Instrument Channel, arm Record and press Play. The notes should appear in the selected Pattern’s Piano roll.
Should MIDI Input and Output use the same port number?
Only when the supported controller profile or vendor guide requires a matched pair for feedback or DAW control. The number itself is not magic. Keep different device roles and required port pairs distinct to avoid conflicts.
Does a MIDI keyboard carry audio into FL Studio?
No. MIDI carries note and control data. To record the sound of an external synthesizer, connect its audio outputs to an audio interface as well as making the required MIDI connections.
