MPC Keygroup Tracks: the complete guide to multi-sampled instruments

The short version

Akai's own manual draws the line between a drum track and a keygroup track in one paragraph, and it's worth quoting both halves side by side because the wording is nearly identical except for the one word that matters: a drum track "uses one or more samples as its sound source... used mostly for creating drum parts and quickly and easily assigning samples to pads," while a keygroup track "uses one or more samples as its sound source... used to play samples chromatically with a MIDI keyboard or the MPC pads." Same raw material, one sample, two completely different jobs. A drum pad plays that sample at one fixed pitch every time you hit it. A keygroup plays it in tune, pitched to whatever note you press, and it can hold up to 128 keygroups in one track so a single instrument, a piano, a bass, a string patch, can span the entire range of a keyboard instead of living on one pad.

Getting there takes four things, in order: turning a sample into a keygroup track in the first place, setting the track-level fields that control how it behaves in your sequence, deciding whether you're editing it the old way or the new way, and, as of v3.9, deciding whether each layer plays back a sample at all or generates its own waveform through the new MPC Oscillators engine. All four are covered below, straight from Akai's own manual, page by page.

SOUND DESIGNER'S NOTE: the packs I review for a living, pianos, string sections, upright basses, are keygroup tracks wearing a nicer file name. Nobody ships you a raw keygroup screen, they ship you a folder of .XPM programs that already did this work. Understanding what's actually underneath one is the difference between loading a piano expansion and being able to build your own out of eleven one-shots and an afternoon.

What a keygroup track actually is

A project holds up to 128 tracks total, split across six track types, and Akai's own chapter intro lists keygroup right after drum, back to back, for exactly the comparison above. The structural definition is short: a keygroup track "contains (1) a list of samples and (2) the settings for each sample (i.e., pitch tuning, effects, etc.)," which is one item shorter than the drum track's definition, drum tracks additionally list "pad assignments" as part of what's tracked per sample, keygroups don't need that field because a keygroup's whole point is that the same sample plays differently depending on which note triggered it, not which physical pad you assigned it to.

In practice that means a keygroup track can still be played from the sixteen physical pads, MPC hardware puts it into Pad Perform mode automatically the moment you select one, but the pads are now a musical keyboard layout, not sixteen independent one-shots. Plug in a MIDI keyboard instead and you get the same instrument across the full width of the controller, which is the other half of why keygroup tracks exist: they're the format every multi-sampled instrument on this platform is built from, whether you built it yourself or bought it from an expansion pack.

Creating a keygroup track from an existing pad

Akai's own walkthrough uses the same example most people actually run into first: an 808 sound sitting on a drum pad that you want to turn into a playable bassline instead of one fixed-pitch hit. The steps, straight from the manual's Getting Started chapter:

1. With the drum track selected, press the pad holding the sample you want, then double-tap the sample area in the Track View of Main Mode to jump into Track Edit Mode.
2. Tap the Global tab, then tap the keyboard+ icon at the top of the screen. This instantly turns that sample into a keygroup track.
3. Press Main to return to Main Mode and select the new keygroup track. It's added at the end of your current track list.
4. Your MPC's pads are now in Pad Perform mode, letting you play the sample melodically across the pad grid.
5. Arm the arrangement (SEQ REC ARM, then REC) and press Play to record a bass part with the pads or a connected MIDI keyboard.

One small procedural difference is worth flagging because it's a genuine change, not just pagination, and it's checkable directly: the older v3.7 manual's version of step 2 is shorter, "tap the keyboard+ icon at the top of the screen to instantly turn this 808 sample into a Keygroup Track," with no mention of the Global tab at all. v3.9 adds "Tap the Global tab to select it, and then" in front of the same instruction, meaning the keyboard+ icon either moved or the manual simply got more precise about where to find it. Either way, if you're following an old tutorial or screenshot built on v3.7 and the icon isn't where step 2 says, check the Global tab first.

That one-time conversion is the fastest way in. The rest of this article covers what you can actually do with the track once it exists, which is considerably more than one bass note per pad.

Track Settings: MIDI routing, monitor modes, transpose

