MPC Pad Perform Mode: scales, chords, and progressions on 16 pads

The short version

The Pad Perform window lets you assign musical scales/modes, chords, or progressions to the pads for more creative performance. It only works on keygroup, MIDI, plugin, or CV tracks; you can technically open it on a drum track, but Akai's own manual is blunt about the result: it does not work there. A Type field picks what the pads represent (a chromatic scale, a chord voiced per scale degree, or a saved progression), a Scale field with twenty-one modes and a Root Note decide what key that mapping sits in, and a Banks field decides whether the pattern keeps climbing across pad banks or resets to the root on every bank. Nothing here needs Pad Perform's own menu entry to first appear, either: select a new keygroup track after sampling into it and the hardware drops you into this mode automatically, no extra step.

WORKING PRODUCER'S NOTE: this is the mode that turns "I sampled one note" into "I have an instrument." Most people who use MPC hardware daily know the pads as drum triggers and never open this window on purpose, they just end up in it after a Quick Sampling pass drops them into a new keygroup track. Worth learning it deliberately once, because the Type field alone is the difference between "notes ascending by semitone" and "full chords voiced correctly in a set key, playable with one finger per pad." That second one is not a party trick, it's how you sketch a chord progression on hardware in under a minute.

What Pad Perform Mode actually is

Every other mode on this site's mode-by-mode coverage repurposes the 16 pads for something non-musical: Clip Launch mode turns them into eight-color status triggers, Track Mute mode turns them into per-track on/off switches. Pad Perform is the one that keeps them musical but changes what they're musical as. Instead of one pad per drum sound, the touchscreen shows the current pad bank's mapping of notes or chords, and that mapping is entirely configurable: a straight chromatic run, a scale-locked run, full chords, or a saved progression you built somewhere else.

It's the same window MPC Keygroup Tracks already flagged in passing: sample into a new keygroup track through Quick Sampling and the last step of that walkthrough puts the pads into Pad Perform mode automatically, no menu trip required, specifically so you can play the fresh sample back melodically right away. That's the clearest single proof of what this mode is for: it's not a performance toy bolted onto the side of sampling, it's treated as the default way to audition a pitched sample the moment it exists.

Opening it, and where it opens itself

Three documented paths in, on top of the automatic keygroup case above: tap the Pad Perform icon in the Track section of Main Mode, press the dedicated Pad Perform button (MPC X only), or hold Shift and press 16 Level, a shortcut named for MPC Live, Live II, One, One G2, Key 61, Key 37, and Key 37 G2. That Shift-plus-16-Level shortcut shares its physical button with an entirely unrelated feature, 16 Level velocity mapping, covered in full in Note Repeat and 16 Levels on an MPC, and that article's own version-note already flags the same drum-track restriction pattern from the opposite direction.

The Type field: six ways to map the pads

The type selector in the top-left decides what gets mapped across the pads. Six options, each documented with its own exact behavior:

Chromatic is the one shown in this article's own image above: notes climb straight up in semitones with no gaps, but the lit/unlit coloring still tells you, at a glance, which of those semitone pads actually sit inside the current scale. That's the mode's whole design philosophy in one Type option, chromatic access with scale guidance layered on top, rather than forcing you to choose between the two.

Scale, Root Note, and Octave

The Root Note field sets the starting point of the scale, chosen from every chromatic note across the pads' range; the pad carrying that root note lights up differently from the rest and is highlighted on the touchscreen too, so you always know where the scale starts in each octave. The Scale Type field sets which scale or mode is built from that root, and it's disabled entirely when Type is set to Progressions, since a saved progression carries its own key. Twenty-one scales and modes ship on the list: Major, Natural Minor, Harmonic Minor, Pentatonic Major, Pentatonic Minor, Blues (minor), Flamenco, Gypsy, Hungarian Gypsy, Persian, Major Bebop, Whole Tone, Chromatic, Phrygian, Dorian, Mixolydian, Aeolian, Locrian, and Lydian round out the modal set. That "Chromatic" entry inside the Scale Type list is a separate thing from the Chromatic Type option covered above: one decides what's mapped to the pads at all, the other is just one of twenty-one possible scale shapes that mapping can be built from.

The Chord fields

When Type is set to Chords or Chromatic Chords, the Chord fields decide exactly which chord voicing plays under each pad press, built from scale degrees relative to that pad's own root note. The two Types don't share one chord list, they each get their own:

Read the table straight: the Chords Type gives you five scale-degree shapes described by their interval formula, all locked to the key set in Scale. The Chromatic Chords Type trades that formula-based list for ten named chord qualities you can trigger regardless of key, the tradeoff already stated in the Type field description above, more chord variety in exchange for giving up the automatic key-locking.

Progressions: saved chord sequences

Set Type to Progressions and each pad carries one chord from a saved chord progression, playable in order to build a song fast or out of order for something less linear. The available chords come from the Chord field, and progressions themselves are external files: build them in the MPC software, then transfer them to the hardware by creating a folder named Progressions on an external storage device's root level and copying the .progression files there. On a computer, MPC Software's own default save location for progressions is C:\Program Files\Akai Pro\MPC\Progressions and/or C:\ProgramData\Akai\MPC\Progressions on Windows, or ~/Library/Application Support/Akai/MPC/Progressions on macOS; your MPC hardware scans whatever Progressions folder you create on removable media and adds the results to the available list. Practically, this Type is the one built for the exact workflow the site's own Song Mode article covers from the arrangement side: play a saved progression's pads to sketch a chord sequence, then arrange the resulting sequences into a full song once you like the order.

