MPC Channel Mixer vs. Pad Mixer: the complete guide

The short version

The Channel Mixer sets levels, stereo panning, and other settings for your tracks, submixes, returns, and main outputs. The Pad Mixer sets levels, stereo panning, and other settings for individual pads, and Akai states the restriction plainly: this mode is only available for Drum and Keygroup tracks. Open the Channel Mixer from Menu > Channel Mixer, or press Mixer. Open the Pad Mixer from Menu > Pad Mixer, or press and hold Shift and press Mixer. Both mixers use the identical five tab names in the identical order, Volume, Pan & Volume, Sends, Effects, I/O, which is exactly why the two get confused. The content behind those names is not identical, the I/O tab in particular means something different at track level than it does at pad level, and we cover the actual differences tab by tab below.

There's also a third way to touch either mixer without formally opening it: the XL Channel Strips docked on the left edge of the screen, which mirror whichever pad, track, or main output is currently selected. And there's one real gotcha that trips people constantly: turn up a Sends knob on a track or a pad with nothing loaded on the matching return, and you'll hear silence, not because anything is broken but because the send has nowhere to go yet.

WORKING PRODUCER'S NOTE: the mistake I see most is someone opening the Pad Mixer expecting to fix a track-level balance problem, or opening the Channel Mixer expecting to nudge one pad's level, and neither screen has the control they're looking for because they're in the wrong scope entirely. Channel Mixer is the whole track sitting in your session. Pad Mixer is one hit inside a Drum program. Get that distinction locked in before you touch a fader, it saves more time than learning any single field does.

The XL Channel Strips: mixing without leaving what you're doing

On the left edge of the screen, next to the five mode icons, are the XL Channel Strips, and Akai's own manual is direct about what they're for: managing mixing tasks without needing to leave whatever mode you're already in. Tap the icons at the top of the condensed strips to show or hide them.

The left strip shows the currently selected track or pad. On a Drum track, tap the single-pad / four-squares icons in the bottom-right corner of the Track/Arrangement section to cycle between the track strip and the pad strip. On a Keygroup track, the same toggle uses a single-pad / keyboard icon pair instead. The right strip is dynamic, not a fixed second track. Select a send on the left strip and the right strip jumps to show that return. Show a track on the left and the right strip shows the main output. Show a pad on the left and the right strip shows that pad's parent track.

Both strip types share the same four views, and it's worth reading the exact wording because a few controls quietly disappear depending on what's selected:

The manual calls out one direct payoff of this design, and it's the whole reason the strips exist instead of just the full mixer modes: "This is useful for mixing your pads without having to enter the Pad Mixer." For a quick level nudge on one pad or one track, the strip is faster than either full mixer mode. For scanning eight channels at once, comparing sends across a whole session, or editing I/O routing in bulk, the full modes below are the better tool.

Opening the Channel Mixer and Pad Mixer

One hardware exception worth flagging plainly rather than glossing over: MPC X's own control-layout reference doesn't document this as one Mixer button with a Shift modifier at all. It lists two separate, dedicated buttons, Pad Mixer and Ch. Mixer, each opening its mode directly with a plain press, no Shift involved. Every other current standalone model documented in the manual uses the single Mixer button plus Shift pairing described in the table above. If you're on an X and hunting for a Shift-plus-Mixer combo that doesn't do what you expect, that's not a documentation gap, the X simply gave the Pad Mixer its own button instead of sharing one.

The Channel Mixer, tab by tab

The Channel Mixer works like a traditional mixing console: up to 8 tracks shown on the display at once, the track name at the top of each strip. Tap a track header to select it, drag left or right to see more tracks, and swipe left quickly to reach Submixes, Returns, and Outputs. The Settings icon in the lower-right corner opens the Mixer configuration screen, which is where the console-level behavior gets set: a Solo Button field (Solo Tracks or Cue Tracks), a Crossfader Profile field (Linear, Exponential, or Logarithmic), and MIDI/Audio Track Input Metering fields that decide when input meters are active (Always, When Record Armed, When Record Armed or Monitoring, or Never) and, for MIDI, whether meters reflect User Input alone or User Input and Playback. Double-tap any track header to jump straight to that track's Track Settings window.

