Slicex in FL Studio: Chop Samples, Map Pads & Fix Clicks

To chop a loop in Slicex, load the audio, check its region markers, then use Dump score or MIDI notes to play the slices. The marker decides which audio belongs to a slice, and the note decides when that slice plays. Keep those two jobs apart, and fixing a clipped attack, an empty Piano roll or two hits that shouldn't overlap gets much easier.

I'd start with a short loop whose rhythm you can follow, and get a few regions playing cleanly before you move on to layers and envelopes. A busy break with dozens of markers makes a poor first test. You can change the wrong region and still hear something that sounds plausible.

What Slicex is and when to use it

Image-Line's Slicex guide describes an instrument that splits audio into playable regions. Its slicing and stretching features suit drum loops especially well, but you can chop a vocal phrase or an instrumental recording just as easily. Detection gives you a starting point; it cannot decide where a musical phrase should breathe.

The current edition matrix includes Slicex in Producer Edition and above, while Fruity Slicer and Fruity Slicer 2 come with every edition. Check which FL Studio edition includes the tools you need before you buy.

Using the standard Trial? You can save projects and export audio, but you cannot reopen a saved project until you purchase and unlock FL Studio. The plugins you use need licenses too, through your edition or a separate purchase where one exists. Keep the original FLP safe: reopening it and saving over it before trial plugins are unlocked can lose their saved settings. Until then, keep the work you need open, and don’t close a useful session just to run a save-and-reopen test. Image-Line explains the separate trial-plugin rules.

If you're still picking a sampling method, start with the broader FL Studio sampling walkthrough. For file cleanup, the Edison guide explains its workspace and the sample-editing tutorial covers trimming and repairs. Arrangement cuts belong in the Playlist guide. This page is about building a playable Slicex instrument.

Protect the source and find the right controls

Keep an untouched copy of the audio outside your working edits. Slicex lets you move markers and also process the waveform data itself, and those are different kinds of edit. Save a named project version before you experiment with destructive tools. Undo helps while you're editing, but it can't replace a saved copy of the source.

Think of the workspace as four places for four different problems. An edit doesn't have to pass through all of them:

• Master settings: global behavior, layering and automatic score dumping.
• Region controls and articulators: routing, cut groups and how a selected region responds to notes.
• Wave Editor: source audio, selections, markers and audio processing.
• Trigger-note mapping: which key or pad plays each region.

The Samples & Audio Editing hub connects this workflow to source preparation and repair. A marker problem usually gets fixed in the editor, while a wrong output destination never means cutting the sample again.

Chop and play a loop in nine steps

1. Keep the source. Retain the unedited audio and save a named working project.
2. Load Deck A. Drag your loop onto Slicex, deliberately targeting Deck B only if you need the second sample deck.
3. Audition the existing markers. Keep useful embedded regions; otherwise choose beat detection or grid slicing.
4. Check the grid when using it. Set the known beat count in Sample Properties and check the downbeat alignment.
5. Review the boundaries. Move a misplaced marker by its top tab, listening for the next attack and the preceding decay.
6. Repair only a real edge problem. Choose the appropriate declick operation; do not run every repair tool in sequence.
7. Create or assign notes. Use Dump score for a starting pattern, or assign trigger notes to your controller pads.
8. Test note playback. Check articulation, overlapping regions and Mixer destinations from notes, not only raw waveform audition.
9. Save and verify. Keep external source dependencies. Reopen a saved copy on a licensed installation; in the standard Trial, keep needed work open until purchase/unlock and export audio for reference.

Load a sample into the intended deck

Drag audio from the FL Studio Browser onto the Slicex channel or interface, or load it with the Wave Editor's file control. A normal import lands on Deck A unless you deliberately drop it onto Deck B. Each deck holds its own sample or loop, so Deck B isn't a backup of Deck A.

Watch where you let go of the file. Hold Shift while dragging and the audio gets appended; drop it onto a marker's name and it replaces that slice. Both are useful editing moves, but neither gives you a fresh sample. If something unexpected happens, stop and check the target before adding more markers.

Choose detection, grid slicing or manual markers

A file with embedded region data uses those regions and skips a new detection pass, so give them a listen before you throw them away. For fresh slicing, right-click the Wave Editor's Auto-slice button to open its presets. The Wave Editor reference treats beat detection and grid slicing as separate options.

