MPC mute groups: the complete guide to choke groups

The short version

Akai's own manual states it as a flat number: 32 available mute groups per track, on both Drum tracks and Keygroup tracks. Assign two or more pads (or two or more keygroups) to the same numbered group and the mechanism is automatic and immediate: whichever one gets played last silences every other pad currently sounding in that same group, no separate mute step required. Akai's own manual states the use case twice, word for word close each time: programming realistic hi-hats, so only the open or closed hat is heard at once. That is Mute Group, and it is the feature this article is mainly about. Two other fields on the exact same screen get confused with it constantly, so this covers all three, plus a fourth screen that reuses the word "mute group" for something else entirely. Mute Targets lets one pad name up to four specific other pads to silence, with no group concept and no reciprocity. Pad Polyphony's Mono setting controls how a single pad behaves when it retriggers itself, not how it interacts with other pads. And Pad Mute Mode's Pad Group tab, several hundred pages later in the manual, is a live performance mute/solo tool capped at 16 groups, not the 32-slot field this article is centered on, despite using almost identical wording to describe itself.

RIO'S NOTE: the name collision between Mute Group and Pad Group is a real one, not something I'm making a big deal out of for no reason. Akai's own procedural text in Pad Mute Mode literally says "press it or tap it on the screen" to "add to a mute group." Read fast, that sentence sounds like it is walking you through setting the Program Edit Mute Group field by hand. It is not. It is a completely separate 16-slot feature for muting and unmuting clusters of pads during a performance. Different screen, different cap, different job. More on that further down.

Why this exists: the hi-hat problem

A real hi-hat is one physical object with two states, open and closed, and it can only be in one of them at a time. Step on the pedal or catch the cymbal with a stick, the ringing open hat cuts off. Program a drum part the naive way, one pad for the open hat sample and a separate pad for the closed hat sample, and MPC has no reason to know those two pads are supposed to behave like one physical hi-hat. Trigger both close together in a pattern and they both ring out on top of each other, open hat still decaying under a closed hat that just fired, which is not how a hi-hat has ever sounded in the physical world. Mute Group is the fix, and it works at the note-trigger level instead of requiring you to manually chop the tail of every open hat hit to make room for the next closed hat: put both pads in the same numbered group, and the moment the closed hat pad receives a note, the still-ringing open hat gets cut instantly, the same way it would if a drummer's foot came down on the real pedal. It is not limited to hi-hats specifically, any pads that should behave as mutually exclusive alternate takes of the same sound can share a group, but hi-hats are the case Akai's own manual reaches for, twice, in two different tabs on the same screen.

Mute Group on Drum tracks

The Mute Group field lives on the Pads tab of Program Edit for a Drum track, right next to Pad Polyphony and just above the Mute Targets tab. Akai's own description is short and states the mechanism plainly:

"Use the Mute Group field to assign the selected pad to one of the 32 available groups. When pads assigned to the same mute group receive MIDI notes, the last pad played will silence all other pads in that mute group. A mute group affects pads within that track only; mute groups do not affect pads in other tracks."