Every track type gets a Track Settings window, opened by tapping and holding the track name in Main Mode's Track Section, double-tapping the track header in the Channel Mixer or Arrange Mode, or, on MPC One G2 and Key 37 G2, holding Shift and pressing Track Edit/Track Settings. For a keygroup track, that window carries the following fields:

MIDI Monitor gets four states, worded the same way it is everywhere else in the manual this appears: Off plays back recorded events without monitoring live input (useful with Local Control active on a keyboard), In always monitors input regardless of Record Arm and doesn't play back recorded events, Auto monitors only while record-armed and does play back recorded events, and Merge always monitors input while also playing back recorded events at the same time.

A second, separate set of fields shows up in the Track Section of Main Mode itself, not the Track Settings window, when a keygroup track is selected: the sample waveform for the current layer with its Start, Loop, and End markers, a Monitor field with the same four states as above, a Length field (linked to the Sequence length, or set manually in Bars:Beats:Ticks), a Velocity field that scales the track's overall output level relative to how it was recorded, and its own Transpose field. Two icons sit at the bottom of that view too: a pad-perform icon that opens the Pad Perform window directly, and a pad/keyboard toggle that swaps the Mixer Channel Strip between Track and Keygroup views. Two Transpose fields, two Monitor fields, in two different screens, is a real source of "wait, which one did I just change" confusion, worth knowing they're not the same field mirrored twice, they're the Track Settings window's version and the Main Mode Track Section's version, and both affect the track.

Building a multi-sample instrument: up to 128 keygroups

This is the field that actually turns "one sample, chromatically pitched" into "a real multi-sampled instrument." From Track Edit Mode's Samples/Oscs tab, the Number of KG field sets how many keygroups the track holds, from 1 up to 128, and Akai's own example is the obvious one: build a realistic piano by assigning a different keygroup, with its own sampled note, to each of the 88 keys. Each of those keygroups isn't limited to a single sample either. The manual's own tip states the full math plainly: "a keygroup track offers up to 128 keygroups, and each keygroup can hold up to eight samples (Layers 1-8). This is a total of 1024 samples."

That's the actual ceiling on how deep a single keygroup track can go, and it's a genuinely large number: 128 keys' worth of pitch range, each one carrying up to eight separately assignable layers, commonly used for velocity switching, so a soft hit and a hard hit on the same key can trigger entirely different recordings instead of one sample just played louder or softer.

Track Edit Mode: Legacy vs Advanced, and the layer-count mixup

Open Track Edit Mode on a keygroup track and the first thing worth understanding is the Legacy button. Enable it and keygroup editing works exactly the way it did on previous MPC releases. Disable it, the default state, and you get what Akai calls the "Advanced keygroup synthesis engine" instead. Every section past that point in the manual is labeled with which mode it belongs to, Advanced, Legacy, or both, which matters if you're following an older tutorial built around Legacy behavior and a field it describes isn't where the tutorial says. Press a pad or key to select a keygroup, or use the Keygroup field at the top of the screen, and the tabs across the bottom, Global and Samples/Oscs among them, show that keygroup's parameters. You can also select All from the Keygroup field to edit every keygroup at once.

The Number of KG field lives here too, described the same way as its Samples/Oscs counterpart above, up to 128 keygroups, useful for multi-samples like an 88-key piano. But this is exactly where the manual trips over its own numbers, and it's worth quoting the actual text rather than rounding it to whatever sounds cleaner. The Number of KG paragraph's own piano example says every keygroup contains "its own sampled note (with up to four possible velocity layers)." Two sentences later, describing the Edit All Layers button on the exact same page, the manual says edits apply "uniformly to all eight layers at once (even if some layers are empty)." Four, then eight, on the same page, about the same feature. We checked which number holds up elsewhere in the manual rather than guessing: the Track Settings chapter's own tip says eight, "each keygroup can hold up to eight samples (Layers 1-8)," the Samples/Oscs subsection three pages later says it again almost verbatim, "Each keygroup can trigger up to eight samples or oscillators, which are assigned in eight individual layers," and the step-by-step "assign samples" procedure references "Layer 1-8" fields directly. Eight is the number that shows up everywhere except one parenthetical on page 215. Build for eight layers per keygroup, and treat "four" as a typo the manual never corrected, not a real, lower ceiling.

