Reverb and Delay Sends in FL Studio: Clean Routing

Your vocal needs space, but every notch of reverb makes the words a little harder to follow. Reverb and delay sends in FL Studio solve that: the direct sound stays on its main route, and the effect lives on its own adjustable path. You'll use two Mixer tracks as returns, make their effects wet-only, and feed them from each source with the routing knobs.

Here's the one distinction worth keeping in your head. A source send changes how much one track contributes; a return fader changes the whole shared effect. Normal Mixer sends follow the source fader, and Fruity Send gives you another option when the copy has to leave earlier in the effects chain.

Build reverb and delay sends in eight steps

1. Choose the returns. Pick two unused Mixer tracks and name them Reverb and Delay. Keep playback stopped while you set up routes you haven't built before.
2. Keep the main paths. Confirm both returns feed the Master. Leave the source's existing main route alone, whether it goes straight to Master or through its intended bus.
3. Load the effects. Put Fruity Reeverb 2 on Reverb and Fruity Delay 3 on Delay. Leave each effect slot's Mix at 100% and its effect enabled.
4. Remove duplicate dry audio. Set Reeverb 2 DRY to 0% and WET to 100%, with ER adjusted to taste. Set Delay 3 output Dry to 0 and make sure its input Wet and output Wet are raised enough to pass echoes.
5. Connect one source. Select its Mixer track by the label. Left-click the routing switch beneath the return you want to feed; this creates a normal audible send. Avoid any route that removes the source's main path.
6. Set the feed cautiously. Check the new send knob before you press play; don't assume it starts at zero. Begin with a low send and a low return level, then bring them up while you listen.
7. Balance the shared effect. Use the source send for that source's amount and the return fader for the combined effect. Add other sources only when they need the same room or echo.
8. Check the result. Mute the return track for a moment to hear what it adds, then bring it back. Listen for dry clarity, tails, feedback, the final output and any automation across the full phrase.

Insert, bus or send: follow the audio

An insert effect sits in one track's processing path. A group bus becomes a shared main path for several tracks. A send return adds a parallel path: the source keeps going to its normal destination while a copy runs through the effect.

There's no special return-track type to hunt for. An ordinary Mixer Insert does the job. The Mixer routing guide explains the wider layout; for now, keep one simple test in mind. Muting Reverb should take away its contribution without silencing the direct vocal.

Create and connect the return tracks

Rename the two empty tracks before you build any links: Right-click track label → Rename / color. Load each plugin from an empty effect-slot menu, then click its loaded name to open the controls. Clear names make it much easier to tell destinations apart when you come back to a source later.

The Image-Line Mixer reference places the routing controls beneath the destination tracks. Select the source, then click the switch under Reverb, and a level control appears for that connection. Repeat under Delay. When you select another source, you're looking at that source's routing, not a global reverb amount.

Keep the source's main route. A sidechain-only link doesn't give the reverb ordinary audible input on its own, and an exclusive route can remove a path you meant to keep. Neither one is the normal parallel-send setup described above. Both returns should reach the Master without feeding back into their sources.

Make Fruity Reeverb 2 wet-only

On the Reverb return, set DRY: 0% and WET: 100%. Those are the send settings in the Fruity Reeverb 2 manual. ER is a separate early-reflection level; adjust it for the character you want rather than treating it as another dry control.

DRY at zero removes the original from this plugin's output only. The source track's main route still carries it. WET controls the reverberant part, and the source send plus the return fader decide how much of that shared space joins the mix.

If a centered or mono source produces very little reverb, check the MID/SIDE selector as well as the levels. SIDE processing needs stereo difference in the input, so it won't act as a universal wider-reverb switch. Start with MID for this basic routing exercise, then choose a mode on purpose.

Separate Delay 3's input and output levels

Fruity Delay 3 has three relevant level controls, not one mix knob. Input Wet feeds its processing; output Wet sets the processed output; output Dry passes the original. Set Output Dry: 0 on this return, and check that both Wet controls are open enough to hear the effect. These roles are documented in the Delay 3 parameter reference.

Turn on Tempo Sync when the echoes should follow the project. With sync selected, Right-click Time → Set offers musical timing choices. Listen for the gaps between phrases instead of treating one note value as the rule. Check the delay model too: Off removes delay while leaving other processing available.

Feedback Level sends echo back into the process. It can go past 100%, and filter resonance can raise overall feedback even below that setting. Keep the feed low while you choose it. If the return starts building out of control, mute the return first, reduce Feedback and resonance, then carefully start listening again.

