How to chop samples on an MPC: the complete Chop Mode guide

The short version

Chop Mode is a screen inside Sample Edit Mode, not a separate app, and it exists on every current standalone MPC: the One, Live, Live II, Key 61, Key 37, and X. Tap the Trim/Chop tab in the lower-left corner until it reads Chop, pick one of four slicing methods, Manual, Threshold, Regions, or BPM, and then run the result through the Convert or Assign Slices window to actually get the pieces onto pads as a real track. The whole process is non-destructive by default: your original sample survives every slice you cut, unless you specifically check a box that says otherwise.

The four modes aren't ranked, they're picked for the source material. Manual for anything you'd cut by ear, one hit at a time. Threshold for a loop with obvious hits and obvious gaps between them. Regions for a sample you just want divided into equal pieces regardless of what's in them. BPM for a loop where you already know the tempo and want the grid to do the counting for you. Pick the wrong one for the sample in front of you and you'll spend twenty minutes hand-fixing slice markers a different mode would have placed correctly on the first pass.

ENGINEER'S NOTE: Chop Mode and Trim Mode share one screen and one toggle button, and it's easy to build slices in Chop, flip to Trim to clean one up, and not notice you're still on the same sample. Check the Trim/Chop tab before you touch a Start or End field. One wrong edit on the wrong mode can move a boundary you spent real time placing.

Where Chop Mode actually lives

Chop Mode is not its own menu item. It's one of three views inside Sample Edit Mode, the other two being Trim Mode (crop the start and end only) and Pad Mode (assign samples to pads for keygroup programs). To get there, open the sample from your project's sample pool and tap Edit at the bottom of the screen. That opens Sample Edit Mode on that sample. From there, tap the Trim/Chop button in the lower-left corner so it reads Chop instead of Trim. That single tab is the entire path between recording or importing a sample and slicing it.

Once you're in Chop Mode, the Start and End fields (or the S and E markers you can drag directly on the waveform) set the boundaries of whichever slice is currently selected, and the first two columns of Q-Link knobs mirror those same two fields for hands-on adjustment.

The four chop modes, and when to use each

The mode selector sits in the lower-left corner of the Chop screen. All four options build slices out of the same sample, they just decide where the slice boundaries land in completely different ways.

Manual is exactly what it sounds like: you place slices yourself, either by tapping Slice+ at the current playhead position, or by pressing an unlit pad during playback to drop a marker at that exact point. It's slower than the other three, but it's the only mode that guarantees a slice boundary lands exactly where your ear says it should, which matters on anything with inconsistent spacing, a vocal chop, a live-played loop, a field recording.

Threshold runs an adjustable detection algorithm that derives the slice count from volume levels in the sample. The Threshold field sets the sensitivity, higher values create more slices, and the Min Time field sets the minimum length a slice is allowed to be, so quiet sustain or reverb tails don't get chopped into slivers. It's the fastest mode for drum loops and breaks where individual hits have real silence between them. It gets messy on anything already compressed flat or dense, since there's no volume dip left for the algorithm to key off of.

Regions ignores the audio content entirely and divides the sample into however many equal-length pieces you set in the Regions field. Reach for it when you want a grid of even pieces and don't need them to line up with individual hits, a texture bed, a pad you're going to scrub through live, a long ambient sample you're turning into a wavetable of sorts.

BPM divides the sample based on tempo: how many bars are in it, how many beats per bar, and a Time Div note value (1/4, 1/8, 1/16, or 1/32) that decides where the actual slice markers land within that grid. The manual's own guidance is that 1/16 is the right setting in most cases. This is the mode for a drum break or a loop where you already know the BPM, since it puts a slice on every subdivision instead of guessing from volume.

Playing, selecting, and cleaning up slices

Once slices exist, you play a slice by pressing the pad it's mapped to, banking over if the sample has more than sixteen. With One Shot enabled, one press plays the full slice, with it disabled, the pad plays only while held. To edit a different slice, use the Slice field, the fourth Q-Link knob column, or, if the headphones icon in the upper-right is selected, just tap the slice directly in the waveform.

