FL Studio’s Cut and Cut By controls can make one instrument channel send a note-off command to another when it plays. Unlike Cut Itself, the relationship does not have to point both ways.
This matters when a beat uses two 808 channels rather than one sample pitched across a single Piano Roll. You might have a short, punchy 808 for one section and a longer, distorted version for another, or separate channels for bass hits that need different processing. Letting both tails run together can create a low-end pileup that note length alone will not prevent.
Cut Itself remains the simpler choice for keeping repeated 808 hits from overlapping on one Step Sequencer channel. Cut and Cut By become useful when the sound arriving on channel A needs to stop activity already playing on channel B.
Suppose the long 808 sits on channel B and should disappear whenever the short 808 on channel A hits. Set A’s Cut value to 1, then set B’s Cut By value to 1. You do not need to give B a Cut value unless B should also silence something else.
This one-way setup is useful when one sound has priority. A hard attack can replace a sustaining bass without allowing the long sound to cancel the next punchy hit. Assigning matching Cut and Cut By values to both channels instead creates mutual choking, where whichever channel triggers next stops the other.
Group numbers are only identifiers. Group 1 is not stronger or faster than group 2, and the number does not change volume, pitch, or timing. Problems usually come from giving unrelated channels the same group number and accidentally making them interact.
This makes cut groups useful for layered arrangements where separate Piano Rolls control different 808 sources. One channel can contain the main sub while another carries a processed accent, yet a trigger on the accent channel can still terminate the main sub before both occupy the same moment.
The cut is not literally a mixer mute. FL Studio sends note data that pushes the target instrument toward its release state, a behavior closer to MIDI note-off messaging than pulling down a channel fader. Plugins with long release envelopes may therefore remain audible after a cut command.
A lingering tail does not automatically mean the group numbers are wrong. Shorten the target instrument’s release when you need a hard transition, or keep some release when the small overlap sounds intentional. The important distinction is between a cut command being sent and the receiving instrument becoming silent immediately.
Use it when the routing works but the handoff itself sounds sharp or cracked. It is solving the boundary artifact, not deciding which channel wins the choke relationship. Changing cut-group numbers will not repair a click caused by the audio stopping too suddenly.
Routing mistakes are easier to diagnose with a deliberately simple test. Trigger channel B by itself and let it ring, then trigger channel A while B is still audible. If B moves into release, the directional group is working. If A also disappears when B plays, you have probably created a mutual relationship rather than the one-way setup you intended.
Plugin behavior can complicate the result further because Cut sends note information instead of silencing the Mixer track. A synth with a long release, internal effects, or delay may keep producing sound after its note has been released. Judge the cut at the instrument first, then decide whether any remaining tail comes from the source envelope or downstream effects.
This matters when a beat uses two 808 channels rather than one sample pitched across a single Piano Roll. You might have a short, punchy 808 for one section and a longer, distorted version for another, or separate channels for bass hits that need different processing. Letting both tails run together can create a low-end pileup that note length alone will not prevent.
Cut Itself remains the simpler choice for keeping repeated 808 hits from overlapping on one Step Sequencer channel. Cut and Cut By become useful when the sound arriving on channel A needs to stop activity already playing on channel B.
Cut and Cut By create a directional relationship
Think of Cut as the number a channel sends and Cut By as the number a channel listens for. If 808 A has Cut set to 1, any channel with Cut By set to 1 can be stopped when 808 A triggers. Leaving 808 A’s Cut By blank means 808 B cannot automatically return the favor.Suppose the long 808 sits on channel B and should disappear whenever the short 808 on channel A hits. Set A’s Cut value to 1, then set B’s Cut By value to 1. You do not need to give B a Cut value unless B should also silence something else.
This one-way setup is useful when one sound has priority. A hard attack can replace a sustaining bass without allowing the long sound to cancel the next punchy hit. Assigning matching Cut and Cut By values to both channels instead creates mutual choking, where whichever channel triggers next stops the other.
Group numbers are only identifiers. Group 1 is not stronger or faster than group 2, and the number does not change volume, pitch, or timing. Problems usually come from giving unrelated channels the same group number and accidentally making them interact.
Cut groups work with Piano Roll activity across channels
Same-channel Cut Itself has a limitation that catches many 808 programmers because it does not handle ordinary Piano Roll notes on that same channel. Cross-channel Cut and Cut By routing is different. Piano Roll activity from one channel can cut note activity on another channel when their group values match.This makes cut groups useful for layered arrangements where separate Piano Rolls control different 808 sources. One channel can contain the main sub while another carries a processed accent, yet a trigger on the accent channel can still terminate the main sub before both occupy the same moment.
The cut is not literally a mixer mute. FL Studio sends note data that pushes the target instrument toward its release state, a behavior closer to MIDI note-off messaging than pulling down a channel fader. Plugins with long release envelopes may therefore remain audible after a cut command.
A lingering tail does not automatically mean the group numbers are wrong. Shorten the target instrument’s release when you need a hard transition, or keep some release when the small overlap sounds intentional. The important distinction is between a cut command being sent and the receiving instrument becoming silent immediately.
Abrupt cuts can expose clicks and hidden routing mistakes
Cutting a waveform at an awkward point can produce a click, especially with bass material carrying a large low-frequency swing. FL Studio includes a Fast Declick for cut groups project option for Sampler channels, which changes their declicking behavior to reduce clicks when one sample stops another abruptly.Use it when the routing works but the handoff itself sounds sharp or cracked. It is solving the boundary artifact, not deciding which channel wins the choke relationship. Changing cut-group numbers will not repair a click caused by the audio stopping too suddenly.
Routing mistakes are easier to diagnose with a deliberately simple test. Trigger channel B by itself and let it ring, then trigger channel A while B is still audible. If B moves into release, the directional group is working. If A also disappears when B plays, you have probably created a mutual relationship rather than the one-way setup you intended.
Plugin behavior can complicate the result further because Cut sends note information instead of silencing the Mixer track. A synth with a long release, internal effects, or delay may keep producing sound after its note has been released. Judge the cut at the instrument first, then decide whether any remaining tail comes from the source envelope or downstream effects.