Check slot Mix before blaming the routing

There are two wet/dry layers here. The plugin has its own controls, and the Mixer effect slot has a Mix knob. Keep the reverb or delay slot at Mix: 100% for a wet-only return, then remove the dry signal inside the plugin. Slot Mix at 100% alone does not make a plugin wet-only, and lowering it can blend unprocessed slot input back into the return.

The Effects Slots manual also explains why bypass can surprise you: disabling an effect does not stop audio passing through its slot. Bypassing the only reverb on a return can therefore expose a second dry copy. To compare the mix with and without that return, mute the return track rather than disabling its effect or the track's whole FX stack.

Run the same check after loading a preset. A preset won't necessarily keep the wet-only settings you just made. If the vocal suddenly sounds louder after a preset change, suspect a dry-routing change before you credit better ambience.

Choose the right level control

If only the lead vocal has too much delay, lower the lead-to-Delay send. If everything has too much delay, lower the Delay return fader. Those two moves touch different parts of the mix. The vocal mixing workflow helps with the direct chain, and this parallel routing should support its clarity.

A shared return also means shared timing, tone and processing. That's useful when several sources should sit in the same space. Create another return when a part really needs a different decay, rhythm or automated treatment. Two returns is a teaching setup, not a limit.

Why does the effect change with the source fader?

Normal Mixer sends take audio after the source effects stack and fader. Pull that fader down and you reduce both the direct sound and the new audio feeding the return. A reverb tail or delay repeat already inside the effect can keep going; a quieter input doesn't empty the plugin.

So a source's feed follows its balance, but the perceived dry/wet ratio won't always stay identical. Existing tails and level-dependent processing complicate that relationship. Re-check the effects after big fader rides, and use the gain-staging walkthrough if you need to trace a level change.

Use Fruity Send for a pre-fader copy

Reach for Fruity Send when later source-fader moves shouldn't change the feed, or when the copy needs to leave before a particular effect. Its slot position decides which earlier processors are included. Pre-fader doesn't mean independent of every upstream volume change.

The Fruity Send manual gives this setup:

1. Select the source Mixer track. Right-click the destination return's routing control and choose Sidechain to this track, keeping the source's main route intact.
2. Load Fruity Send at the intended point in the source effects stack.
3. Right-click its Send to selector and choose the linked return.
4. Set Fruity Send Dry: 100% when the source must continue through later slots and its fader. Its default Dry is 0%, which can silence that onward path.
5. Raise Fruity Send's Volume cautiously to feed the return. Leave the ordinary Mixer send at zero so an additional post-fader copy does not join it.

Use a separate Fruity Send instance for each additional destination, and keep pass-through enabled in each one when you want the main source path preserved. Image-Line blocks this plugin on the Master and prevents feedback-loop sends, so don't try to route the return back to its source.

The sidechain link here simply makes the destination available to Fruity Send. It won't duck anything like a compressor would. If you want a vocal to turn down a reverb while the words are present, follow the separate sidechain compression workflow.

Automate one word, not every source

For a delay throw, select the source, right-click its send knob and choose Create automation clip. Keep the send at zero before the chosen word, raise it over that word, and bring it back to zero afterward. Play through the transition: zero stops new feed but won't necessarily cut the echoes already in flight. Leave a small baseline send only if you also want quieter echoes on the surrounding words.

Native control automation and Playlist range behavior are described in the Automation Clip documentation. The automation editing guide covers shaping and troubleshooting the clip. Check the start-of-song value too; creating an Automation Clip initializes the control's current value.

Delay 3 input Wet is another feed control, but on a shared return it affects every source entering that plugin. The return fader affects the combined audible return, existing tails included. Automate the source send when one source needs the move; give a source its own return if its whole effect needs separate movement.

Process and audition the wet path

EQ after the reverb shapes its output; EQ before it shapes its input. With delay, an external EQ after the plugin isn't the same as Delay 3's feedback filter, which works on the echoes every loop. Pick the location that addresses the problem, then use the Parametric EQ 2 controls guide to make the filter change.

Compression after the effect controls the combined return. Compression before it changes the feed, not the echoes already circulating inside the plugin. If you add a compressor, compare the timing with the Fruity Limiter guide. One loud source can make a shared processor react to the whole return.

To hear the wet sound alone in this simple direct-to-Master example, temporarily disconnect the source's direct Master route while leaving its send active. Don't mute the source or pull down its post-fader level, because that also changes the feed you're trying to hear. Restore the original direct route right afterward. If the source reaches Master through a bus, find that dry branch instead of disconnecting tracks blindly.

