FPC in FL Studio: Build and Play a Velocity-Layered Drum Kit

FPC is the pad drum sampler included in every FL Studio edition, with 32 pads in banks A and B. To build a kit, load the Empty preset, drop samples on each pad, click Spread Even for velocity layers or pick Cycle for alternate takes, then map your controller with Map notes for entire bank. Add CUT and BY groups for hi-hats, route FPC to its own Mixer track before setting Output offsets, and save the kit as an .fst preset with its samples in an Extra search folder.

FPC handles two jobs: drums programmed in the Piano roll and drums played from a pad controller. Setup goes fastest in a fixed order. Build the sound, set how the layers respond, map the controller, then add choke groups and Mixer routing. Save last, because a preset helps only when it finds its samples on the next load.

Every control name below matches the Image-Line FPC manual. Velocity splits and pad layouts depend on your samples and your controller, so the steps set a starting structure that you then tune by ear.

Image-Line's editions comparison lists FPC as included in all editions, so Fruity Edition has it too. More sound banks download from the Content Library inside the plugin, and the FL Studio editions guide covers what else changes between editions.

What FPC solves that separate Channel Rack samples do not

Separate sampler channels are quick when a pattern needs one kick, one snare and a couple of hats. FPC wins once the drums need to behave like one connected instrument.

• One pad can hold several samples. A light snare hit can trigger a soft layer while a hard hit reaches a brighter layer.
• Repeated notes can rotate through alternates. Cycle mode gives you round-robin variation instead of firing the same sample every time.
• Pads can interact. A closed hi-hat can stop an open hi-hat through CUT/BY groups.
• A controller layout can stay consistent. You can map a bank of 16 pads in sequence and preserve that note layout while changing presets.
• Drums can leave FPC through separate Mixer paths. Output offsets keep the kit in one instrument while giving important pieces their own processing.

FPC does not replace drum sequencing. You still build rhythms in the Piano roll or record a performance. If the pattern itself is the weak spot, start with the drum-pattern guide. For fast step entry with independent channels, the Step Sequencer workflow is the simpler route, and the FL Studio stock plugins guide lists the other instruments that ship with FL Studio.

Start with a preset before building a kit from zero

Load FPC from the Channel Rack and open one factory preset first, so the pad-to-note relationship, the Piano roll and the audio path make sense before your own samples add more variables. When the orientation is done, I start a new kit from the Empty preset, because its pads already sit on the General MIDI keys. Pick it in the plugin wrapper menu under Presets > Empty.

FPC has two banks of 16 pads, 32 in all, numbered from Pad 1 at the bottom left to Pad 16 at the top right. Left-click a pad to hear it and select it for editing. The height of the click sets the velocity: near the top plays soft, near the bottom plays hard. Right-click previews a pad without selecting it, and Ctrl+Right-click opens the Pad menu. The Layout control behind the gear icon switches among three views, and its Bank A and Bank A+B views are built for touch screens.

The Pattern Manager loads percussion MIDI loops onto the FPC channel as Piano roll data. Picking another loop replaces the selected pattern, so make a new pattern first when you want to keep the one you have. Treat the loops as raw material and edit the notes, velocities and timing to fit the track.

Your own MIDI drum loops can appear in the same menu. Open your personal FL Studio data folder in Windows Explorer or Finder, go to FL Studio > Presets > Scores, create a folder named FPC drumloops and put the MIDI loop files there. Subfolders keep a large collection organized.

A five-minute orientation with a factory preset:

1. Load a factory FPC preset.
2. Open the Pattern Manager and choose one short pattern.
3. Open the Piano roll and inspect which notes trigger which pads.
4. Change a few note velocities and listen for different responses.
5. Select pads in FPC and watch the pad and layer areas change.

Once that relationship makes sense, either adapt the preset or clear individual pads and start swapping in your own sounds.

Read the interface in three working zones

Most FPC confusion comes from changing the right kind of setting in the wrong place. It helps to read the plugin as three connected zones:

• Pad Matrix: chooses the drum or articulation you are editing.
• Main Pad Properties: controls pad-level behavior such as the MIDI note, name, volume scaling, CUT/BY group and Output offset.
• Layer Properties: controls the samples inside the selected pad, including their velocity ranges and playback behavior.

Think of a pad as the container and its layers as the contents. Renaming a pad or changing its MIDI note affects the container. Adjusting a waveform, layer volume or velocity range affects one sample inside it.

Each pad also has a Volume and a Pan envelope with ADSR controls. An envelope does nothing until you enable the LED at the bottom left of its editor, so check that LED first when a pad ignores its envelope settings.

Build a custom FPC kit one drum family at a time

Do not fill all 32 pads before the first few play well. Build a small core kit, make it playable, then grow it.

1. Choose a pad layout. Put the most-used drums where your hands or Piano roll habits expect them. A common core is kick, snare, closed hat, open hat, clap and one or two percussion sounds.
2. Load the samples for the first pad. In FL Studio 26.1 and later, drop several samples on one pad to add them as layers in a single move. In older builds, click Create to add an empty layer and Browse to load its sample, or drag one sample from the Browser onto the selected layer.
3. Name the pad. Right-click the Pad name box, or middle-click the pad for the name, icon and color pop-up. Names such as Kick Tight, Snare Main and Hat Open make routing and troubleshooting faster.
4. Balance the layers. Recordings arrive at different levels. Use each layer's volume knob so the step from soft to hard sounds like one drum played harder, not a sudden jump in gain.
5. Repeat by drum family. Finish the kick layers before moving to the snare, then hats and percussion. Problems stay local to one pad that way.

If your samples are scattered across temporary download folders, sort them out before building the kit. The sample-pack setup guide shows how to expose stable folders in the FL Studio Browser.

Three shortcuts speed up the build. Right-click a layer's sample view and choose Show in browser to open its folder, where F5 and F6 step through the neighboring samples and load each one into the selected layer. Drag a finished pad onto another to duplicate it, and a menu item swaps the selected pad with another to rearrange the grid.

Use velocity layers to change intensity, not merely volume

Velocity can do much more than turn the same sample up and down. A well-built pad uses different recordings for different playing strengths: a softer transient at low velocity, a fuller body in the middle and a sharper attack near the top.

I click Spread Even right after dropping velocity-related samples, because it splits the velocity range evenly among the layers with no overlap. Four layers give four zones from the lowest to the highest input velocity, a starting point for your ears, not a finished split.

Then move the boundaries by ear. A snare wants a broad middle zone when most of its notes land there, and a kick can get by with a narrow hard layer for accents. Lock Layers locks the end points of neighboring layers together, so the ranges cannot overlap and one sample plays at any given velocity.

I leave Scale volume on unless the layers carry the whole dynamic change, because with it on, incoming velocity still sets the level inside each layer.

Separate layer overlap from round robin

Two different ideas get mixed up in FPC:

• Velocity layering chooses a sample according to how softly or hard the note is played.
• Round robin rotates among alternate samples that belong to the same velocity area.

With Random layers off, overlapping layers play together. Use that to blend a body sample with a transient or room layer. It is not round robin, because every overlapping layer sounds on the same hit.

For round robin, turn Lock Layers off, overlap the alternate takes, turn Random layers on, then right-click its switch and choose Cycle in the FPC layer controls. I use Cycle only for alternate takes of the same hit, because it plays every layer in the velocity group in turn. The same right-click menu offers Random and Random (avoid previous), and the last one never plays the same layer twice in a row.

A practical snare pad uses three velocity bands. Each band holds two or three alternate recordings with overlapping ranges, and Cycle rotates through them within that band. Incoming velocity still decides soft, medium or hard, and the cycle changes only which equivalent take plays next.

Do not build variation by piling unrelated sounds into one group. Alternates should share a role, tuning and intensity, or the kit changes character at random instead of sounding less repetitive.

Map a MIDI controller after the kit responds correctly

Check the kit from the Piano roll or the onscreen pads before you map hardware. That keeps a kit problem separate from an input problem.