The I/O tab's Monitor button behaves differently by track type, and this is the one place where a fourth option shows up that audio tracks simply don't get:

That contrast checks out against the manual's own text: Merge is documented only under "For MIDI tracks," with no equivalent line under "For Audio tracks" at all. Audio tracks stop at three states, MIDI tracks get a fourth that layers live input on top of played-back audio simultaneously, which is genuinely useful for a MIDI track feeding an external synth you want to hear both live and on playback without flipping a setting mid-session.

The Input and Output fields below the Monitor button also split by track type. Audio tracks get an Audio In field (a stereo pair like Input 1,2, or a single input) and an Audio Out field (a submix, a stereo output pair, or a single output). MIDI tracks get MIDI Input/Channel fields plus a Send To field that routes one track's MIDI output into another track, and MIDI Output/Channel fields on the output side.

The Pad Mixer, tab by tab

The Pad Mixer works, in Akai's own phrase, "just like the Channel Mixer" but scoped to pads: up to 8 pads shown on the display at once, the pad name at the top of each strip. Select a pad by tapping it on the hardware or tapping its channel strip header, and drag left or right to view more. The Settings icon here opens a different configuration screen than the Channel Mixer's, scoped to what's useful when you're staring at a bank of pads instead of tracks: a Filter by events checkbox (show only pads with events), a Filter by samples checkbox (show only pads with samples assigned), and a Write automation when recording checkbox.

Worth stating directly because it's a genuine, checkable difference and not just a formatting quirk: every Pad Mixer tab description stops at "Use the M and S buttons to mute and solo the pad." None of them mention an Automation button or a record-arm button the way every Channel Mixer tab past Volume does. That lines up exactly with what the Mixer Strips section already told us, Automation is "Not shown for Pad" and Record is "Not shown for Pad or Main Output" on the LVL strip view too. Automation and record-arm are sequence-level and track-level concepts. A pad doesn't get armed or written to on its own, the track it lives on does, so the Pad Mixer simply doesn't carry controls for either.

The Pad Mixer's I/O tab is the biggest real divergence from the Channel Mixer's, and it's worth being specific instead of assuming the two just share a layout with different labels. It's built entirely around a pad triggering something externally and where its audio goes, not around monitoring an input, because a pad doesn't have an audio input to monitor in the first place:

• MIDI Out Enabled. Never (no MIDI note sent), Always (a MIDI note fires every time the pad is triggered), or When Empty (a note only fires if the pad has no internal sample loaded). Built for triggering external gear, lighting, or video systems off a pad hit.
• MIDI Out Note. The specific MIDI note sent for the selected pad.
• MIDI Out Channel. The MIDI channel the output goes out on.
• Audio Out. Track routes the pad's audio into its parent track as normal, or you can send it directly to one of the outputs, bypassing the track.

Why Audio, MIDI, and Plugin tracks don't get a Pad Mixer

Akai's manual doesn't hedge on this one: "This mode is only available for Drum and Keygroup tracks." If you're on an Audio, MIDI, or Plugin track and the Pad Mixer menu entry looks greyed out or does nothing useful, that's the documented restriction working as intended, not a bug or a missing option you failed to find.

