Drum pad controller not sending CC values?

You turn a knob or hit a pad, but your music software shows no CC values. The cause could be the controller's assignment, the wrong MIDI input, or a filter in the software. First check what messages the controller actually sends.

The MIDI Test displays incoming messages from a keyboard or controller in your browser. It can help you tell whether a control sends a control change, a note, or no message at all.

Test the drum pad controller

1. Open the MIDI Test in a browser that supports it. MIDI Test does not work in Safari. If the browser asks to access MIDI devices, allow access.
2. Select your drum pad controller as the MIDI input if it appears in the device list. If you do not see it, reconnect it and reload the page.
3. Move the knob, slider, or other control that should send CC data. Watch the incoming messages while you move it slowly from one end of its range to the other.
4. Test a pad separately. Press it once, release it, and check whether the message is a note or a control change. Try any other control you expect to send CC messages.
5. Write down the message type, channel, CC number, and values that appear. Test one control at a time so you can tell which control produced each message.

CC means control change. A CC message has a controller number and a value, usually from 0 to 127. A drum pad commonly sends note messages instead. That can be normal even if the sound software uses the pad to control an effect.

What the result means

You see CC messages and the value changes

The controller is sending CC data, so the next place to check is the receiving app. Confirm it is listening to the same MIDI input and channel, and that the control is mapped to the CC number shown in the test. A MIDI channel is one of 16 numbered routes that an app can use to separate messages.

You see note messages when you hit a pad

The pad is sending notes, not CC. That is typical for drum pads, which often trigger a different note for each pad. If you need a pad to control an effect, check whether its configuration lets you assign a CC message instead. If the notes arrive but are assigned to the wrong sounds, see MIDI pad controller sending the wrong notes?

The value appears only at the start or end of a movement

The control may be set to toggle between two values, or it may send data only when it crosses a threshold. A rotary control may also be configured for relative changes instead of a full 0 to 127 range. Check its assignment before treating a limited range as a fault.

No messages appear

The browser may be listening to a different device, the controller may not be connected as a MIDI device, or that control may not be assigned to send MIDI. Try the fixes below. A browser test can show messages that reach the browser, but it cannot inspect the controller's internal settings.

How to fix missing CC values

1. Check the control's assignment. Open the controller's configuration software or consult its manual. Confirm that the specific knob, slider, or pad is assigned to send a CC message, and note the CC number and channel. Pads may be set to send notes by default.
2. Choose the correct MIDI input. If the test lists several devices, select the controller itself rather than a virtual port or another keyboard. Disconnect other MIDI devices temporarily if you are unsure which one is sending the messages.
3. Check that the computer recognizes the controller. In Windows 11, right-click Start and open Device Manager. A controller may appear under Sound, video and game controllers or another device category. On macOS, open Audio MIDI Setup, then choose Window › Show MIDI Studio. Device names and categories can vary by model.
4. Try a different USB connection. Connect the controller directly to another USB port, rather than through a hub or dock. Use a cable that carries data, not a charge-only cable. If it is bus-powered, disconnect it briefly and reconnect it.
5. Check channel and CC filters in your app. The receiving app may ignore messages on other channels, or accept notes while filtering control changes. Match the app's input, channel, and CC mapping to what MIDI Test displays.
6. Restart the browser and controller. Close music software and controller editors, reconnect the controller, then reopen the test. Try a supported browser such as Chrome or Edge if the MIDI input is still unavailable.

There is no single Windows 11 or macOS setting that assigns CC numbers to every drum pad. The controller's configuration and the receiving app's MIDI settings determine what the control sends and how the app uses it.

Why a drum pad may not send CC data

A pad's pressure response is not automatically a CC message. Depending on the controller, pressure may be sent as aftertouch, used only to change note velocity, or not sent at all. These are different MIDI message types. Check the exact message shown in the test, and look for an explicit assignment for CC output in the controller's configuration.

If the controller appears in the test but a particular control never produces a message after its assignment is checked, test that control in the manufacturer's configuration software or on another computer. If it remains unresponsive, contact the manufacturer or ask about a repair or replacement. The test runs in your browser, and nothing you record is uploaded.