Two slices too many, or too few, can be fixed without redoing the whole pass. Tap the glue-and-scissors icon to open Split/Combine: Split cuts the selected slice into two equal halves, Combine merges it with the one before it. To start over completely, hold Shift and tap Clear All.

Two settings decide whether your slices behave and sound clean. Link Slices, on by default, means moving a slice's start point also moves the end point of the slice before it, which is exactly what you want for a contiguous chop, but it has to be turned off if you need slices that skip around the sample or overlap on purpose. 0 Snap forces every start and end point onto the waveform's actual zero crossings, which is the single biggest lever for killing clicks and pops at a slice boundary. Hold Shift and tap 0 Snap at the bottom of the screen to toggle it. If a chopped loop is popping on every hit, 0 Snap is almost always the fix, check it before you start hand-nudging boundaries by ear.

Turning slices into a track you can play

Slices sitting in Chop Mode aren't a track yet, they're markers on one sample. To get them onto pads where you can actually sequence and perform them, hold Shift and tap Convert to open the Convert or Assign Slices window, then choose what the Convert To field builds. There are six options, and they are not interchangeable, three create a full new track, two assign to a single pad, and one builds a tempo-synced phrase.

For most beats, New drum track using slices is the option to actually use. It builds a new track and points each pad straight at a slice number instead of creating separate sample files, which keeps your project smaller and keeps every pad referencing the same source audio. Check Create Events while you're in that window and the machine will also auto-build a sequence that plays each pad's slice in ascending order, which is a fast way to hear the whole chop back to front before you start rearranging it.

Create New Samples is the move when you specifically want standalone files, printing stems for another project, or handing slices off outside the MPC. Just know the Crop Samples box inside that same window deletes the unused parts of each new sample once it's created, that's flagged as destructive in the manual itself, though your original source sample is untouched either way.

Common mistakes and quick fixes

Mistake: assigning a slice to a pad you thought was empty. Assign Slice to Pad and New Sample to Pad both replace whatever is already on that pad's first layer, the manual states this as an explicit warning on both options. Check the pad before you commit, or use New drum track using slices instead, which builds a fresh track rather than overwriting one.

Mistake: dragging one slice boundary and watching a different one move too. That's Link Slices doing exactly what it's designed to do, keep adjacent slices contiguous. It's correct behavior for a straight chop, but it has to be turned off before you can build non-sequential or overlapping slices on purpose.

Mistake: Threshold mode returning either one giant slice or a hundred tiny ones. That's the Threshold and Min Time fields fighting each other. Raise Threshold if the algorithm isn't catching enough hits, raise Min Time if it's catching too many and slicing up silence or tails into slivers.

Mistake: clicks or pops at the start of every slice. Turn on 0 Snap before you touch anything else. It forces start and end points onto actual zero crossings in the waveform, which is the documented fix for exactly this.

Mistake: checking Crop Samples or Crop Sample because it sounds like a safe cleanup option. It isn't destructive to your original sample, but it is destructive to the new copies it creates, deleting the unused parts permanently once you tap Do It. Leave it unchecked if you might want the full sample back later.

A note on manual versions

Rule two on this site is that conflicts between sources get stated, not quietly resolved, so here's one worth flagging. A quick-reference summary of this topic that circulated recently cited pages 272 to 275 of the MPC Standalone OS v3.7 User Guide for the Chop Mode walkthrough. Checked against an actual copy of v3.7, that citation holds up, Chop Mode does start on page 272 in that build, and Converting or Assigning Slices does start on page 275.

The manual on file for this article is the newer v3.9 User Guide, and in that build the same section runs pages 282 through 288, a ten-page shift from v3.7. Content immediately before Chop Mode in v3.9 covers Akai's Stems feature, which is one likely source of the added page count between versions, though this article isn't claiming to have confirmed every change in between. What matters for chopping: the menu path, the four mode names, the field names, and the Convert or Assign Slices options are worded identically in both manuals wherever this article checked them side by side. Only the page numbers moved. If you're following along in an older printed copy or a different PDF, check your version number before hunting for a page that doesn't match what's printed here.

Verdict: which mode, which convert option

Run into a Chop Mode quirk this didn't cover? Tell us what happened.