Workflow

What DAW control features actually need to do

A controller with many knobs and pads can still be awkward if the controls do not map to the actions you use. Assess the mapping route, the software version and the task—not just the feature count.

Decide which actions you want under your hands

List the concrete tasks that would benefit from hardware: starting and stopping transport, changing tracks, adjusting levels, selecting a software instrument, triggering clips or entering drum notes. A fader is useful for level changes only if the DAW script or assignment sends it to the intended channel. A pad is a trigger surface, not an included drum instrument.

Separate built-in integration from custom mapping

A manufacturer may provide scripts for named DAWs, support common control protocols or allow user presets. Check which modes are actually listed for the exact product and what its current resources page offers. “Compatible” can mean anything from basic MIDI-note input to more detailed transport or instrument control; it is not proof of one-click setup in every version.

Check the right kind of sensitivity

Velocity sensing on keys can describe how strongly a note is sent when a key is pressed. Pressure sensing on pads refers to a pad gesture. Keyboard aftertouch is a different capability and should not be inferred from pressure-sensitive pads. If a particular expression method matters, look for that exact field in the manual or feature list.

Use a small mapping test plan

  1. Confirm operating-system and DAW support for the exact controller model.
  2. Find the current manufacturer script or setup instructions.
  3. Choose one task for each control group and see whether the mapping exposes it.
  4. Check whether user assignments survive preset or project changes.
  5. Verify that a DAW update has not changed the script or protocol behavior.

These are pre-purchase checks, not claims that an untested mapping works. If software integration is the main reason to choose a model, reserve time to test the exact software and controller together within a return window.

Alesis's VI25, VI49 and VI61 each have 16 pads described as velocity-sensitive, but their exact pages and manuals do not establish pressure-sensitive pad response. The Vortex Wireless 2 and Vmini also describe velocity-sensitive pads without establishing pressure sensing. Vortex key aftertouch and an assignable Vmini knob's channel-aftertouch message are separate controls, not evidence of pad pressure. None of these Alesis models is counted as a pressure-pad match on the available evidence. Check the same pressure-required answer.

The four KORG non-Air microKEY2-25, -37, -49 and -61 layouts specify joystick or wheels and octave controls, not pressure-sensitive pad banks. KORG documents eight velocity-sensitive trigger pads on the nanoKEY Studio, but does not establish their pressure response; Black nanoKEY2 documents keyboard keys and buttons, not a pad bank. Neither is counted as a confirmed pressure-pad match. Key and pad velocity are different from pad-pressure sensing. See the complete pressure-pad result set.

When pad pressure, not just velocity, is required

The Roland A-49 has no documented separate pad bank. The A-88MKII has eight assignable illuminated pads, but Roland's product page and manual do not specify continuous pressure response. Neither is counted as a confirmed pressure-pad match; the A-88MKII's key action and pad controls are distinct. See the same pressure-sensitive-pad-required result set.

The three Alesis Q reviews also do not establish pressure-sensitive pads: Q Mini and Q49 MKII have no separate pad bank documented, while Q88 MKII documents wheels, a slider and pedal inputs rather than pads. Keys' velocity response is not pad pressure. Use the same pad-pressure-required finder answer.

For an earlier-enabled choice, the discontinued A-300PRO, A-500PRO and A-800PRO have eight Dynamic Pads each; the shared A-PRO manual's PAD AFTERTOUCH CURVE setting specifically maps pressure on pads A1–A8 to aftertouch data. That is separate from channel aftertouch on the 32-, 49- or 61-key beds and does not establish polyphonic pad aftertouch. The similarly named A-500S is not an A-PRO: its manual and product page document no pad bank or key aftertouch. The same pressure-pad requirement with earlier models enabled preserves the user's conditions; the reviews distinguish the control surfaces and setup limits.

At a 56.5-inch cap with at least 88 keys, USB-C and DIN MIDI, the source-backed set includes five configurations when pad pressure is left open. Requiring pressure-sensitive pads reduces it to three: the A-88MKII leaves because response on its eight pads is undocumented; key aftertouch is not a substitute. Compare the open-pad result with the same brief with pads required. The latter includes the documented pressure-sensitive Arturia KeyLab 88 mk3, KeyLab Essential 88 and Novation Launchkey 88 MK4.

The Alesis Q88 MKII documents 88 keys and DIN but cannot enter either of these complete setups: the product page/manual do not confirm USB-C or chassis width, and no pad bank is specified. Its direct DIN output alone does not satisfy the width/host/pad combination. Check the same five required answers.