The logic tracks with what a Drum or Keygroup track actually is versus everything else. A Drum track maps individual samples to individual pads, sixteen (or a bank's worth) of separately triggerable one-shots, each with its own level worth mixing on its own. A Keygroup track maps samples across pads and zones the same structural way. Audio, MIDI, and Plugin tracks aren't built on a bank of individually assigned pads in that sense, an Audio track is a continuous recording, a MIDI track drives an external or plugin instrument as one channel, a Plugin track is one instrument instance. There's no per-pad sample bank on any of those three for a "pad" level of the mixer to have anything to act on, which is consistent with why the manual scopes the mode to exactly the two track types that do have one.

The Sends knob that does nothing, and how to fix it

This is the single most common way people waste time in either mixer, and Akai's own copy flags it directly, in nearly identical wording, on both the Channel Mixer's Sends tab and the Pad Mixer's Sends tab: load an effect onto the matching return first, or the send knob has nowhere to send audio to. Worth flagging the small difference between the two warnings honestly rather than treating them as identical: the Channel Mixer's version tells you exactly where to go next, swipe left to the Returns and select the Effects tab there. The Pad Mixer's version states the same requirement but doesn't repeat that navigation instruction, since the fix lives in the Channel Mixer either way, not inside the Pad Mixer itself.

Here's the actual fix, straight from the manual's own step list:

1. In the Channel Mixer, swipe left to show the Returns, between the Submixes and Main Outputs.
2. Tap the Effects tab at the bottom of the screen.
3. Tap an insert slot to open the effects window and load or edit an effect. You can also tap the Inserts button to open the Inserts window and load, change, or enable/disable effects there.

Set the return level the same way, swipe left to the Returns, but pick the Volume or Pan & Volume tab instead of Effects, tap the track that corresponds to the return you want, then use the level slider in the channel strip (double-tap for a larger version if you need finer control). Do that once per return you actually plan to use, and every Sends knob pointed at it, on any track or any pad, starts doing something audible instead of sitting there as a dead control.

Common mistakes

Mistake: turning up a Sends knob and hearing nothing. The return has no effect loaded yet. Load one on the Return's own Effects tab first, covered in full just above.

Mistake: opening the Pad Mixer on an Audio, MIDI, or Plugin track and expecting per-pad controls. That's the documented Drum/Keygroup-only restriction, not a missing menu item. Those three track types don't carry a per-pad sample bank for the mode to act on.

Mistake: hunting for an Automation or Record button on a Pad Mixer tab. Every Pad Mixer tab stops at M/S, mute and solo. Automation state and record-arm live at the track and sequence level, not the pad level, which is why the Channel Mixer's Pan & Volume, Sends, Effects, and I/O tabs carry both and the Pad Mixer's equivalents don't.

Mistake: expecting the Pad Mixer's I/O tab to show input monitoring like the Channel Mixer's does. It won't, because a pad has no input to monitor. That tab is built around MIDI-out triggering (Never/Always/When Empty, plus note and channel) and Audio Out routing (Track or direct to an output), output-side controls only.

Mistake: pressing Shift and Mixer on an MPC X expecting a toggle, and getting confused when it doesn't behave like other models. The X's own control reference gives Pad Mixer and Channel Mixer two separate dedicated buttons instead of one button with a Shift modifier. Every other current model uses the Shift pairing.

Mistake: opening a full mixer mode just to nudge one pad or one track's level. The XL Channel Strips on the left edge of the screen mirror whatever's currently selected and let you adjust level, pan, sends, and I/O without leaving the mode you're already working in. Akai's own tip calls this out directly for pads specifically.

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 worth flagging plainly: page numbers moved between manual revisions, content did not.

The Mixer Strips section sits at page 133 in the current v3.9 guide and page 128 in the older v3.7 guide. Channel Mixer sits at page 140 in v3.9 and page 135 in v3.7. Pad Mixer sits at page 145 in v3.9 and page 140 in v3.7. That's a flat 5-page shift across all three sections, consistent with the page-shift deltas already disclosed in prior articles on this site between these same two manual versions.

We checked the actual chapter text on both sides of that shift, not just the table of contents, and every paragraph we quoted above from the Channel Mixer and Pad Mixer chapters, the tab descriptions, the Sends caveat, the Settings-icon fields, the I/O behavior tables, reads word for word identical in v3.7 as it does in v3.9. The only difference we could find checking directly was pagination. That's the honest version of this claim: the mixer's own documentation hasn't changed in substance across these two releases, only where it sits in the printed page count.

Verdict: which screen for which job

Found a mixer quirk this didn't cover, or a model where a shortcut differs from what's documented here? Tell us what happened.