For a single pad, Learn assigns the next key you play and Last hit assigns the last key you played. I map a 16-pad controller with Map notes for entire bank, because one pass assigns every pad from the bottom left to the top right. Trigger the 16 physical pads in the order you want them in FPC. Changing a pad note, changing the pad or choosing Cancel Map notes in the Pad menu stops the pass.

Use current layout when changing presets keeps your pad layout when you load another kit. The FL Studio change log shows it on by default since version 20.9, so check that option first when a preset moves your pads around. With the (none) layout option, FPC follows the note layout saved in the song or preset instead.

Use Save note layout when the same controller serves several kits, and Load note layout brings that pad-to-note map back. The MIDI controller mapping guide covers FL Studio input setup and wider controller links, while bank mapping in FPC is the pad-to-note layer inside that setup.

If one pad refuses to respond, check the chain in this order:

1. Does FL Studio receive the controller at all?
2. Does the physical pad send the note you expect?
3. Is that note assigned to the intended FPC pad?
4. Does the selected pad contain an active sample layer for the played velocity?

That last check matters. A note can be mapped and still stay silent when the layer ranges leave a gap at that velocity. When the first check fails and FL Studio shows no input at all, start with the MIDI controller troubleshooting guide before changing anything in FPC.

Use CUT and BY for open and closed hi-hats

An open hi-hat should stop when a closed hi-hat arrives. If both keep ringing, even a tight pattern sounds disconnected.

FPC handles that relationship with two pad-level values:

• CUT places the selected pad in a cut group.
• BY tells FPC which cut group can stop the selected pad.

For a simple pair, give the closed-hat pad CUT 1 and the open-hat pad BY 1. The closed hat then cuts the open hat. If a pad should stop its own previous note, set its CUT and BY values to the same number.

I give each choke pair its own group number, because any pad in a CUT group stops every pad whose BY value names that group. Keep a group for a true either-or pair, such as open and closed hats or two strokes of the same percussion instrument, and set the values by left-clicking a box and dragging up or down. Reusing one number across unrelated cymbals and drums cuts off notes you meant to keep.

Route important pads to separate Mixer tracks

The Output control is an offset, not a fixed Mixer destination, and it counts from the Mixer track the FPC channel is assigned to. A new instrument channel starts on the Master track, as the Channel Settings page notes.

I route FPC to its own Mixer track before setting any Output offset, because every offset counts from that track. Choose Route to free mixer track in the wrapper menu or press Ctrl+L, as the plugin wrapper manual lists, or click the TRACK label in Channel Settings to take the next empty track.

Suppose FPC is routed to Mixer track 10:

• An offset of 1 reaches track 11.
• An offset of 2 reaches track 12.
• An offset of 3 reaches track 13.
• With the offset set to --, the pad stays on track 10.

This keeps the kit in one instrument while you process the kick, snare, hats or percussion on their own. A compact plan leaves the kick on the FPC track with --, sends the snare to offset 1, all hats to 2 and percussion to 3. You do not need a separate output for every pad, only for the pads that need their own processing.

Reserve enough consecutive Mixer tracks before you assign offsets, and name them. If FPC later moves from track 10 to track 20, every offset moves with it. That relative behavior is handy, and it also explains why a saved routing plan can seem to land on different track numbers after the base FPC channel is reassigned.

Use the Mixer routing guide for inserts, buses and sends after the pads reach their intended tracks.

Save the kit so FPC can find its samples again

A working session does not prove the preset is portable, because FPC has to find the source samples the next time the .fst file loads.

Samples dragged from Slicex or Edison onto FPC get saved as files. I set the Data folder before dragging slices from Slicex or Edison, because otherwise they land in the FL Studio installation folder. In Project General Settings, choose Store in the specified folder and point it at a kit folder that is also an Extra search folder. The Slicex guide covers the slicing side.

Save the kit in four steps:

1. Add the kit folder, including the Data folder from the step above, to the Browser's Extra search folders in the File settings page. FL Studio also searches their subfolders, and FPC looks for the kit samples there when the preset loads.
2. Open the plugin wrapper menu and choose Save preset as.
3. Save the kit as an .fst preset where you want to keep it.
4. Reload the preset and confirm that every sample loads.

