How to Use a MIDI Controller in Logic Pro

Checked against Apple's Logic Pro for Mac 12.3.1 release notes and current documentation on August 28, 2026.

To use a MIDI controller in Logic Pro, connect it before opening Logic, create a software instrument track, choose a patch, and play a few notes. Once the keys work, map knobs and faders with Auto Assign, Smart Controls, or Controller Assignments. Use Key Commands for transport buttons. Treat note input and control mapping as two separate tests.

Quick setup: get notes playing first

1. Connect a USB MIDI controller directly to the Mac or through a powered hub that you know works. For a keyboard with only standard 5-pin MIDI ports, connect it through a MIDI interface.
2. If the manufacturer supplies a current macOS driver or setup utility for your model, install that version before troubleshooting in Logic.
3. Open Logic Pro and create a new software instrument track.
4. Choose a stock patch from the Library so the sound source is known.
5. Select the track and play the keys or pads. Watch the MIDI Activity display in the control bar while you play.

Apple's current software instrument setup guide separates the common connection routes: USB can connect directly, while a standard MIDI connection needs an interface. Apple also tells users to check the device maker's instructions for any required driver. That qualification matters. Some controllers work without extra software. Others need a driver, firmware update, or vendor integration package for their deeper controls.

If Logic shows MIDI activity but you hear nothing, the controller is probably reaching the app. Check that the selected track is a software instrument track, a patch is loaded, the track isn't muted, and the audio output is working. A MIDI controller sends performance data. It doesn't produce the sound of a Logic software instrument.

MIDI note input and control mapping are separate jobs

Keys and pads normally send note messages. Knobs, faders, encoders, and buttons often send control-change messages or device-specific data. Logic can receive the notes even when it has no useful assignment for the other controls. This is why “the keyboard plays, but the knobs do nothing” isn't a connection failure.

Do not map everything in one sitting. Start with a control you can identify on sight, such as the first fader or top-left knob. A one-control test exposes the active MIDI port, message, target, and persistence behavior without leaving a page of mystery assignments behind.

Choose the right mapping method

Auto Assign is the shortest route when Logic recognizes a supported USB controller. Smart Controls are useful when one physical knob should follow the selected patch's main performance control. Controller Assignments are better when you need a fixed relationship with an exact mixer or plug-in parameter. Key Commands suit buttons that should trigger a Logic command.

These methods can overlap. That doesn't mean they should. If a vendor script already maps the transport and faders, add only the missing controls. Duplicate assignments are hard to diagnose because one movement can reach more than one target.

Use Auto Assign for a supported controller

The first time Logic sees a supported USB controller, it can ask whether you want to use the device as a control surface. Choose Auto Assign when you want Logic's supported mapping for buttons, knobs, faders, and Smart Controls. Choose No when you only need MIDI input or when you plan to use a specific manufacturer setup.

Apple limits this feature to supported USB MIDI controllers. If the prompt never appears, that alone doesn't prove the device is broken. The keys can still send MIDI notes, and the remaining controls can still be assigned manually.

To review the choice later, open Logic Pro > Settings > Control Surfaces > MIDI Controllers. The current pane lists supported devices that use Logic's controller scripts and gives you access to Auto, Controller Assignments, and Setup.

Map a knob or fader with Smart Controls

This route is good for a controller knob that should follow a useful control on the selected track — filter cutoff on one patch, drive on another.

1. Select the software instrument track and press B to open Smart Controls.
2. Click the Inspector button in the Smart Controls menu bar.
3. Select the on-screen knob, switch, or other screen control you want to operate.
4. Click External Assignment in the inspector.
5. Click Learn, then move the physical knob or fader through part of its range.
6. Click Learn again to stop listening for a new message.
7. Move the hardware control slowly and confirm that only the intended screen control responds.

Apple notes that a Smart Controls hardware assignment is retained across Logic projects until you reassign it. That makes it convenient, but it also means a casual experiment can affect tomorrow's project. If a knob already has a dependable job, do not reuse it without checking the existing assignment.

External Assignment versus Parameter Mapping

Smart Controls have two layers. External Assignment connects your physical control to a screen control. Parameter Mapping connects that screen control to an instrument, effect, or channel-strip parameter. Apple documents that parameter mappings are saved with the patch. If the hardware moves the screen control but the sound doesn't change in a useful way, inspect Parameter Mapping rather than relearning the same hardware knob.

Make a fixed Controller Assignment in Easy View

Use Easy View when you want a direct assignment to an exact mixer or plug-in parameter.

1. Open the Mixer or the plug-in window and select the parameter you want to control.
2. Choose Logic Pro > Control Surfaces > Learn Assignment for [parameter name]. The default Command-L key command opens the learning route as well, but custom key-command sets can differ.
3. Move the hardware knob, fader, or button once. The incoming MIDI message should appear in the Input message field.
4. Click Learn Mode to finish. Do not leave it active while you touch other controls.
5. Close the window, move the control again, and confirm the target and direction.