Reeverb 2 SEP changes the wet stereo signal. Delay 3 Ping pong alternates stereo channels; a mono input needs its Pan adjusted to create that bouncing effect. Check the stereo separation options and perform a mono compatibility check before keeping an impressive solo sound that weakens in the mix.

Keep tails and output under control

Several sends can stack up more level than one. A high internal Insert meter isn't automatically clipped audio, since FL Studio's floating-point path has headroom. Plugins can still distort, though, and hardware output or fixed-depth export can clip. The official level guidance separates these cases. If you hear distortion you don't want, find the first bad stage with the clipping diagnosis instead of hiding it later.

Listen after the last note as well as during the chorus. In export settings, Tail → Leave remainder extends the render for decays, while Cut remainder cuts at the chosen endpoint. The render Tail documentation explains the options. Check the actual file through the song export workflow; picking an option doesn't prove the whole tail survived.

Troubleshoot one path at a time

• No effect: check the selected source, normal audible link, send level, plugin enable state, both wet levels where applicable, return fader and route to Master. A sidechain-only link is not the normal reverb input.
• Unexpected dry or louder sound: check plugin Dry, slot Mix and effect bypass before changing the source balance.
• Pre-fader source disappears: inspect Fruity Send Dry pass-through and the source's main route.
• Delay feeds every phrase: check which control the automation targets. Input Wet on a shared return is not a per-source selector.
• No distinct repeats: check Delay Model Off, input/output Wet, Time, Feedback and whether diffusion is smearing the echoes.
• Reverb disappears on a mono source: inspect Reeverb 2 SIDE mode before adding gain.
• Feedback grows: mute the return to stop listening to the buildup, reduce Feedback and resonance, and restart at a low level.
• Mix washes out: reduce the relevant send, shorten the effect or change its tone. Use the return fader when the whole shared effect needs less level.

You're done when the direct parts are easy to understand, the effect is audible where it belongs, and the tails you wanted are intact. The Mixing library connects the next processing decisions. If basic track setup is still getting in the way, go back to Start here before adding more routes.

FL Studio reverb and delay send FAQ

How do I create a reverb send in FL Studio?

Use an empty Mixer track as a Reverb return, load Reeverb 2, set DRY to 0% and WET to 100%, and leave slot Mix at 100%. Keep the return routed to Master and the source's main path intact, then create a normal audible source-to-return send and raise it cautiously.

Should a reverb send be 100% wet?

For this parallel setup, keep dry audio out of the return. In Reeverb 2 use DRY 0% and WET 100%, with ER adjusted separately. Leave the Mixer effect-slot Mix at 100%, then balance the effect with source sends and the return fader.

Which Dry control should I turn down in Delay 3?

Set output Dry to zero. Input Wet feeds the effect and output Wet controls processed output; both must allow enough signal through to hear echoes. Keep the effect slot enabled with Mix at 100%.

Are normal FL Studio sends pre-fader or post-fader?

Normal Mixer sends are post-fader. Fruity Send extracts a copy from its position in the source effects stack, before the source fader. Earlier effects and upstream level changes can still affect that copy.

Why does lowering the source also lower its reverb?

The normal send follows the source fader, so it receives less new input. A tail that's already inside the reverb can carry on. Use Fruity Send if the feed specifically needs to be independent of that later fader.

Why is the return adding dry sound?

Check the plugin's Dry control, the slot Mix and whether the effect is bypassed. A bypassed slot still passes audio. Mute the return track when comparing its contribution, instead of bypassing the only wet effect.

How do I automate a delay throw for one vocal word?

Automate that source's send knob up over the word and back down afterward. Existing echoes can continue. Delay 3 input Wet can also control feed, but on a shared return it affects all sources entering the plugin.

How can I hear only the wet return?

In a simple direct-to-Master layout, temporarily remove the source's direct Master route while leaving its send active, then restore the route after listening. Muting the source or lowering its normal post-fader level also changes the feed.

Why did Fruity Send silence my source track?

Its Dry control defaults to 0%, blocking onward pass-through. Set Dry to 100% when the original must continue through later slots and the source fader, and confirm its main route remains connected.

Should EQ go before or after the return effect?

Before the effect, EQ changes what goes in; after it, EQ shapes what comes out. That's different from a delay's internal feedback filter, which acts on each loop. Choose the position that fixes the masking or tone problem you actually hear.

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