Skip to main content
MIDI Command Studio

MIDI controllers and device guides.

MIDI Command Studio can work with many MIDI controllers that expose suitable controls to Windows. The devices below have dedicated guides; they are not a complete compatibility list.

Use MIDI Command Studio free to test MIDI Learn with your own device.

Standard MIDI mapping and hardware feedback are different.

Standard mapping

Standard MIDI controls

If MIDI Command Studio can learn a suitable control, it can be mapped to a supported Windows action. This commonly includes buttons, pads, knobs, faders, encoders, and jog wheels.

  • Keyboard shortcuts and macros
  • System, application, and input volume
  • Application targeting and preset switching

Device dependent

Hardware feedback

LED, LCD, and motorised-fader feedback depends on the controller, its selected mode, its MIDI implementation, and any supported protocol behaviour.

  • LED state feedback
  • LCD or text feedback
  • Motorised fader positioning

Device and protocol guides.

Choose a guide for your device or protocol.

Akai LPD8 MK2

Use its Note/CC pads and knobs for Windows shortcuts, macros, media controls, volume, and four hardware layouts.

Open device guide

Korg nanoKONTROL2

Use its faders, knobs, buttons, and LEDs for Windows volume, shortcuts, macros, media controls, and presets.

Open device guide

Behringer X-Touch One

Use its fader, buttons, LEDs, and LCD for Windows volume, shortcuts, presets, and MCU channel workflows.

Open device guide

Mackie / MCU

Use compatible single- and multi-fader MCU control surfaces for Windows volume and actions with supported feedback.

Open protocol guide

An unlisted MIDI controller may still work.

If Windows exposes suitable MIDI controls that MIDI Command Studio can learn, they may be mapped even when the device does not have a dedicated guide. Use MIDI Command Studio free to test your device.