DAW receives control changes as notes? How to check

You turn a knob or move a fader, but your DAW records notes instead of control changes. Or the controller seems to trigger a sound when you meant to adjust a parameter. The cause could be the controller's mode, the DAW's input setup, or the way the track displays MIDI data.

First, check what the controller actually sends. The MIDI Test shows incoming messages from keys, knobs, pedals, and other MIDI controls, so you can separate a controller problem from a DAW setting.

Check what your controller sends

1. Close your DAW temporarily, then open the MIDI Test. It works in browsers other than Safari.
2. Allow the browser to access MIDI devices when it asks. Select your controller if the test shows a device list.
3. Turn one knob or move one fader a little, then inspect the messages. Do not press keys or pads during this check.
4. Press one key or pad, then move the same knob again. Compare the messages for each action. A knob assigned to a control change should send a Control Change message. A key or pad usually sends Note On and Note Off messages.

Testing one control at a time matters. If you press a key while turning a knob, both messages may arrive together and make the result harder to interpret. The MIDI Test checks messages reaching the browser. It does not inspect your DAW's routing, track filters, or MIDI effects.

What the result means

The knob sends Control Change messages

The controller is sending control data, often shortened to CC. If your DAW records notes instead, the conversion or misrouting is happening after the controller sends its message. Check the DAW's selected MIDI input, control-surface setup, and any input processing on the track.

The knob sends Note On and Note Off messages

The controller is sending note events for that knob. This is not a DAW misreading the message. The control may be in a different mode, or its assignment may have been changed in the controller's editor or configuration software. Look for a mode that assigns knobs and faders to CC messages.

The test shows CC, but the DAW's piano roll shows notes

Check where you are looking. A piano roll is designed to show note events, while control changes are usually shown in a separate controller lane, automation view, or event list. If the DAW's event list identifies the events as notes, check for a MIDI effect, input transformer, or mapping that converts incoming messages.

The test shows no messages

The browser is not receiving input from the device. Confirm that you granted MIDI permission and selected the right device. If the controller is connected but still silent, test its connection and mode before changing DAW settings.

How to fix it

1. Check the controller's mode. Switch between its common modes, such as DAW, MIDI, or user mode, if it has them. Consult the controller's own display or manual for the mode that sends knobs and faders as CC messages. Use the MIDI Test again to confirm the change.
2. Choose the controller as the track input. In your DAW's MIDI preferences, confirm that the physical controller or its correct MIDI port is enabled. Then check the track's input source. DAWs often list a control-surface port separately from a port for playing notes, so selecting the wrong one can produce confusing results.
3. Check the track's MIDI view and filters. Look for a controller lane or event list instead of relying only on the piano roll. If the incoming event is identified as a note, temporarily bypass MIDI effects, input filters, and transformations on the track. Re-enable them one at a time to find which one changes the data.
4. Review MIDI learn and control-surface mappings. If the DAW learned the control from a key or pad, remove that assignment and learn it again while moving only the intended knob or fader. Control-surface settings and track recording settings may use separate inputs, so check both.
5. Reconnect the device. Unplug a USB controller and connect it directly to another port. For a Bluetooth controller, check the connection in Windows 11 at Settings › Bluetooth & devices › Devices, or on a Mac at System Settings › Bluetooth. Close and reopen the DAW after reconnecting so it refreshes its MIDI device list.
6. Restart the DAW, then the computer. Reopening the program can clear a stale MIDI connection. Restart the computer only if the controller remains unavailable in both the DAW and the browser test.

DAW menus differ, so use the program's Preferences or Settings area and look for MIDI, controller, or track input options. The same MIDI message types apply on Windows 11 and macOS, but the names and locations of those controls depend on the DAW.

Why a control change can look like a note

MIDI carries different kinds of messages. A note message identifies a key or pad, along with details such as its pitch and how hard it was struck. A control change carries a controller number and a value, often used for a knob, fader, or pedal. The DAW may display these in different areas, even when they were recorded in the same MIDI region.

A controller can also be configured to send notes from a knob or pad. That can be useful for triggering sounds, but it is not the same as sending CC data. If the MIDI Test reports notes, change the controller's assignment. If it reports CC and the DAW reports notes, look for a DAW input transform or confirm that you are viewing the right kind of MIDI event.