Native Instruments' S49/S61/S88 MK3 specify polyphonic aftertouch on keys, not a drum-pad bank; the A25/A49/A61 control panels also have no documented pad bank. M32 and the M-Audio keyboards likewise do not establish a separate pressure-sensitive pad layout; Hammer 88 Pro's key channel aftertouch is not pad pressure. The pressure-sensitive-pad finder result keeps the same required-pad answer and does not count a keyboard-aftertouch feature as pad response.

KORG's Keystage-49 and Keystage-61 are another explicit nonmatch for this requirement: KORG specifies polyphonic aftertouch on the keyboard keys but no separate pad bank, and the exact product specifications list zero pads. Key pressure messages are not evidence of pressure-sensitive drum/control pads.

Twenty-three reviewed models document source-backed pressure-sensitive pads: MPK Mini IV, MPK Mini Plus II, Mini MK3 and Mini Play MK3, both MiniLabs, all five standard Launchkey MK4 sizes, both Mini MK4 models, all four current FLkeys and all six KeyLabs. The exact Mini MK3 and Play MK3 pages specify eight pressure-sensitive pads; Play alone adds a sound bank, speaker and headphone output. The original MPK Mini Plus page documents eight velocity-sensitive pads but does not establish their pressure response, so it is not counted in this result. The Mini IV has eight velocity- and pressure-sensitive pads across two banks; the Plus II specification and FAQ list eight physical pads, with pressure and velocity response. A separate Plus II CV support discussion says “16 drum pads” in a routing context, which does not establish sixteen physical pads or change the product-page count. None of these pad facts establishes pressure response on the keyboard keys or polyphonic pad aftertouch. Each standard Launchkey and all four current FLkeys specify sixteen velocity-sensitive pads with polyphonic aftertouch; this is pressure control on the pads, not evidence of aftertouch on the keyboard keys. FLkey Mini 25 has 25 mini keys and TRS Type-A MIDI; FLkey 37 has 37 full-size synth-action keys and direct five-pin DIN; FLkey 49 and 61 use semi-weighted 49- and 61-key beds with direct DIN. All use USB-C for the documented computer route. Launchkey 61 uses 61 semi-weighted waterfall keys and a 35.24-inch body; Launchkey 88 uses a custom-designed semi-weighted keybed and a 50.16-inch body. The non-Essential KeyLab 88 mk3 has twelve pads in four banks; Essential 88 has eight. MicroLab shows keys, strips and buttons but no separate pad bank, and all four KeyStep configurations are nonmatches. The KeySteps' key aftertouch is not a substitute for pressure-sensitive drum/control pads. Pad messages also do not include a drum instrument; the chosen software must interpret them. M-Audio lists eight velocity-sensitive pads on the Oxygen Pro Mini and the distinct Oxygen 25 (MKV), Oxygen 49 (MKV) and Oxygen 61 (MKV), but their inspected product pages and manuals do not establish pad-pressure response, so they are not counted when pressure-sensitive pads are required.

Keep three terms distinct when reading specifications: velocity is the response to the initial strike; pad pressure describes continued pressure on a pad; keyboard aftertouch is a separate expression feature on the keys. The two non-Essential KeyLab mk3 models document channel aftertouch on their keys, and all four KeySteps document keyboard aftertouch, but that does not make the KeySteps pressure-pad matches. The reviewed MiniLab pages do not confirm key aftertouch. Follow the exact model review and manual rather than treating controls as interchangeable.

Twenty-three reviewed models have source-backed pressure-sensitive pads. The Oxygen Pro 25/49/61 and Oxygen 25/49/61 (MKV) product pages list velocity-sensitive pads, but no inspected source establishes pad-pressure response for either range, so they remain outside this match set. The Pro shared manual also documents channel aftertouch on its keys; that is a different control. Read the Oxygen 25 (MKV), Oxygen 49 (MKV) and Oxygen 61 (MKV) assessments separately from the Oxygen Pro siblings.

Find every assessed controller with pressure-sensitive pads.

Twenty-three reviewed models have source-backed pressure-sensitive pads. The three standard Oxygen Pro pages describe velocity-sensitive pads, while the shared manual documents aftertouch on the keys; the inspected materials do not establish pad-pressure response, so they remain outside this match set.

For Akai pad examples, compare the 25-key USB-B MPK Mini MK3, the sound-producing 25-key Mini Play MK3 and the Mini IV; the original MPK Mini Plus is left out because its exact sources do not document pad pressure. Pad pressure does not establish keyboard aftertouch.

KeyStep mk2 review: why key aftertouch does not meet this pad requirement · KeyStep 37 mk2 review: its four encoders do not add pressure pads.

KeyStep Pro review: step keys and aftertouch are not pressure pads · KeyStep Pro Chroma review: LED color customization does not add a pad bank.

Turn the question into a practical shortlist

Build my shortlist →