DAW plays wrong notes? Inspect MIDI messages

You press one key on your MIDI keyboard, but the DAW plays a different note, several notes, or nothing at all. The problem could be the controller, a MIDI setting, or the track and instrument in your DAW.

Test the keyboard outside the DAW first. The MIDI Test shows input from a MIDI keyboard or controller, including keys, velocity, knobs, pedals, and messages. That gives you a way to check what the device sends before changing your project.

Inspect the MIDI messages

1. Open the MIDI Test in a browser that supports MIDI. The test does not work in Safari, so use another browser if it does not detect your keyboard.
2. Connect the MIDI keyboard or controller to your computer. If the browser asks to access a MIDI device, allow access and choose the connected device if prompted.
3. Play one key at a time, starting with a key you can identify easily. Watch the keys and message area, and note what appears when you press and release it.
4. Repeat with the key that sounds wrong in your DAW. Check whether the test shows a different key, more than one key, or a key that stays active after you release it.
5. Try a few keys in different parts of the keyboard. If your controller has octave, transpose, split, or zone controls, test with those settings unchanged for now.

For a clean test, close the DAW and other music programs first. Some MIDI setups do not let multiple apps share a device reliably. If the test detects nothing, reconnect the keyboard and try again before changing settings.

What the result means

The test shows the same keys you press

The controller is sending recognizable key input. If the DAW still plays a different pitch, look for a DAW setting that changes incoming notes, such as a transpose control, MIDI effect, scale tool, or track routing. The instrument may also be set to play a different sound or map notes to different actions.

The test shows a different key or an unexpected note value

The change is happening before the DAW plays the note. Check the keyboard's octave and transpose controls, and look for a split or zone that assigns different parts of the keyboard to different channels or note ranges. If the unexpected result follows the same physical key in the test, the controller or its configuration is the likely cause.

One key produces several notes or repeated messages

The controller may be sending more than one event, or another connected device may be sending input at the same time. Disconnect other MIDI controllers and virtual MIDI connections, then repeat the single-key test. If the extra messages remain, check the controller's layer, split, or internal routing settings.

The key appears on press but does not clear on release

A MIDI note normally has an event for starting the note and another for ending it. If the test keeps showing a key as active after you release it, the controller may not be sending the release event consistently. Test several keys and check whether the problem follows one key or the whole keyboard.

The test detects the keyboard, but the DAW receives nothing

The controller can send input, so check the DAW's selected MIDI input, track input, and monitoring or record-arm state. A track may be listening to a different device or MIDI channel than the one your keyboard uses.

How to fix the wrong notes

1. Check the track's MIDI input. In the DAW, select the connected keyboard as the track's input. If there are several similarly named inputs, test them one at a time. Make sure the track is set to receive input and that monitoring or record arming is enabled when required.
2. Look for note-changing effects. Temporarily bypass MIDI effects and tools that transpose, quantize, harmonize, arpeggiate, or map incoming notes. If the right pitch returns, enable those tools one by one to find which setting changes it.
3. Check the octave and transpose controls. Reset any octave shift or transpose setting on the keyboard, and compare the test with the DAW. Some keyboards also store these settings in presets, layers, or performance zones.
4. Match the MIDI channel. Set the track to receive the channel the keyboard sends, or use an all-channel input option if your DAW provides one. A channel mismatch can make a correctly detected keyboard seem silent or send input to the wrong track.
5. Remove duplicate inputs. Disconnect other controllers and disable virtual MIDI sources temporarily. If the DAW listens to the same keyboard through more than one route, a single press can trigger duplicate notes.
6. Confirm the computer sees the device. On Windows 11, open Settings › Bluetooth & devices › Devices to check whether the connected device appears. On macOS, open Applications › Utilities › Audio MIDI Setup and check whether the keyboard is listed. These screens confirm device visibility, but the browser test is better for checking the notes it sends.
7. Reconnect and retest. Try another USB port, connect directly instead of through a hub, and restart the DAW. Then test the keyboard in the browser again before reopening the project.

Why the octave label may differ

Different DAWs do not always use the same name for the same MIDI note number. For example, one program may label a note C3 while another labels the same pitch C4. That naming difference alone does not mean the keyboard is transposing notes.

Compare the actual pitch or note value, not just the octave label. If the browser test and DAW use different octave names but the note sounds at the same pitch, the keyboard may be working normally. If the pitch itself changes, look for transpose settings, MIDI processing, or an incorrect input route.

The MIDI Test checks messages received by the browser, so it can help separate controller output from DAW behavior, but it cannot diagnose every setting inside your music software.