• Beat detection: Dull finds fewer regions, Medium more and Sharp the most. Pick the result closest to the hits you want, rather than assuming the most sensitive setting is best.
• Grid slicing: Small, Medium and Large divisions follow the editor grid. Useful for deliberate rhythmic divisions; unhelpful if the grid does not match the recording.
• Manual boundaries: move the top tab of a marker and audition both neighboring regions. Preserve the intended attack or pickup, not merely the largest visible peak.

When you know the beat count, select that passage and open the Wave Editor's Format > Edit properties. Type the count into Sel (beats), the selection beat-count field, and check whether the grid lines up with the source. Check tempo and downbeat placement separately, because the spacing can be right and still start at the wrong point. The manual also documents a two-stage manual downbeat/grid gesture. A random drag doesn't detect tempo.

For a loose performance, keep the natural timing wherever it serves the phrase. You can rearrange notes later without forcing every source boundary onto an equal division.

Fix clicks without damaging the attack

Listen to the source first, then to the chopped version. If a region starts late, move its boundary before adding an attack envelope. When a tail goes missing, check whether the next marker cut it short. A quieter edge fixes neither problem.

Once the markers sit in the right place, pick the fix that matches the fault:

• Tools > Regions > Declick out all regions smooths region ends. It can be a better fit for drum attacks than processing both edges.
• Tools > Regions > Perfect all regions smooths starts and ends. Use it when both need attention, and check that a soft attack has not become duller.
• Tools > Time > Drum(loop) stretch is a separate option for already-cropped drum decays. It changes sample data; work on a protected copy and compare the result. It does not recover the original missing performance.

Each one fixes a different fault, and you never need all three in a row. A zero-crossing adjustment can reduce a discontinuity, but moving a boundary also shifts timing. After every change, judge the sound in the intended pattern.

A click that repeats at one particular boundary points to the slice. Crackle that changes with load, or turns up across unrelated instruments, means you should also run through the audio crackling diagnosis. Treat both as clues. Neither one proves a single cause.

Dump regions to the Piano roll

Dump score writes a note sequence that triggers the current regions. It doesn't render a WAV file. Once the basic mapping works, the Piano roll editing guide shows how to move, repeat or shorten notes.

The Master settings documentation limits Auto-dump to Deck A imports. For Deck B, press the Wave Editor's Dump score button yourself. If a new import keeps producing an unwanted sequence, check Auto-dump instead of deleting notes and importing again and again.

Right-click the Dump score button to get variations. Normal follows the loop's beat length at the current tempo. Reverse flips the order of the regions, but the audio inside each one still plays forward. Keep a normal sequence around for comparison before you try the variations.

Move a note onto another mapped key and it may trigger a different region instead of pitch-shifting the same audio. Check which chop a key plays before you treat a vertical note move as a melodic change.

Make note playback match your intention

Right-click a waveform region and you hear its raw audio without articulation. A key, Piano roll note or controller trigger plays it with articulation. That's why the raw slice can't confirm an envelope or output assignment. Test the real note pattern.

Play the whole slice or follow note length

To let the whole slice play out however long the key is held, the main manual specifies Vol - sustaining.fnv in the linked articulator's VOL/ENV mapping. Select the region, check its AMP articulator link and enable the envelope you want. It isn't a global switch that overrides every other playback setting.

Run script > Regions > Play to end is a separate option, and it has a documented limitation for low-tempo drum loops and fill-gaps. Don’t swap it in blindly when all you need is a region that ignores a short note length.

Assign regions to MIDI pads

In the editor's Regions menu, Assign trigger notes to all steps through the regions while you press the key or pad you want for each one. Try it on one region first, then work through the rest. Your controller's pad numbers might not match any particular default note range.

The Slicex keyboard panel previews and assigns regions, but it can't step-sequence. If the wrong deck or region sounds, check the real trigger assignment and the note color/channel in your current setup. Hold off on transposing the whole pattern until you know which mapping is wrong.

Typing keyboard priority gives editor shortcuts priority, so leave it off when you want typing-to-piano input for auditioning. For hardware setup and control assignments outside the plugin, use the MIDI controller mapping guide.