I give every kit sample a unique file name, because FPC loads the first file with that name it finds in the Browser. Names such as Kick1 and Kick2 collide across packs, while a descriptive name like DustRoom_Kick_Hard_03 does not. FPC finds samples by file name, so settle the folder and the names before the final save.

I reload the saved kit in an empty project before using it anywhere else, because the reload shows whether FPC finds every sample through the Browser folders. If a sample is missing, fix the folder or the name and save the preset again. The missing samples guide covers the project-wide version of the problem.

The Export section of the FPC Options menu in Main Pad Properties offers more ways out. Save entire kit as pad presets writes each pad as a separate pad preset to share between kits, Save all wav files exports every sample the preset uses, and Export kit as SFZ file writes the kit in SFZ format. Save for FL Studio Mobile writes a monolithic .dwp file for the DirectWave sampler in FL Studio Mobile, and Import DirectWave program loads a .dwp program, not a bank, with only its first 32 zones. The DirectWave guide covers that sampler.

FPC troubleshooting by symptom

A repeatable FPC setup order

The cleanest FPC workflow is short enough to remember:

1. Orient with a factory preset. Confirm that FPC, the Piano roll and the audio path work together.
2. Start your kit from the Empty preset. Its pads already sit on the General MIDI keys.
3. Load and balance one drum family at a time. Drop related samples on a pad and level the layers.
4. Click Spread Even for velocity zones. Then move the boundaries by ear.
5. Choose overlap for stacking or Cycle for alternate takes. Turn Lock Layers off before overlapping ranges.
6. Map the controller with Map notes for entire bank. Keep Use current layout when changing presets on.
7. Add CUT and BY groups. Give each either-or pair its own number.
8. Route FPC to its own Mixer track. Then set Output offsets for the pads that need their own processing.
9. Set the Data folder and Extra search folders. Use unique sample file names.
10. Save the .fst preset and reload it. Open it in an empty project to confirm that every sample loads.

Mistakes that break an FPC kit

• Do not build all 32 pads first. Get a small core kit playing well, then grow it.
• Do not overlap layers by accident. With Lock Layers off and Random layers off, every overlapping layer plays on the same hit.
• Do not fill a Cycle group with unrelated sounds. Alternates should share a role, tuning and intensity.
• Do not set Output offsets before FPC has its own track. Offsets count from the track FPC is routed to, so moving FPC later moves every pad with it.
• Do not reuse one choke number for every cymbal. A shared group cuts notes you meant to keep.
• Do not reuse generic file names. FPC loads the first file with that name it finds in the Browser, so a Kick1 from another pack can replace yours.

Frequently asked questions

Is FPC included in every FL Studio edition?

Yes. Image-Line lists FPC as included in all editions, so Fruity Edition has it too.

How do you add several samples to one FPC pad?

In FL Studio 26.1 and later, drop several samples on the pad and FPC adds them as layers. Click Spread Even if they are velocity layers or set Cycle if they are alternate takes. In older builds, add layers with Create and load each sample with Browse.

How do you set up round robin in FPC?

Turn Lock Layers off, overlap the alternate takes in the same velocity range, turn Random layers on, then right-click its switch and choose Cycle.

How do you map a pad controller to FPC?

Choose Map notes for entire bank and hit the 16 physical pads in order. FPC assigns them from Pad 1 at the bottom left to Pad 16 at the top right. Use Learn or Last hit to map a single pad.

How do you stop an open hi-hat with a closed hi-hat?

Set the closed hat pad to CUT 1 and the open hat pad to BY 1. The closed hat then cuts the open hat. Setting CUT and BY to the same number makes a pad cut itself.

How do FPC Output offsets work?

The offset adds to the Mixer track FPC is routed to. With FPC on track 10, offset 2 sends a pad to track 12. Setting the offset to -- turns it off.

Why does an FPC kit load with missing samples?

FPC finds kit samples through the Browser Extra search folders. Put the samples in a folder listed there, give each file a unique name and reload the .fst preset to confirm.

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