Use a MIDI Keyboard in Logic Pro: First Track to Clean Part
Connect the keyboard, load one instrument, record a part, and edit timing and velocity without killing the performance.
A MIDI keyboard does not record audio into Logic Pro. It records performance data: notes, timing, velocity, and controller movement. The sound comes from the software instrument on the selected track.
Once that distinction is clear, most MIDI setup problems become simple. Either Logic is not receiving the keyboard, the wrong track type is selected, or the instrument is not loaded.
Quick answer
If you are in Logic Pro right now, do not start by opening every menu. Connect the controller before opening the project. Create a software instrument track, not an audio track. Then move through the four checks below in order.
The order matters because midi work usually breaks earlier than it looks. A wrong track, region, input, bus, or range can make the last setting look guilty when it is only receiving a bad setup.
Use this as the short version before reading the full guide.
- Confirm MIDI activity first: Press a key and check that Logic sees input.
- Choose one focused instrument: Use a basic piano, electric piano, bass, or synth patch for the first pass.
- Record the part without stopping every bar: Let a full pass happen.
- Edit note length, timing, and velocity: Fix wrong notes first.
Before you start
- Connect the controller before opening the project.
- Create a software instrument track, not an audio track.
- Load a simple sound before browsing presets.
- Record a short loop before editing anything.
A clean pass from start to finish
Run this as one clean pass, not as disconnected tricks. Begin with the first checkpoint: confirm MIDI activity first. Then move to the second: choose one focused instrument. Those two checks make the project readable before you make detailed changes.
After that, use the next two checkpoints as the decision stage: record the part without stopping every bar, then edit note length, timing, and velocity. This is where you stop guessing and let the screen show whether the sound, timing, routing, or edit is behaving the way the song needs.
If you change more than one thing at once, write down what you changed or save a new version. Logic Pro is fast enough that a session can go from fixed to confusing in under a minute. Small, named moves are easier to trust later.
1. Confirm MIDI activity first
Press a key and check that Logic sees input. If nothing responds, swap the cable, check controller power, or reconnect before blaming the instrument.
Do this before opening plugin windows. No MIDI input means no instrument will behave.
2. Choose one focused instrument
Use a basic piano, electric piano, bass, or synth patch for the first pass. Huge layered presets can hide timing and velocity problems.
The goal is to record a musical part, not win the preset browser.
3. Record the part without stopping every bar
Let a full pass happen. Small mistakes are easier to repair in the Piano Roll than a performance broken by constant stopping.
Use the metronome if it helps, but turn it down if it makes you play stiff.
4. Edit note length, timing, and velocity
Fix wrong notes first. Then correct timing only where the groove needs help. Finish with velocity, because dynamics are what make MIDI feel played rather than typed.
A perfectly quantized part with flat velocity usually sounds worse than a slightly loose performance with good dynamics.
Decision table
| Problem | Where to look | Fix |
|---|---|---|
| No sound | Track type and instrument slot | Use a software instrument track |
| Wrong notes | Piano Roll | Move or delete selected notes |
| Stiff feel | Quantize and velocity | Reduce quantize strength and vary velocity |
| Late part | Region or selected notes | Move only the notes that feel late |
Checkpoint table
| Checkpoint | What should be true | If it is not true |
|---|---|---|
| Confirm MIDI activity first | Do this before opening plugin windows. | Back up and fix the setup before continuing. |
| Choose one focused instrument | The goal is to record a musical part, not win the preset browser. | Do the smaller edit instead of rebuilding the whole part. |
| Record the part without stopping every bar | Use the metronome if it helps, but turn it down if it makes you play stiff. | Check what is selected, then repeat the change deliberately. |
| Edit note length, timing, and velocity | A perfectly quantized part with flat velocity usually sounds worse than a slightly loose performance with good dynamics. | Use the mixer or playback context as the final judge. |
Before and after check
Before the change, make one short playback pass and name the exact problem in plain words: late entrance, dull vocal, wrong input, harsh consonant, missing output, messy routing, clipped bounce, or whatever the session is actually doing. If you cannot name it, you are not ready to fix it yet.
After the change, play the same section at the same volume. Louder almost always sounds better for ten seconds, so level-match when you are judging midi decisions. The useful question is not whether the edit is impressive. It is whether the part sits better without pulling attention away from the song.
Check the edges of the fix. In Logic Pro, a repair can solve the center of a problem while damaging the bar before it, the breath after it, the bus return, or the export tail. A good before/after pass includes a little lead-in and a little space after the moment you changed.
If the after version only feels better while you are watching the screen, take a break and listen again without touching the mouse. Visual neatness is helpful for editing, but the final test is still playback. Keep the version that makes the project easier to finish.
What not to chase yet
Do not chase polish before the basic workflow is stable. For this topic, the first two checkpoints have to make sense before you worry about the smaller details: confirm MIDI activity first, then choose one focused instrument. Fancy settings cannot rescue a confused source.
Do not copy numbers blindly from another session. Buffer sizes, EQ points, quantize strength, compression timing, send levels, and bounce choices all depend on the material. Use examples as starting points, then move the control until this project sounds and behaves correctly.
Do not keep editing because the tool is available. Logic Pro gives you enough control to over-fix almost anything. Stop when the problem is gone and the performance still feels like a performance.
What good looks like
The midi workflow is working when you can explain what changed without pointing at a random plugin window. If the fix depends on luck, the session is not stable yet.
After the main pass, close the editor you were using and play the section from a few bars before the change. A good edit survives context. A bad edit only sounds correct when the screen is zoomed into the problem.
Keep one version before the major change and one version after it. Logic Pro projects can move quickly, and a clean fallback saves more time than trying to reverse a dozen tiny edits later.
If it still feels wrong
If the result still feels wrong, return to the signal chain. Ask whether the source is clean, whether the region edit is correct, whether the track is routed where you think it is, and whether the mixer confirms what your ears are telling you.
Do not add another processor just because the current one did not solve the issue. In Logic Pro, many problems are earlier than the plugin slot: wrong input, messy region boundaries, doubled monitoring, over-quantized MIDI, or a bus that is louder than the dry track.
When you get stuck, simplify the project. Mute everything except the source and the one track or aux it depends on. If the problem disappears, bring the session back one group at a time until the conflict shows itself.
Common mistakes to avoid
- Recording MIDI on an audio track. Fix it by returning to the first visible control in the chain and confirming it before you touch a plugin.
- Quantizing to the smallest grid available. Fix it by listening to the section in context, then changing only the thing that fails the playback test.
- Ignoring velocity after timing edits. Fix it by saving a version, making the edit smaller, and checking whether the song still feels natural.
- Browsing sounds so long that the part never gets written. Fix it by simplifying the session view until the routing, region, or setting is obvious again.
Practice pass
Record an eight-bar chord part. Make only three timing edits and five velocity edits. The limit forces you to fix what matters instead of sterilizing the performance.
When to move on
You are done when the change helps the song at normal listening volume. Not when the screen looks tidy, not when every meter behaves perfectly, and not when the analyzer is pretty.
Print or bounce a short reference after the fix. Listening outside the edit screen catches problems that are invisible while you are staring at regions, lanes, and meters.
Sources checked
This draft was checked against current Apple Logic Pro documentation and release notes before writing. Source links used for version-sensitive claims on May 16, 2026:
FAQ
Why does my MIDI keyboard make no sound in Logic Pro?
Most often the track type is wrong, no software instrument is loaded, the track is not selected or record-enabled, or Logic is not receiving MIDI input.
Can I edit MIDI after recording?
Yes. MIDI is editable after the take: pitch, timing, length, velocity, and controller data can all be changed.
What is velocity in Logic Pro?
Velocity is how hard a MIDI note was played, usually 0 to 127. It often controls loudness and tone.
Should I use Smart Quantize?
Use Smart Quantize when you want timing help without destroying the relative feel of notes and controller events.
