Slice to Drums: breaks on the 6.1 Sampler in an afternoon

From record crate to playable drum rack in one session: transient slicing, pitch discipline, Grid resequencing and a hardware dub tail, with the pitfalls flagged before they eat your evening.

The pitch of this piece is narrow on purpose: one break, one sampler, one afternoon, drums at the end. Everything below happens in Bitwig 6.1, whose Sampler rewrite (release notes here) finally makes slice-to-pattern a single sitting instead of a weekend project. If your break lives inside an old mix rather than on its own, spend the first coffee on UVR's v5.6 release

• the version still current since September 2023, whose download list carries a beta Roformer build - separate the drums first, because slicing a break that still has a bassline welded to it is how good kits get haunted.

1. Load the break and set the loop

Drop the drum stem into a new clip and find the bar that loops clean - first kicker to last pre-roll, not bar one to bar two because the software said so. Set Bitwig's tempo so the loop closes without a gap; if the break is from the vinyl era, a small fade at the seam beats a click every time.

2. Slice on transients, not on grid

Load the loop into the Sampler and set the Slicing Mode to Onsets, the mode that cuts at the sample's transients; an Onset Sensitivity control dials weaker onsets out of the pass. If the break is so mashed that even the transients have given up, the Beats and Divisions modes are the documented fallback - and they will reward you with a kit full of half-snare.ogg ghosts. Trust the Onsets pass first, audition the slices by clicking down the row, and clean up the edges by hand - manual slices are added and removed with a double-click in the waveform. The classic amateur tell is a kit with forty slices and three good ones. Aim for a dozen.

3. Map the kit, then murder the mapping

Convert the slices to a drum map - Convert to Drum Machine is one right-click away - and play them from a pad controller or a MIDI keyboard's low octave. Now the discipline: move every slice off its default pitch before you sequence anything. A resequenced break lives or dies on pitch memory - kick at its root, snare a fourth up, hats wherever they stop arguing - and the default chromatic layout guarantees your muscle memory builds the wrong song.

4. Resequence in the Grid

The 6.1 Sampler now exists as a Grid module, so the sliced break moves into Bitwig's modular rack without leaving the device: a step sequencer driving the Select trigger mode walks the slices, another modulator can chase the pitches, and the module's analysis outputs - onset, pitch, envelope - hand the rest of the patch signals derived from the sample itself. Keep the pattern at the break's native feel for the first eight bars: the old-school jungle move is not chaos, it is a bar of the original groove, then one ghost note added, then another. The moment every sixteenth has an event in it, stop, undo, and delete your favorite note. It will still be too busy.

5. Stretch only what must be stretched

If the tune needs the break faster than it was born, use the Spectral mode rather than the classic resample - with Preserve Onsets engaged, so the hits survive the stretch; the point is to move the tempo without embalming the cymbals. Keep a bounce of the unstretched loop on a muted track, because at 3 a.m. you will want to hear the original and admit which version you actually prefer. This is also the stage where a hardware comparison is honest: Hermetic Modular's Capicola does the same job in the rack, open source, and - assuming you already own the $389.99 module - patching a break through it before committing in the box takes five minutes and settles the argument your ears were having.

6. Dub the tail on hardware

Run the pattern through the effects that made the genre's tails famous. In software: Bitwig's stock delay chain will do. On hardware, jeffebauer's Resilio firmware turns a Versio into a spring reverb plus tape echo pair - feed it the snare only, sidechained by an envelope follower, so the snares trail dub and the kick stays dry enough to hit. Record the returns as stems, not as a stereo bounce; the tail belongs to the tune, not to the break.

7. Bounce, rename, close the session

Export the kit as a preset while the mapping is fresh - slice maps are the only assets that depreciate overnight - and write the break's source in the preset name. Future-you, digging for a kit at 2 a.m. before a set, will not remember that the good one was "new kit final 3."

Total elapsed time, for a first pass: about one session. The kit will not be your sound yet. The point of the afternoon is that the path from a record you love to a drum rack you play is now short enough to walk on a weeknight - and that the tools that matter, a slicer that reads transients, a separator that hands you the break, a stretch that does not punish the cymbals, are available today in versions you can run tonight: Bitwig 6.1 itself, UVR 5.6 (the Roformer build on its download list), and Bitwig's own Spectral stretch mode. Capicola is the exception on this list - a $389.99 shipping module, not a download - and Resilio, for all that its firmware runs tonight, wants a Noise Engineering Versio in the rack first.