Apple's current Easy View instructions warn that Learn Mode remains active until you end it. That's the small step most likely to create accidental mappings: you learn one fader, reach for another control, and Logic treats that movement as a new assignment.

Assign transport buttons through Key Commands

For an unsupported controller, Play, Stop, Record, Cycle, marker navigation, and other command-style actions can be learned in the Key Commands window.

1. Open Logic Pro > Key Commands > Edit.
2. Search for the command you want, such as Play or Record.
3. Click Learn New Assignment.
4. Select the command in the Command column.
5. Press the controller button once and wait for Logic to receive the complete MIDI message.
6. Test the button while the Key Commands window is closed.

Apple's controller-assignment procedure for key commands also provides a Delete Assignment control. Use it when the learned button triggers the wrong command. Do not stack a second assignment over a bad first attempt.

Keep assignments predictable across tracks and projects

• Write down the physical control and its job. “Fader 1 = selected channel volume” is useful. “Faders mapped” is not.
• Keep manufacturer mappings intact. If a device-specific installer asks to replace a control-surface preference file, back up the existing file and learned assignments first. Follow the current guide for that exact model.
• Test a new empty project. This tells you whether an assignment is global, part of a patch, or tied to the current project state.
• Check focus and selection. Some mappings follow the selected track or active plug-in; a fixed assignment can point to a specific channel strip.
• Avoid two routes for the same control. Auto Assign, vendor integration, Smart Controls, and manual Controller Assignments can all compete.

If you want a knob movement recorded over time, mapping is only the setup. The next job is writing or recording that movement as Logic Pro automation.

Fix the common MIDI controller setup failures

Logic shows no MIDI activity

Reconnect the controller before launching Logic, try a known data-capable cable and another port, and check Audio MIDI Setup in macOS. Confirm that the device is powered and that any required current driver or firmware is installed. Do not start by deleting Logic settings.

Notes work, but knobs or faders do not

The connection is carrying MIDI notes. Check whether the controller has a Logic-specific mode, whether Auto Assign is available, and whether the control sends a message in Controller Assignments. Then learn one control with the method that matches its job.

One control moves the wrong parameter

Open Controller Assignments or Smart Controls and remove the incorrect assignment before learning a replacement. Also check for an active vendor map. One control reaching two mapping systems can appear to jump or affect two targets.

The controller is detected, but there is no sound

Select a software instrument track and load a known patch. MIDI activity without audio points away from the cable and toward track selection, the sound source, mute state, or audio output. The full Logic Pro MIDI keyboard troubleshooting guide follows the failure from input to output without mixing it into this mapping tutorial.

Logic behaves strangely after mapping

End Learn Mode and temporarily choose Logic Pro > Control Surfaces > Bypass All Control Surfaces as an isolation test. If the problem stops, inspect control-surface assignments and duplicate device entries. Turn control surfaces back on after the test. This is a reversible check, not a fix by itself.

Frequently asked questions

Does any MIDI controller work with Logic Pro?

Many controllers can send standard MIDI notes to Logic, but automatic mapping and deeper integration depend on the model, its operating mode, current drivers, and Logic's supported-device scripts. Check the current manufacturer and Apple documentation for the exact controller.

Why does my MIDI keyboard play notes but the knobs do nothing?

Note input and control mapping are separate. The keys can reach a software instrument while the knobs have no assigned Logic target. Use Auto Assign for a supported controller, Smart Controls for a patch-facing control, or Controller Assignments for an exact parameter.

How do I map a MIDI knob in Logic Pro?

Select the target parameter and choose Logic Pro > Control Surfaces > Learn Assignment for that parameter, move the physical knob, then end Learn Mode. For a Smart Control, use its inspector's External Assignment > Learn route.

How do I map Play and Record buttons?

Open Logic Pro > Key Commands > Edit, choose Learn New Assignment, select the Play or Record command, and press the controller button once. Test it after closing the window and delete the assignment if it triggers the wrong command.

Are MIDI controller assignments saved with the Logic project?

Do not assume every mapping has the same scope. Smart Controls hardware assignments can persist across projects, while screen-control parameter mappings are saved with a patch. Test the assignment in a new empty project and document the behavior you need.

How do I record what I play on the controller?

Once note input works, record-enable or select the software instrument track, set the count-in and metronome as needed, and record a MIDI region. Continue with the Logic Pro MIDI recording guide for takes, overdubs, quantization, and editing.

Map one control, then make music

A useful controller setup is small enough to remember. Get the notes playing, give one physical control one clear job, reopen the project, and verify it. Add the next assignment only when the first one behaves predictably. The Create Music in Logic Pro hub connects the controller to recording, beat making, synthesis, sampling, and arrangement.