Route, choke and shape regions

The Articulation Panel reference keeps the selected region's output and cut group apart from its sound-shaping controls.

OUT is an offset. If Slicex's base Mixer destination is track 5 and the selected region has OUT set to 2, that region goes to track 7, not track 2. Play its assigned note and watch the destination before adding effects. The Mixer routing guide picks up from there.

CUT is a choke group. Triggering another region in the same group stops an earlier region that's still sounding. Test with an obvious overlap: if the first hit has already ended, there's nothing left to cut. This CUT control has nothing to do with the filter's cutoff parameter.

Articulators are shared. You can link eight modulation banks to region parameters, and changing a bank can affect every other region linked to it. For independent shaping, assign a different bank before you edit. Editing just the region selected on screen won't make a shared bank private.

For a volume envelope, link the region's AMP to an articulator, choose VOL and ENV, enable the envelope and audition some notes. Region FILTER, SPEED and START offer other changes, but leave them alone until you can name the result you're after. START has a limited range unless Sample start covers whole length is enabled. Changing speed isn't the same as changing project tempo.

Layer only when you want simultaneous regions

Several regions can share a trigger note, including regions on both decks. The All layering mode plays the assigned regions together, and its gain-compensated version lowers the combined level. Velocity-based layering can crossfade between co-assigned regions. Before you build the full pattern, check the combined sound at several velocities.

Layers and choke groups solve different problems. For two hits at once, look at layering. If a new hit should silence a ringing one, look at CUT.

Save the instrument and keep its audio

Keep the FLP as the editable version of the instrument and pattern. If another program needs the chops as files, the Wave Editor can export regions as WAVs named after their markers, and its sampler export can include middle-note metadata. Audio exports and the note sequence are separate deliverables, and sending either one won't rebuild every Slicex setting in another sampler.

The editor's drag/copy control sends the selection, or the whole sample if nothing is selected, to a compatible destination. Check the selection before you drag. When you're zoomed in, it's easy to mix up a highlighted region and the whole recording.

• Rename important regions and retain the untouched source.
• Check the note mapping, cut groups and actual Mixer outputs.
• Inspect Leave unedited audio data on disk: when enabled, that unedited data is not stored inside the project or preset. Keep the referenced file with the project's dependencies.
• Save a project version. On a licensed installation, reopen a saved copy and test it before archiving or moving the source files.
• In standard Trial, keep needed work open until purchase/unlock. Save the project for later and export a reference mix while it is available.

Lock audio data blocks further audio edits. It doesn't create a backup, and it doesn't prove that external files were collected. A successful test on the current machine helps, but once you move the project, you still need to check its dependencies at the destination.

Frequently asked questions

What is Slicex used for?

Slicex turns regions of audio into a playable instrument. Use it to trigger chops from notes or pads, rearrange a loop and control individual regions. If you only need one repaired file, an audio editor is the better tool.

Why is Deck B not creating Piano roll notes?

Auto-dump applies to Deck A imports. Select Deck B and use the Wave Editor's Dump score action explicitly. The result is a note sequence that triggers regions, not rendered audio.

Why does right-click preview sound different?

Right-clicking a waveform region plays raw audio without articulation. Notes from the keyboard, Piano roll or controller include articulation, so use notes to check envelopes and region output settings.

How do I play a whole slice from a short note?

Use Vol - sustaining.fnv in the linked articulator's VOL/ENV mapping and check that the intended envelope is enabled. The separate Play to end region script has limitations for low-tempo drum loops and fill-gaps.

How do I stop Slicex regions overlapping?

Put the regions in the same CUT group. A new trigger then stops an earlier region in that group if it is still sounding. Test with an overlap you can hear, and remember that filter cutoff is a completely different control.

Can I save and reopen Slicex in the Trial?

You can save the project and export audio in the standard FL Studio Trial, but you cannot reopen the saved project until you purchase and unlock FL Studio. The plugins also need valid licenses, through your edition or separate purchases where available. Do not overwrite the original FLP after reopening it with trial plugins still unavailable. Keep needed work open until then.

Eric Norris Nashville-based FL Studio producer and editor focused on practical workflow, mixer routing, troubleshooting, sampling and native Image-Line tools.