The Global tab, which the manual states works identically whether Legacy or Advanced editing is active, carries Global Semi and Global Fine (tuning the whole track), Transpose (shifting incoming MIDI notes), Poly (Mono plays one keygroup at a time and cuts off anything else playing, Poly lets several ring at once up to the total voice count), individual Key Group Semi/Fine per keygroup, Key Group Level and Pan, and Lo Key/Hi Key fields that restrict which notes trigger that specific keygroup at all, set Lo to A0 and Hi to C8 to emulate a full 88-key piano's range on a single keygroup.

MPC Oscillators: the new sound source that isn't a sample

Everything above assumes a keygroup layer is playing back a recorded sample. As of v3.9, that's no longer the only option. Akai's own release notes state it plainly: "Drum and Keygroup tracks can now use oscillators as a sound generator per layer instead of samples." The setup is a per-layer switch, not a track-wide mode change: select a Drum or Keygroup track, open Track Edit Mode, go to the Samples/Oscs tab, and for any individual layer, flip the Sample/OSC selector to an oscillator. The tab's appearance changes to show oscillator parameters, and the Oscillator field lets you pick a waveshape for that layer specifically, meaning one keygroup can mix sampled layers and oscillator layers side by side. Some oscillator waveshapes need extra downloadable content, and the manual points to a specific, named path for getting it: after switching a layer to Oscillator, tap the Get Oscillator Content button to jump straight to Preferences > Activations, where the required MPC Oscillator Content downloads.

You're not limited to Akai's own oscillator content either. The manual documents a specific drive folder structure for loading your own Single-Cycle or Wavetable waveforms as oscillator sources: create an Oscillators/SingleCycles/ folder at the root of a drive, drop each waveform library into its own subfolder underneath, and those single-cycle .wav files show up under User Single Cycles in the Oscillator source menu once the drive is connected. The rule is strict about structure: "Each Library Folder must contain only single-cycle .wav files. Do not include nested sub-folders." Wavetables work the same way under an Oscillators/Wavetables/ folder, but each wavetable folder additionally needs a hand-edited format.json file declaring exactly how many samples make up one cycle and how many cycles the file contains, get that file wrong and the manual is direct about the consequence: "any formatting errors or invalid values will prevent the wavetable from loading." One practical detail worth knowing before you build a project around user oscillator content and hand it to someone else: saving a Project or Track automatically copies the required user oscillator assets into that Project's or Track's own asset folder so it loads correctly on another MPC system, but factory oscillator content is deliberately not duplicated that way, since it's assumed to already be installed locally on the receiving machine.

SOUND DESIGNER'S NOTE: this is the feature I'd point a synth-curious sampler user toward first. You don't need a modular rig or a plugin synth to get a generated, non-sampled tone into a keygroup layer anymore, it's a field in the same Samples/Oscs tab you already use for multi-sampling, and it stacks with real samples on the same instrument. Layer a sampled piano note under an oscillator sub-bass on the low keys and you've built something a straight sample library can't ship you pre-made.

Why this is the expansion pack's engine room

Every multi-sampled piano, string patch, or bass instrument in an expansion pack you've ever loaded is a keygroup track someone else already built and saved off as a program. Our own roundup of the best MPC expansions ranks packs by how fast they get you from download to a playable beat, and the reason a well-built multi-sample pack feels instant is that the keygroup work, the Number of KG count, the Lo/Hi Key ranges per note, the velocity layers, is already done and mapped before you ever open the file. If you've followed our guide to installing expansion packs, the .XPM programs you dropped onto your drive are, for anything melodic in the pack, keygroup tracks in program form.

Understanding the mechanism changes what you can do with a pack once it's loaded. Want a piano patch to only cover the bottom two octaves so it stops colliding with a bass you're playing on another track? That's the Lo Key/Hi Key fields on the Global tab, not a limitation of the pack itself. Want to add your own layered texture underneath a purchased instrument's existing samples? That's an open Layer slot on an existing keygroup, up to eight per keygroup, waiting to be filled. The pack is the finished furniture. This article is the workshop it came out of.