Custom mode and the three note-map presets

Custom lets you assign a specific note to each pad by hand: tap Edit Note Map, select a pad either on the touchscreen or by pressing it on the hardware, then set the desired note in the MIDI Note field. Tap Close, the X, or anywhere outside the window when you're done. Three named presets sit under Custom too: Chromatic C1, Chromatic C2, or Classic MPC. The Pad Perform chapter itself never explains what those three names mean; the definitions live in a completely different part of the manual, the general-purpose Edit Pad Note Map function documented under track functions, which happens to use the identical three preset names for its own pad-to-MIDI-note mapping: Chromatic C1 is an ascending chromatic scale beginning at C1, Chromatic C-2 is the same shape starting an octave-plus lower at C-2, and Classic MPC is the default MIDI note map used by classic MPC hardware. Worth being precise about what we're claiming there: Akai's manual defines those three preset names once, inside the separate Edit Pad Note Map function, and never repeats the definitions inside the Pad Perform chapter itself, which just names the presets without elaborating. We're treating the shared names as the same three layouts rather than a coincidence, since both features use them for the identical purpose, mapping specific MIDI notes across the 16 physical pads, but the manual itself never states outright that Pad Perform's Custom presets and Edit Pad Note Map's presets are implemented as the same underlying data.

The Banks field

The Banks field decides how a Pad Perform mapping continues, or doesn't, when you switch pad banks. Set it to Continuous and Pad 01 of the next bank picks up exactly one scale degree higher than Pad 16 of the bank before it, so the full mapping reads as one long, unbroken run across every bank on the project. Set it to Start on Root instead and every single pad bank resets to the scale's root note on Pad 01, trading that continuous run for a mapping that's identical, and therefore predictable, on every bank you switch to. That's the actual tradeoff, and it maps cleanly onto two different playing styles: Continuous rewards players who think of the pads as one long keyboard split across banks, Start on Root rewards players who'd rather memorize one shape and get it back identically no matter which bank they land on.

Quick-select buttons and shortcuts

A row of buttons at the bottom of the screen sets Type without opening the field's own selector: Notes and Chords each jump straight to their own Type, Progressions does the same, and Octave −/+ shifts every pad assignment down or up a full octave at once. A separate set of Shift-modified button presses jumps directly into a specific chord: Shift+1-3-5 sets Type to Chords and Chord to 1-3-5, and Shift+1-4-5, Shift+1-3-5-7, and Shift+1-3-5-7b do the same for their respective chord shapes. Shift+Note −/+ shifts every pad assignment by a single semitone instead of a full octave, which is really just the Root Note field moved a half-step at a time. Every one of those shortcuts is documented as a change to the existing mapping, not a new window; none of them require leaving Pad Perform to reach the Type, Scale, or Root fields they're modifying.

Common mistakes and quick fixes

Mistake: opening Pad Perform on a drum track and assuming the pads are broken when nothing happens. They're not, Akai's own manual states plainly that Pad Perform doesn't function on drum tracks even though the window will technically open. Switch to a keygroup, MIDI, plugin, or CV track first.

Mistake: setting Scale Type and wondering why it's greyed out. That's expected behavior when Type is set to Progressions specifically, since a saved progression already carries its own key and doesn't need a separate scale applied on top.

Mistake: expecting Chords and Chromatic Chords to share one chord list. They don't. Chords gives you five interval-formula shapes locked to the current key; Chromatic Chords swaps that for ten named chord qualities playable in any key, at the cost of the automatic key-lock.

Mistake: building a Progressions file and never seeing it show up on the hardware. The hardware only scans a folder specifically named Progressions at the root level of external storage, not a subfolder or a differently named folder; the file extension has to be .progression too.

Mistake: assuming every current model gets the Shift+16 Level shortcut into this mode. MPC X uses its own dedicated Pad Perform button instead, not the Shift+16 Level combination; the Shift shortcut is named specifically for the Live, One, Key 61, and Key 37 model lines.

A note on manual versions

Rule two on this site is that conflicts and differences between sources get stated, not quietly resolved, and this article has one genuine, independently re-verified delta worth flagging. The Pad Perform chapter's substance, every Type, every field, every shortcut, is identical in wording between the current v3.9 guide and the older v3.7 guide, but two things around that identical text changed.

First, the page numbers moved. The chapter sits at pages 81 through 83 in the current v3.9 guide and pages 76 through 78 in the older v3.7 guide, a flat 5-page shift, consistent with the same-size shifts already disclosed in this site's mixer-guide and song-mode-arranging articles between these two manual versions.

Second, the Shift+16 Level shortcut's own device list grew. The v3.7 guide's line reads "Hold Shift and press 16 Level (MPC Live, MPC Live II, MPC One, MPC Key 61, and MPC Key 37)." The current v3.9 guide's version of the same line reads "Hold Shift and press 16 Level (MPC Live, Live II, One, One G2, Key 61, Key 37, Key 37 G2)," adding MPC One G2 and MPC Key 37 G2. A direct diff of both manuals' Pad Perform chapters confirms this is the single content change between the two versions, every other line, field, scale name, and chord list is word-for-word identical. That's not a copy-editing pass, One G2 and Key 37 G2 are genuinely newer hardware than v3.7's release; the shortcut list grew because Akai's hardware lineup grew, matching the identical pattern this site already disclosed for the Song Mode chapter's own Key 37 G2 addition.

Verdict

Found a Pad Perform quirk this didn't cover? Tell us what happened.