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

FPC turns a folder of drum samples into one playable instrument. You don’t have to keep every kick, snare and hi-hat on separate Channel Rack rows. Instead, you build a pad layout, stack several samples on each pad, let velocity pick the right layer and send individual drums to their own Mixer tracks.

That makes FPC handy for two jobs: programming drums from the Piano roll and playing them from a pad controller. Setup gets much easier when you work in the right order. Build the sound first, decide how the layers respond, map the controller, then add choke groups and Mixer routing. Save last, because a preset only helps if it can still find its samples later.

This guide follows the controls documented in the Image-Line FPC manual. It lays out a reliable structure for building a kit, without pretending there’s one perfect velocity split or one universal MIDI layout.

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 doesn’t 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. If you mostly want fast step entry with independent channels, the Step Sequencer workflow may be all you need.

Start with a preset before building a kit from zero

Load FPC from the Channel Rack and start with one of its presets. That way you know the pad-to-note relationship, the Piano roll and the audio path all make sense before custom samples add more variables.

FPC has two banks of 16 pads, 32 pads in all. The selected pad is the one whose settings and layers you’re editing. The Layout control switches among three interface arrangements, including pad-bank views meant for touch screens.

The Pattern Manager holds percussion MIDI patterns. Pick one and it lands on the FPC channel as Piano roll data; pick another and it replaces the currently selected pattern. Treat these as raw material. Adjust the notes, velocities and timing to fit your track, because a preset groove won’t solve the arrangement for you.

A sensible five-minute orientation is:

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.

Build a custom FPC kit one drum family at a time

Don’t fill all 32 pads before you’ve checked the first few. 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. Select the first pad and load samples. Dragging several samples onto one FPC pad automatically creates layers.
3. Name the pad clearly. Names such as “Kick Tight,” “Snare Main” and “Hat Open” make routing and later troubleshooting faster than generic names.
4. Balance the layers. Different recordings rarely arrive at the same perceived level. Use layer volume so the transition from soft to hard feels intentional rather than like a sudden gain jump.
5. Repeat by drum family. Finish the kick layers before moving to the snare, then hats and percussion. This keeps problems local.

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.

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.

After loading velocity-related samples, click Spread Even. Image-Line documents it as dividing the available velocity range evenly among the layers without overlap, so four layers give you four zones from the lowest to the highest input velocity. It’s a clean starting point, not a finished musical rule.

Then move the boundaries by ear and by purpose. A snare may want a broad medium zone because most of its notes live there. A kick may only need a narrow hard layer for accents. Lock Layers links neighboring endpoints, so the ranges stay pressed against each other instead of drifting into accidental gaps or overlaps.

Leave Scale volume on in most kits, because incoming velocity still shapes the output level inside the layer structure. Image-Line notes you can switch it off when the velocity-sensitive layers already carry the whole dynamic change. I’d only do that on purpose; turning it off out of habit can make a kit feel flatter than you expect.

Separate layer overlap from round robin

Two different ideas often get mixed together 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. That’s useful when you deliberately want to blend a body sample with a transient or room layer. It isn’t round robin, though: every overlapping layer sounds on the same hit.

With Random layers on, overlapping layers can behave according to the selected randomization mode. Cycle is the documented round-robin option: FPC plays each layer in the group in turn. The Random modes choose among the group, with an option that avoids repeating the previous layer.

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

Don’t create variation by piling unrelated sounds into one group. Alternates should share a similar role, tuning and intensity. Otherwise the kit changes character at random instead of just 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.

FPC can learn one note for the selected pad, but Map notes for entire bank is faster for a 16-pad controller. Starting from the lower-left FPC pad, each incoming MIDI note is assigned to the next pad in sequence until the bank is mapped. Trigger the physical pads in the order you want them to appear.

After mapping, turn on Use current layout when changing presets if you want the controller layout to stay put when you load another kit. Without it, a preset can bring its own note layout along and make your hardware seem inconsistent.

Save the note layout separately if you use the same controller across several kits. The general MIDI controller mapping guide covers FL Studio input setup and broader controller links; FPC’s bank mapping 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 correctly and still stay silent if the active layer ranges leave a gap at that velocity.

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 carefully programmed pattern feels 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.

Keep choke groups narrow. A group should describe a real either-or relationship, such as open and closed hats or two articulations of the same percussion instrument. Reusing one number across unrelated cymbals and drums can cut off notes you meant to keep.

Route important pads to separate Mixer tracks

FPC’s Output control is an offset, not an absolute Mixer destination. It is calculated from the Mixer track assigned to the FPC channel.

Suppose FPC is routed to Mixer track 10:

• Output 0 reaches track 10.
• Output 1 reaches track 11.
• Output 2 reaches track 12.
• Output 3 reaches track 13.

This keeps the kit in one place while you process the kick, snare, hats or percussion groups on their own. A compact setup could send kick to Output 0, snare to 1, all hats to 2 and percussion to 3. You don’t need a separate output for every pad unless the mix actually calls for it.

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 is not proof that the preset is portable. FPC must be able to locate the source samples the next time the `.fst` file loads.

Image-Line’s documented saving sequence is straightforward:

1. Keep the kit samples in a folder visible under the Browser’s Extra search folders.
2. Open the plugin Wrapper menu and choose Save preset as.
3. Save the FPC kit as an `.fst` preset.
4. Reload the preset and confirm that its samples resolve correctly.

Use unique sample filenames. If several search folders contain a file called “Kick1.wav,” FPC can load the first match it finds. Descriptive names like “DustRoom_Kick_Hard_03.wav” clear up that ambiguity. Renaming files after the preset is built can break the lookup, so settle the folder and the names before the final save.

For an important kit, reload it in a fresh empty project before you rely on it anywhere else. You’re checking the saved file and its paths here, so there’s no need to copy the samples into random project folders.

FPC troubleshooting by symptom

A repeatable FPC setup order

The cleanest FPC workflow is short enough to remember:

1. Load a preset and confirm that FPC, the Piano roll and audio routing work.
2. Choose the pad layout and build a small core kit.
3. Drop related samples onto each pad and balance the layers.
4. Use Spread Even for initial velocity zones, then refine the boundaries.
5. Use deliberate overlap for stacking or Cycle for alternate takes.
6. Map the controller and preserve the current note layout.
7. Add CUT/BY groups for mutually exclusive articulations.
8. Assign only the Mixer offsets the mix needs.
9. Place samples in a stable Extra search folder with unique names.
10. Save the `.fst` preset and reload it to verify the dependency path.

FPC is one of the most practical instruments in the FL Studio stock-plugin set because it ties sound design, performance and mixing together without scattering the kit across unrelated channels. Get the pad behavior right before chasing a bigger layout; a predictable 16-pad core kit will usually serve you better than 32 pads you can’t predict.

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