Three things worth pulling out of that paragraph specifically. First, the number: 32 groups per track, not a handful, so there is room to build several independent choke relationships (hats, two different sets of layered percussion, a pair of vocal chops that shouldn't overlap) without them stepping on each other. Second, the trigger condition is MIDI notes, meaning this fires during normal playback and normal performance, not just in some special editing mode, so it works whether the pad is hit from the sequencer, a connected MIDI keyboard, or the pads themselves. Third, and this is the part that trips people up when a kit spans more than one track: mute groups are scoped to the track. Two pads on two different Drum tracks can both be set to group 5 and they will never silence each other, only pads within the same track sharing that group number interact.

Mute Group on Keygroup tracks

Keygroup tracks get the identical field, same mechanism, same 32-slot cap, just scoped to keygroups instead of pads:

"Use the Mute Group field to assign the selected keygroup to one of the 32 available mute groups. When keygroups assigned to the same mute group receive MIDI notes, the last keygroup played will silence all other keygroups in that mute group. A mute group affects keygroups within that track only; mute groups do not affect keygroups in other tracks."

This matters for multi-sampled instruments the same way it matters for hi-hats, just less obviously. A sustain-pedal-style piano patch built across keygroups, or a set of layered pad textures that should crossfade rather than pile up, can use a mute group the same way a hi-hat pair does. If you're building a multi-sampled instrument from scratch, the full field-by-field breakdown of every Keygroup track parameter, including how Keygroup tracks differ from Drum tracks in the first place, is its own article. Mute Group is one line in that bigger picture, but it is the same field, doing the same job, on both track types.

Mute Targets: a narrower, direct-named tool

One tab over from Mute Group on the same Pads screen sits Mute Targets, and it is genuinely a different feature, not a second name for the same one, even though Akai's own manual draws the comparison directly:

"The Mute Targets tab lets you select up to four pads (in the same track) for the currently selected pad. When the currently selected pad is played, it will immediately silence its mute targets. Use each Pad field to select the desired mute target."

The structural difference from Mute Group is the whole point. Mute Group is many-to-many: any pad in the group can silence any other pad in the group, and which one wins is purely a matter of which one played most recently, no pad has priority over another. Mute Targets is one-directional and pad-specific: you pick one pad, then name up to four other named pads that get silenced the instant that one pad plays. The targets do not silence the source pad back, and they do not necessarily silence each other unless you've separately named them as each other's targets too. Akai's own tips section calls out both the shared use case and the shared spirit between the two features, while keeping them distinct:

"This feature is useful for programming realistic hi-hats, especially if only the open or closed hat should be heard. This feature is similar to the mute group feature, available for both drum tracks and keygroup tracks."

In practice, reach for Mute Targets over Mute Group when the relationship isn't symmetric, a ride bell choking a crash tail, or a specific fill hit that should cut a specific sustained pad, without wanting every other pad that might eventually join a numbered group to inherit that same choke behavior later by accident.

Pad Polyphony and Mono mode: not the same mechanism

The field directly above Mute Group on the same screen is Pad Polyphony, and it is worth a clear line drawn between it and Mute Group because both involve one hit cutting off a previous one. Akai's own wording:

"Use the Pad Polyphony field to determine how the pad's sound behaves when multiple hits are registered. When set to Mono, only one pad will sound at a time. If a pad is played while another (or the same one) is still playing its sample(s) or oscillator(s), the new pad will immediately mute all other currently playing pads in that track. When set to Poly, several pads can be triggered at the same time (limited only by the total number of voices available)."

Worth flagging plainly rather than smoothing over: that quoted paragraph's own wording, "the new pad will immediately mute all other currently playing pads in that track," reads almost identically to the track-wide Global Poly field description a page earlier, which genuinely does describe track-wide mono behavior. Akai never clarifies in the manual whether that phrasing for the per-pad field was meant literally (a single pad set to Mono choking every other currently playing pad in the whole track, not just itself) or is boilerplate carried over from the track-wide field's description. Treated at face value alongside its own field name, the practical, documented behavior to rely on is a single pad's own retriggers: hit the same pad again before its sample finishes, and Mono mode cuts the pad's own previous hit instead of letting both copies ring together, the way a real instrument only makes one sound per strike. That's a different mechanism from Mute Group entirely: Mute Group is explicitly cross-pad and requires two or more pads opted into the same numbered group by hand. Pad Polyphony's Mono setting is a single pad's own voice-stealing behavior, always on for that one pad once set, no second pad or group number required. You can also set Pad Polyphony to Poly, or to a specific voice count from 2 to 32, letting exactly that many simultaneous hits of the same pad ring before the oldest one gets cut.

Setting a Mute Group on the hardware

There's no separate procedural screen for this one, and that's worth saying directly since a couple of adjacent MPC features do have their own dedicated workflow modes. Setting a Mute Group is a normal Program Edit field edit: open Program Edit, select the Pads tab (or the Keygroup track's equivalent Keygroup tab), select the pad or keygroup you want to assign, then tap or turn to the Mute Group field and dial in a number from 1 to 32, or Off to remove it from any group. Do that for every pad or keygroup that should share the same choke relationship, using the same group number for all of them, and the behavior is live the next time any of those pads receive a note. Nothing about it requires leaving Program Edit or entering a separate mode. That's a deliberate contrast with the next section, because a separate mode does exist, uses almost the same words to describe itself, and is not the same feature.

Pad Mute Mode's Pad Group is a different feature

This is the genuine mixup risk in this whole topic, and it's worth stating plainly rather than resolving it quietly. Pad Mute Mode, a separate hardware mode entered from Menu or a dedicated Shift combination, has its own Pad Group tab, and Akai's own procedural text for it uses the phrase "mute group" repeatedly to describe it:

"The pad group feature extends the concept of pad mutes: you can mute or unmute multiple pads (on a single track) by pressing one pad that you have assigned to a mute group. This is useful if you want to hear a track without a particular group of sounds or if you want to isolate specific sounds in various combinations. You can create up to 16 different pad groups. To use pad groups: 1. If the Pad Group tab in the lower-left corner is not already selected, tap it. 2. Use the Pad Bank buttons to select the desired pad bank. 3. To select a pad to add to a mute group, press it or tap it on the screen. The selected pad is lit green. If there are other pads in the same mute group, they will flash yellow. 4. To add the pad to the mute group, tap the number of the desired mute group on the left side of the screen. To remove it from the mute group, tap Off."

Read on its own, that passage sounds like the hands-on version of everything covered above. It is not. Line up the two features side by side and the differences are real: Pad Group caps out at 16 groups, not 32. Pad Group lives in Pad Mute Mode, reached from Menu or Shift plus Track Mute/Pad Mute, a screen built for live performance muting and soloing of pads, not from Program Edit where every other pad-level synthesis and playback parameter lives. And the mechanism itself is different in kind, not just in scale: pressing a pad in a Pad Group toggles a manual mute or unmute state for every pad in that group at once, a performance move you trigger with your hand, while Mute Group has no manual toggle at all, it fires automatically and only in response to MIDI notes during playback, the instant a same-group pad is played. One is something you do. The other is something that happens on its own once you've set it up. They share the phrase "mute group" in Akai's own procedural writing because they solve a conceptually related problem, keeping certain sounds from piling up, but they are not the same field, the same cap, the same screen, or the same trigger condition, and treating Pad Mute Mode's walkthrough as instructions for setting the Program Edit Mute Group field will leave you in the wrong mode entirely.

Common mistakes

Mistake: looking in Pad Mute Mode to set a Mute Group. Pad Mute Mode's Pad Group tab is a separate 16-slot live-performance mute/solo feature, not a hands-on path to the 32-slot Program Edit Mute Group field. Set Mute Group in Program Edit's Pads (or Keygroup) tab directly.

Mistake: assuming a mute group works across tracks. It doesn't, on either Drum tracks or Keygroup tracks. Two pads in the same numbered group on two different tracks will never silence each other. If a kit is spread across multiple tracks, each track needs its own group assignments.

Mistake: expecting Mute Targets to be mutual. Naming pad B as pad A's mute target means playing A silences B. It does not automatically mean playing B silences A, unless you've separately gone into B's own Mute Targets tab and named A there too.

Mistake: reaching for Pad Polyphony Mono when the goal is two different pads choking each other. Mono mode governs one pad's relationship to its own retriggers. To make two separate pads, like an open and closed hat on different pads, choke each other, that's Mute Group or Mute Targets, not Pad Polyphony.

A note on manual versions

Every technical claim above is checked directly against Akai's Standalone OS User Guide, Manual Version 3.9, extracted one page at a time and matched against that page's own printed footer number: the drum track Mute Group, Mute Targets, and Pad Polyphony fields on page 194, the keygroup track Mute Group field on page 218, the Pad Mute Mode entry point on page 262, and the Pad Group workflow steps on page 265. Every one of those was cross-checked against Manual Version 3.7 and confirmed word-for-word identical in content, with the page numbers shifted: 188, 210, 252, and 255 respectively. That drift is not uniform across the manual, the same pattern this site's Time Stretch and Warp guide already found and disclosed: the drum-track pad section shifted by 6 pages between versions, the keygroup section shifted by 8, and the Pad Mute Mode section, further into the manual, shifted by a full 10 pages.

One correction worth stating directly: this assignment's own brief, working from an earlier pass at these page numbers, cited the drum-track pad section as page 193 and the keygroup section as page 217. Direct single-page extraction against both PDFs placed the actual quoted text one page later in each case, 194 and 218. The Pad Group workflow section was similarly narrowed from a loosely estimated page 260 to 264 range down to its exact page, 265, with the Pad Mute Mode entry point itself confirmed separately at page 262. Every number in this article reflects that direct, page-by-page verification, not the original estimate.

The larger disclosure, stated plainly rather than smoothed over per this site's standing rule that conflicts get disclosed, not silently resolved: Pad Mute Mode's Pad Group feature and Program Edit's Mute Group field are not the same feature, despite both being described with the phrase "mute group" in Akai's own manual text, and despite living roughly 70 pages apart from each other in the same document. One is a 32-slot, per-pad or per-keygroup field that fires automatically on MIDI note input. The other is a 16-slot, screen-based live performance tool that fires manually when you press a pad. This article treats them as the separate features their own field caps and trigger mechanisms prove them to be, rather than presenting Pad Mute Mode as a hands-on alternate path to setting the Program Edit field, which the initial framing for this piece assumed and which a direct read of both sections does not support.

Verdict

Found a mute group trick or a hat pair worth sharing? Tell us what happened.