A MIDI controller is a hardware device used to generate and transmit MIDI performance or control data to another device or application. Pressing a key can send Note On, note number, and velocity data. Moving a wheel can send pitch bend or modulation wheel data. Pads, knobs, faders, pedals, buttons, and touch surfaces can send notes, Control Change messages, pressure, program changes, transport-related commands, or device-specific data.
A dedicated MIDI controller normally does not generate the final audio sound itself. It controls something that does: a software instrument, DAW, hardware synthesizer, sampler, drum machine, sound module, lighting system, or another MIDI-capable device. Some products blur that boundary by combining a controller interface with an internal sound engine, but the controller function is still the generation and routing of control data rather than audio.
Table of Contents
Why a MIDI controller can make no sound
This is the first practical distinction to understand.
A MIDI keyboard may look like a synthesizer, but a pure controller has no onboard oscillator, sampler, piano engine, amplifier, or speaker responsible for generating the played sound.
The signal flow is more like:
Key press -> MIDI controller -> MIDI data -> software or hardware instrument -> audio -> speakers
For a computer setup:
Key press -> USB MIDI -> DAW or instrument plug-in -> audio engine -> audio interface or computer output -> speakers/headphones
The MIDI controller describes the performance.
The receiving instrument creates the sound.
This is why connecting a USB MIDI keyboard to a computer and pressing keys can produce complete silence until:
- the operating system recognizes the controller;
- a DAW or software instrument is running;
- the correct MIDI input is enabled;
- the track or instrument is receiving the MIDI channel;
- audio is routed to an output.
MIDI is not audio
MIDI messages describe events and control values.
They can represent information such as:
- play note 60;
- velocity 100;
- stop note 60;
- move modulation wheel to 73;
- bend pitch upward;
- press harder on a held key;
- change program;
- press sustain pedal;
- move a fader.
None of those messages contains the acoustic waveform of a piano, synthesizer, or drum.
That separation is one of MIDI’s strengths. The same performance data can play many different instruments without rerecording the notes.
What a MIDI controller sends
A controller can generate many kinds of MIDI data.
Note On and Note Off
A keyboard, pad, drum trigger, or other note-producing surface normally sends a Note On message when a note begins.
In MIDI 1.0, Note On is a Channel Voice message containing:
- status and MIDI channel;
- note number;
- velocity.
The status-byte pattern is:
1001nnnn
where nnnn identifies one of 16 MIDI channels.
The first data byte contains the note number from 0 to 127.
The second contains velocity from 0 to 127.
For example, note number 60 is commonly used for middle C in MIDI note-number tables.
A receiver may also interpret a Note On message with velocity 0 as Note Off behavior, a convention explicitly defined in MIDI 1.0.
Velocity
Velocity represents the performance intensity associated with the initial note event.
On many keyboard mechanisms, velocity is derived from timing, not from a direct force measurement.
A common design uses two sensing events at different points in the key travel.
If the time between those events is short, the key was moving quickly.
The controller maps that timing into a MIDI velocity value.
The exact sensor arrangement, scan method, timing algorithm, and velocity curve are manufacturer-specific, so “all MIDI keyboards use two rubber contacts” would be too broad.
Control Change messages
Knobs, faders, pedals, switches, and wheels often transmit Control Change, commonly shortened to CC.
A MIDI 1.0 CC message contains:
- status/channel;
- controller number;
- controller value.
The status is:
1011nnnn
or hexadecimal 0xB0 to 0xBF depending on channel.
The controller number identifies the function.
The value normally ranges from:
0 to 127
Common defined examples include:
- CC1: Modulation Wheel or Lever;
- CC7: Channel Volume;
- CC10: Pan;
- CC64: Damper/Sustain Pedal.
Other CC numbers may be assigned to instrument-specific parameters or used through a DAW’s MIDI Learn system.
Pitch Bend
Pitch Bend is not an ordinary 7-bit CC.
MIDI 1.0 gives it a dedicated message with two 7-bit data bytes, producing 14-bit resolution:
16,384 possible values
with center at:
8192 decimal
or:
0x2000
The receiving instrument determines how that numerical range maps to semitones or cents.
The dedicated Pitch Bend article covers bend range, RPN Pitch Bend Sensitivity, center values, and per-note bend in expressive systems.
Aftertouch
Pressure-capable controllers may transmit aftertouch.
Two MIDI 1.0 message types are important:
- Channel Pressure, one pressure value for the channel;
- Polyphonic Key Pressure, a separate pressure value associated with a note number.
A keyboard specification that simply says “aftertouch” should therefore be checked carefully. It may mean channel pressure, polyphonic pressure, or pressure on pads rather than on the keys.
Keyboard controllers, pad controllers, and other forms
“MIDI controller” does not mean only “MIDI keyboard.”
The category includes many physical interfaces.
Keyboard controllers
A MIDI keyboard usually combines:
- piano-style keys;
- velocity;
- octave and transpose controls;
- pitch bend;
- modulation;
- sustain-pedal input;
- knobs or encoders;
- pads;
- faders;
- transport controls.
Different sizes suit different workflows.
Compact 25-key models prioritize desk space and portability.
49- and 61-key controllers offer more performance range.
88-key hammer-action controllers prioritize piano-style playing.
Pad controllers
Pad controllers emphasize velocity-sensitive pads for:
- drums;
- samples;
- clips;
- chords;
- melodic playing.
Pads may also support pressure after the initial hit.
The physical feel can be more appropriate than piano keys for finger drumming even when both send the same MIDI note numbers.
Fader and knob controllers
Some controllers focus on:
- mixing;
- automation;
- plug-in parameters;
- virtual synth editing;
- live performance.
Their main controls may be:
- faders;
- rotary potentiometers;
- endless encoders;
- buttons;
- touch strips.
Foot controllers
Footswitches and expression pedals let performers control MIDI while both hands remain occupied.
Applications include:
- sustain;
- patch changes;
- expression;
- effect bypass;
- loop control;
- organ-style expression;
- guitar-rig control.
Wind, guitar, and multidimensional controllers
MIDI can also be generated by interfaces modeled after:
- wind instruments;
- guitars;
- touch surfaces;
- multidimensional key surfaces;
- gestural controllers.
The defining feature is not the physical shape.
It is the device’s role in converting performance gestures into MIDI data.
MIDI controller vs synthesizer
A synthesizer generates sound.
A MIDI controller generates control data.
A modern hardware synthesizer can do both.
For example, a keyboard synthesizer may:
- play its internal sound engine;
- transmit MIDI notes through USB or DIN;
- send pitch bend and modulation;
- act as a controller for a software instrument.
That does not turn “synthesizer” and “MIDI controller” into synonyms.
The same hardware contains two functional roles.
Local Control
Many hardware synths provide a Local Control setting.
When Local Control is on, the keyboard directly controls the instrument’s internal sound engine.
When Local Control is off, the keyboard and sound engine can be separated internally so MIDI is routed through an external sequencer or DAW.
This is useful in studio setups where the DAW should determine what receives the performance data.
MIDI controller vs sound module
A traditional sound module is almost the inverse of a pure MIDI keyboard controller.
A controller provides the playing interface but may have no sound engine.
A sound module provides the sound engine but may have no piano-style keyboard.
Connect them:
MIDI controller -> sound module -> audio output
and the two devices together behave like a playable electronic instrument.
Modern computers and plug-ins perform the sound-module role in many studios, but the conceptual split is the same.
MIDI controller vs DAW control surface
A DAW control surface is designed specifically to operate recording and mixing software.
It may provide:
- motorized faders;
- pan encoders;
- mute, solo, and record-arm buttons;
- transport;
- jog wheel;
- automation controls;
- track names or parameter displays.
Some control surfaces also function as general MIDI controllers.
Some MIDI keyboards include a control-surface mode.
The categories overlap, but they are not identical.
Standard MIDI CC mapping
A generic controller can expose a knob as CC74, for example.
A DAW or plug-in can then map that CC to a parameter.
This is simple and flexible.
For one-way control, it can work extremely well.
Deep DAW integration
Mixer control often needs more than “knob sends CC value.”
Useful bidirectional functions include:
- motorized fader positions following automation;
- LEDs reflecting mute/solo state;
- track names shown on hardware;
- parameter names and values returned from software;
- banking across tracks;
- plug-in parameter pages.
Manufacturers therefore use DAW integration scripts, device APIs, SysEx, and control-surface protocols such as Mackie Control or HUI.
Those systems may transport information over MIDI connections while assigning MIDI messages special meanings defined by the control-surface protocol.
They should not be confused with open, universal MIDI CC semantics.
MCU and HUI are not part of the MIDI Association’s standard CC table.
Potentiometers vs endless encoders
The type of physical control changes how a controller behaves.
Potentiometer
A conventional rotary potentiometer has a physical minimum and maximum position.
It naturally represents an absolute setting.
If the knob is physically at 20% but a software parameter is currently at 80%, moving the knob can create a sudden parameter jump unless the software or controller uses a pickup mode.
Endless encoder
An endless encoder has no fixed end position.
It detects rotation rather than one permanent absolute position.
That makes it useful when:
- hardware changes between plug-in pages;
- presets have different values;
- one encoder controls many software parameters;
- a DAW sends parameter state back to the controller.
The exact MIDI messages used by relative encoders vary among controller modes and software implementations.
There is no single universal “relative encoder MIDI message” that every product must use.
Pickup, jump, and parameter mismatch
Physical faders create a practical problem when hardware and software positions disagree.
Suppose:
- the software cutoff is 90%;
- the physical fader is at 20%.
With Jump behavior, touching the fader can immediately move the software parameter to approximately 20%.
With Pickup behavior, the fader can remain inactive until it physically crosses the software’s current value.
This prevents sudden jumps.
Novation’s current Launchkey MK4, for example, provides Jump and Pickup behavior for faders in its settings.
Motorized faders solve the problem differently by physically moving to match the software state, but motorization is much more common on dedicated mixing surfaces than on standard keyboard controllers.
Keybed action
The mechanical action matters because the controller is an instrument interface, not merely a data source.
Synth-action
Synth-action keys are generally light and fast.
They suit:
- synth leads;
- bass lines;
- organ-style parts;
- rapid electronic performance.
Semi-weighted
Semi-weighted actions add resistance while remaining lighter than piano hammer actions.
They are common on larger studio MIDI controllers because they can work reasonably well for both synth and keyboard parts.
Hammer action
Hammer-action controllers attempt to reproduce more of the mechanical resistance and inertia of an acoustic piano action.
They are typically preferred by pianists and composers who prioritize piano technique.
The exact feel varies substantially among keybeds, so “synth-action,” “semi-weighted,” and “hammer-action” are broad product categories, not precise measurements of force or travel.
Velocity curves
A controller may let the player choose a velocity curve.
The curve changes how physical key speed maps to MIDI velocity.
A light curve can make high velocity values easier to reach.
A heavier curve can require faster key movement before high values are transmitted.
This can be important when the same keyboard is used for:
- piano libraries;
- drums;
- orchestral instruments;
- synth basses;
- velocity-switched sample libraries.
A technically correct velocity range does not guarantee a comfortable performance response.
The mapping curve matters.
USB MIDI and class compliance
USB is now one of the most common connections for MIDI controllers.
A single USB cable can often carry:
- MIDI data;
- bidirectional device communication;
- power.
It does not imply that the controller is sending audio.
USB is the transport.
MIDI is the data being carried.
What class-compliant means
The USB Implementers Forum defines standard USB device classes, including MIDI device classes.
A class-compliant USB MIDI device follows a standard interface that a compatible operating system can support without requiring a proprietary device-specific MIDI driver for basic operation.
USB-IF published the original USB MIDI Devices 1.0 class definition in 1999 and USB Class Definition for MIDI Devices 2.0 in 2020.
Class compliance is valuable because basic connectivity is not tied entirely to one vendor’s custom driver.
However, a class-compliant controller may still use optional manufacturer software for:
- firmware updates;
- custom mappings;
- DAW scripts;
- preset management;
- additional ports or modes;
- device configuration.
“Class-compliant” does not mean “the device has no software.”
5-pin DIN MIDI
The original MIDI hardware connection uses 5-pin DIN connectors.
A controller with DIN MIDI Out can often control hardware without a computer:
controller MIDI Out -> synth MIDI In
This is useful for:
- hardware synth rigs;
- rack modules;
- drum machines;
- live systems;
- computer-free setups.
Classic MIDI DIN operates at 31.25 kbit/s using the MIDI 1.0 electrical transport.
Because MIDI messages are serialized, several events do not literally travel down one MIDI cable at the same instant.
In ordinary performance that is rarely a problem, but dense MIDI traffic can create timing and bandwidth considerations.
TRS MIDI
Compact hardware often uses a 2.5 mm or 3.5 mm TRS connector instead of full-size 5-pin DIN.
Early products did not all use the same TRS wiring.
That created the familiar Type A vs Type B compatibility problem.
The MIDI Manufacturers Association later published the specification for using TRS connectors with MIDI devices, establishing the standardized TRS wiring used by compliant newer products.
A normal stereo aux cable does not solve every TRS MIDI compatibility problem.
The electrical pin mapping still has to match.
If two devices use different legacy TRS conventions, the correct adapter or crossover wiring is required.
MIDI over Bluetooth
MIDI can also travel over Bluetooth Low Energy.
BLE MIDI is useful for:
- tablets;
- phones;
- mobile controllers;
- stage setups where a cable would be inconvenient.
Wireless MIDI is not automatically “too slow for music,” but latency and jitter depend on:
- the controller;
- receiving device;
- operating system;
- wireless environment;
- buffering;
- software.
For timing-critical performance, wired USB or DIN remains easier to diagnose because fewer wireless variables are involved.
Do you need an audio interface for a MIDI controller?
Not necessarily.
A USB MIDI controller can connect directly to a computer.
The software instrument can generate audio through:
- the computer’s built-in output;
- USB headphones or speakers;
- an external audio interface.
The MIDI controller itself does not require an audio interface merely to send MIDI.
An audio interface becomes important when the production setup needs benefits such as:
- lower-latency audio drivers;
- microphone or instrument inputs;
- studio monitor outputs;
- headphone monitoring;
- better analog I/O;
- additional routing.
This is a useful distinction because “MIDI input” and “audio output” are separate parts of the signal chain.
MIDI controller latency
When a key feels delayed, the controller itself is only one possible source of latency.
The complete path may contain:
- key sensing;
- controller processing;
- MIDI transport;
- operating-system MIDI handling;
- DAW processing;
- software-instrument processing;
- audio buffer;
- D/A conversion;
- speaker or headphone path.
The audio buffer is often a major contributor in computer-based playing.
So replacing a MIDI keyboard may not fix a 30 ms software-monitoring delay if the real problem is an oversized audio buffer.
DIN transmission time
Classic MIDI DIN transmits at 31,250 bits per second.
One serial byte occupies 10 transmitted bits, so one byte takes approximately:
10 / 31,250 = 0.32 ms
A three-byte Note On therefore occupies about:
0.96 ms
when transmitted as a complete three-byte message.
Several messages on one serial MIDI connection are sent sequentially.
Running status and message type can change the exact byte count, so “every MIDI event takes 1 ms” is not a reliable universal rule.
Latency vs jitter
Latency is delay.
Jitter is variation in delay.
A system that consistently responds 5 ms late may feel more predictable than one that varies unpredictably between 2 and 10 ms.
For tight musical performance, stability matters as well as the average delay.
MIDI channels, zones, splits, and layers
MIDI 1.0 Channel Voice messages support 16 channels per MIDI port.
A controller can use those channels to organize a performance.
Split
A keyboard split assigns different key ranges to different destinations.
For example:
- left side -> MIDI channel 1 -> bass synth;
- right side -> MIDI channel 2 -> piano module.
Layer
A layer sends one played note to several destinations.
For example:
one key -> channel 1 strings + channel 2 piano
Zones
More advanced controllers use several keyboard zones, each with its own:
- key range;
- MIDI channel;
- transpose setting;
- velocity behavior;
- controller routing.
This is why older dedicated controller keyboards were often called master keyboards. Their job was to command several external instruments from one playing surface.
MIDI Learn and mapping
One of the fastest ways to use knobs and faders is MIDI Learn.
A typical workflow is:
- enable MIDI Learn in the plug-in or DAW;
- click the software parameter;
- move the hardware control;
- software associates the incoming MIDI message with that parameter.
For example:
encoder CC74 -> filter cutoff
The actual mapping can be stored by:
- the plug-in;
- the DAW;
- the controller;
- a controller template;
- a script.
Why CC numbers do not guarantee identical behavior
CC1 has a defined modulation-wheel meaning.
CC7 has a defined channel-volume meaning.
But many controller mappings use assignable or undefined CC numbers for arbitrary parameters.
A plug-in can also deliberately map a defined CC to something unconventional.
MIDI standardization makes data interoperable, but it does not force every synthesizer preset or DAW template to interpret every controller identically.
DAW integration scripts
Modern controllers often provide deeper integration through dedicated scripts.
A script can let hardware controls automatically follow the DAW context.
One encoder may control:
- track pan in mixer mode;
- plug-in parameter 1 in device mode;
- send level in send mode.
Buttons may change function according to the active track or software page.
This is different from a permanent one-to-one CC assignment.
Novation, for example, provides dedicated Launchkey integration for several major DAWs while also retaining Custom Modes and normal MIDI operation.
Arturia similarly provides dedicated DAW integration scripts for KeyLab mk3 while also supporting user MIDI mappings.
MIDI 2.0 and modern controllers
MIDI 2.0 expands the amount and structure of performance data available to compatible devices.
Relevant improvements include:
- higher-resolution controller data;
- higher-resolution velocity;
- Universal MIDI Packet, or UMP;
- bidirectional capability negotiation through MIDI-CI;
- Profiles;
- Property Exchange.
These features are important, but “MIDI 2.0 ready” should not be interpreted as “every feature automatically works with every computer, DAW, plug-in, and cable.”
A complete MIDI 2.0 workflow depends on several components supporting compatible parts of the ecosystem.
For a controller buyer, MIDI 1.0 compatibility remains extremely important because it is still the common interoperability layer across enormous amounts of hardware and software.
MPE controllers
MPE, or MIDI Polyphonic Expression, extends MIDI 1.0 workflows to provide independent expression for individual notes.
An MPE controller commonly gives each active note its own Member Channel.
That allows gestures such as:
- per-note pitch bend;
- per-note pressure;
- per-note timbre control.
This differs from ordinary channel-wide pitch bend or Channel Pressure.
It also differs from native Polyphonic Key Pressure, which includes the note number directly in the pressure message.
MPE belongs to the broader MIDI-controller world, but not every MIDI controller needs MPE to be useful.
Current hardware examples
Arturia KeyLab 61 mk3
The Arturia KeyLab 61 mk3 is a useful example of a full-size studio controller that combines performance input with software and DAW control.
Arturia documents:
- 61 velocity-sensitive semi-weighted keys;
- aftertouch;
- 12 velocity- and pressure-sensitive pads;
- nine rotary controls;
- nine faders;
- pitch and modulation wheels;
- MIDI In and Out;
- USB-C;
- DAW integration scripts;
- MCU/HUI compatibility;
- customizable MIDI operation.
That combination illustrates how a modern MIDI controller can move between three roles:
- keyboard performance;
- virtual-instrument parameter control;
- DAW operation.
Affiliate disclosure: MPG may earn a commission from qualifying purchases made through affiliate links, at no extra cost to you. See the affiliate disclosure.
Arturia KeyLab 61 mk3 Black at Thomann is a current 61-key example with aftertouch, pads, faders, encoders, USB-C, and 5-pin MIDI I/O.
Novation Launchkey 49 MK4
The Novation Launchkey 49 MK4 shows a different balance between keyboard, pad performance, custom MIDI mapping, and DAW integration.
Novation documents:
- 49 semi-weighted keys;
- 16 velocity-sensitive pads with polyphonic aftertouch;
- eight endless encoders;
- nine faders;
- pitch and modulation wheels;
- USB-C;
- 5-pin MIDI Out;
- custom pad, encoder, and fader modes;
- dedicated integrations for several major DAWs;
- HUI compatibility for other DAWs.
An important detail is that the pads support polyphonic aftertouch. The 49-key keyboard itself is not advertised as an aftertouch keybed.
Novation Launchkey 49 MK4 at Thomann is a current keyboard controller with extensive DAW controls and polyphonic-aftertouch pads.
Common MIDI controller mistakes and myths
“A MIDI keyboard should make sound when connected to speakers”
Not if it is a pure controller.
It sends MIDI data.
A synth, plug-in, sampler, sound module, or other receiving sound engine must generate audio.
“USB MIDI means USB audio”
No.
The same USB connector family can carry many kinds of data.
A controller can send USB MIDI without containing an audio interface.
“Every knob sends MIDI CC”
No.
A controller may use:
- CC;
- NRPN or RPN;
- pitch bend;
- note messages;
- SysEx;
- proprietary data;
- DAW integration scripts;
- a control-surface protocol.
Check the selected operating mode.
“All endless encoders send the same kind of relative MIDI data”
No.
Relative encoder conventions differ among hardware and software implementations.
A DAW or plug-in must understand the selected mode.
“MCU and HUI are standard MIDI CC mappings”
No.
They are control-surface protocols that can use MIDI messages as transport building blocks with protocol-specific meanings.
Their behavior should be configured through the DAW’s control-surface system, not assumed from the standard CC table.
“Class-compliant means no software is ever needed”
No.
Basic MIDI communication may use standard operating-system support while optional software is still required for firmware, templates, mappings, scripts, or advanced device configuration.
“DIN MIDI is always slower than USB in a musically obvious way”
Too simple.
Classic DIN MIDI has a fixed serial bandwidth, but total perceived latency depends on the entire performance and audio path.
USB does not automatically guarantee lower end-to-end musical latency.
“A more expensive controller sends better-sounding MIDI”
MIDI data itself does not have audio tone.
A more expensive controller may offer:
- better key action;
- more consistent velocity;
- aftertouch;
- more controls;
- better build quality;
- displays;
- motorized controls;
- deeper integration;
- better sensor behavior.
Those features can improve performance and workflow, but they do not make the binary note number “warmer.”
“MIDI 2.0 makes MIDI 1.0 obsolete”
No.
MIDI 2.0 adds major capabilities while interoperability with MIDI 1.0 remains essential.
A useful controller in a modern studio may still spend much of its life communicating with MIDI 1.0 devices and software.
What to check when choosing a MIDI controller
The useful specification depends on the workflow.
For playing instruments, consider:
- number of keys;
- key size;
- synth, semi-weighted, or hammer action;
- velocity response;
- aftertouch;
- pitch and modulation controls;
- pedal inputs.
For beat production:
- pad size;
- velocity response;
- pressure support;
- pad layout;
- note/chord modes.
For plug-in control:
- encoder count;
- faders;
- pickup modes;
- display feedback;
- mapping software;
- MIDI Learn workflow.
For DAW mixing:
- dedicated DAW scripts;
- control-surface support;
- feedback from the DAW;
- motorized vs non-motorized faders;
- transport controls;
- track banking.
For hardware rigs:
- 5-pin DIN or TRS MIDI;
- MIDI In as well as Out if needed;
- standalone operation without a computer;
- power requirements;
- zones and channel routing.
For expressive performance:
- channel or polyphonic pressure;
- MPE;
- high-resolution control where supported;
- configurable curves;
- sensor behavior.
The most useful controller is the one whose physical interface matches the work being performed.
Related terms
- MIDI: the digital communication system carried by the controller’s messages.
- Aftertouch: pressure expression available on some keys and pads.
- Modulation Wheel: commonly transmits MIDI CC1.
- Pitch Bend: a dedicated high-resolution MIDI 1.0 performance message.
- Modulation: MIDI controller data often becomes modulation inside a synth or effect.
- Control Voltage: MIDI-to-CV conversion lets a MIDI controller operate voltage-controlled synthesizers.
- Polyphony: interacts with channel-wide and per-note expressive control.
- MPE: a multi-channel MIDI 1.0 method for independent per-note expression.
- Control Surface: hardware optimized for DAW mixer, transport, automation, and parameter control.
- Class-Compliant: a USB implementation that can use a standard operating-system device-class driver for basic communication.
- MIDI CC: Control Change messages used for pedals, wheels, knobs, faders, and many assignable parameters.
References and further reading
- The MIDI Association: Summary of MIDI 1.0 Messages
- The MIDI Association: MIDI 1.0 Control Change Messages
- The MIDI Association: MIDI Transports
- The MIDI Association: TRS Connectors with MIDI Devices
- The MIDI Association: MIDI Specifications
- USB-IF: USB Class Definition for MIDI Devices 2.0
- Arturia KeyLab mk3
- Novation Launchkey 49 MK4