Common mistakes

Mistake: expecting the keyboard+ icon to sit in the same spot an older tutorial describes. v3.9 adds an explicit "tap the Global tab first" step that v3.7's identical walkthrough doesn't include. If a screenshot from an older guide shows the icon somewhere else, check the Global tab.

Mistake: building a piano patch around "four velocity layers per keygroup" because that's what the Number of KG paragraph says. Every other mention of the same limit in the same manual, the Track Settings tip, the Samples/Oscs subsection, the Layer 1-8 field references, says eight. Build for eight, the "four" is an uncorrected inconsistency in one parenthetical, not a separate, lower ceiling that applies somewhere else.

Mistake: changing Transpose or Monitor in one screen and assuming it covers both. The Track Settings window and the Main Mode Track Section each carry their own Transpose field and their own Monitor field for the same keygroup track. They're not the same control mirrored twice.

Mistake: hunting for MPC Oscillators on a MIDI, Audio, or Plugin track. The feature is explicitly scoped to Drum and Keygroup tracks only, per Akai's own wording. It won't show up as an option anywhere else.

Mistake: dropping user Single-Cycle or Wavetable .wav files loose in a nested subfolder. The manual is explicit both times: each Library Folder "must contain only single-cycle .wav files" (or the .wav plus format.json pair, for wavetables) and must not include nested sub-folders. A folder structure that's one level too deep just won't show up in the Oscillator source menu.

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 checked four Keygroup Tracks sections against the older v3.7 manual specifically to see what changed. Two things did, and one thing very much did not shift the way earlier articles' version-note sections have shown.

Page numbers moved between the two manuals, and this time the shift is not a single flat offset the way it's been in prior comparisons on this site. Creating and Recording a Keygroup Track sits at page 13 in v3.7 and page 17 in v3.9, a 4-page shift. The Track Settings chapter's Keygroup Tracks section sits at page 46 in v3.7 and page 50 in v3.9, also a 4-page shift. The Main Mode Track Section's Keygroup Tracks entry sits at page 115 in v3.7 and page 120 in v3.9, a 5-page shift, one page more than the first two. The Track Edit Mode Keygroup Tracks chapter sits at page 207 in v3.7 and page 215 in v3.9, an 8-page shift, the largest of the four. We're stating that plainly rather than picking one number and implying it holds across the whole manual: it doesn't, this time the drift itself grows chapter by chapter.

The content itself is word-for-word identical across both versions in three of those four sections, the Creating and Recording walkthrough (aside from the one added Global-tab instruction noted above), the Track Settings fields, and the Main Mode Track Section fields all read the same in v3.7 as they do in v3.9. The fourth section is where a real, substantive change lives: v3.7's Track Edit Mode chapter says its tabs include "Global or Samples." v3.9's equivalent sentence says "Global or Samples/Oscs." That's not a typo or a renumbering artifact, it's the tab being renamed to reflect a feature v3.7 doesn't have at all.

We checked specifically and independently for MPC Oscillators anywhere in v3.7 rather than assuming its absence from the renamed tab was the whole story. The word "Oscillator" does appear in v3.7, twice, but neither instance is this feature: page 401 uses it inside the AIR Bassline plugin's own synth engine documentation ("Oscillator Waveform... continuously variable waveshape for the oscillator"), and page 410 uses it describing a Low-Frequency Oscillator inside an effects chapter. Neither is a Drum or Keygroup track sound-source option, and v3.7 has no equivalent to the "MPC Oscillators" feature section that opens v3.9's new-features chapter at all. We can confirm it's absent from v3.7 and present in v3.9. We only have these two manual versions on file to compare, so we're not claiming v3.9 is the exact release that introduced it, an intermediate v3.8 could have shipped it first, only that it did not exist in v3.7 and does exist in v3.9.

Verdict: the five-minute setup

Built a keygroup instrument worth sharing, or found a field this didn't cover? Tell us what happened.