Sidechain ducking is in almost every electronic track: the bass or the pads dip each time the kick hits. FL Studio and Ableton Live both do it, but they wire it differently. That difference decides what a converter has to rebuild when a project moves between them.
2 free conversions every month. No card required.
This guide compares the methods, then lists what DAWPORT converts in each direction and what you rebuild by hand.
How each DAW does sidechain
FL Studio
FL Studio producers usually use one of three methods.
- Fruity Limiter keyed from another Mixer track. On the kick's Mixer track, you route it to the bass track as a sidechain ("Sidechain to this track"). Then, on the bass track's Fruity Limiter, the COMP section's SIDECHAIN selector picks the kick track (Image-Line manual). A sidechain route sends audio to the other track without it being heard there (Image-Line manual).
- Fruity Peak Controller. It sits on the kick track, follows the kick's level and is linked to another control, usually the bass track's volume fader. With a negative Volume, its output dips on each peak, which gives the ducking effect (Image-Line manual).
- Volume automation or a gain plug-in, drawn by hand in the shape of the duck.
Ableton Live
Live uses a device's own sidechain section. On Compressor, you enable Sidechain and choose a source track and tap point; Gain, Dry/Wet and a sidechain EQ shape what the detector hears (Ableton manual). Several Live devices have sidechain inputs, including Compressor, Glue Compressor, Multiband Dynamics and Auto Filter (Ableton manual).
So the same musical move is a routing setting plus a plug-in in FL Studio, and a source chooser inside a device in Live.
FL Studio to Ableton Live
| FL Studio method | In Ableton Live | Status |
|---|---|---|
| Fruity Limiter keyed from another Mixer track, compressor section in use | Compressor whose sidechain listens to the source track (Post FX), followed by Limiter | Approximation, since 1.0.72 |
| Fruity Limiter keyed, only the limiter section in use | Limiter only (the sidechain has nothing to drive) | Approximation |
| Fruity Peak Controller turning down another track's fader or a Fruity Balance volume | One or two sidechained Compressors on the ducked track | Approximation, since 1.0.72 |
| Peak Controller linked to anything else (a filter, a plug-in knob) | Not converted | Settings kept in recovery data |
| Fruity Compressor keyed from another track | Not converted | Listed in the notes |
| A sidechain route on its own, or into a third-party plug-in | Not carried | The route is not written to Live |
| Volume automation | Track volume automation | Converted |
Keyed Fruity Limiter
The new Compressor listens to the kick track at Post FX, with the kick's fader level as its sidechain gain, and the Limiter still listens to its own track, as in FL. In real Live renders, the result averaged 0.37 dB from FL Studio on 22 test states and 0.65 dB on 17 held-out states. Very deep or slow-releasing ducking gets an extra note, because it can differ more.
DAWPORT does not rebuild the sidechain when the source track is missing, is the same track, is muted, has automated volume, or would create a feedback loop. In those cases that Fruity Limiter is left out and listed. Details: Fruity Limiter in Ableton.
Fruity Peak Controller
Live's audio effects do not move another track's fader, so DAWPORT measures the duck Peak Controller makes and fits Live's own Compressor to it. It uses two Compressors in a row when one cannot follow a deep duck. Each link is checked on its own: the target must be a fader or a Fruity Balance volume on another track, driven only by this controller and not automated. An LFO-driven or automated controller is not converted. Details: Fruity Peak Controller in Ableton.
Expect the depth of the duck to be close and the recovery shape to differ a little. A compressor release is not the same shape as Peak Controller's fall. On very wide stereo sources, Live ducks slightly less, because its detector listens to both sides together.
Ableton Live to FL Studio
| Live method | In FL Studio | Status |
|---|---|---|
| Compressor with sidechain from another track | Fruity Compressor, keyed from a helper Mixer track named "Sidechain detector" | Approximation, supported cases |
| Glue Compressor with sidechain | Not converted | Listed in the notes |
| Multiband Dynamics or Auto Filter with an active sidechain | The device is not converted | Listed in the notes |
| Third-party plug-in with a sidechain input | The plug-in converts; its sidechain input is not connected | Rebuild the routing in FL Studio |
| Max for Live Shaper pumping a Utility's gain, in a specific rack setup | Mixer volume automation | Approximation |
| Volume automation | Mixer volume automation | Converted |
Compressor sidechain
The helper "Sidechain detector" Mixer track is fed by the key track, so Fruity Compressor reacts to the real kick at the level Live's sidechain heard. A sidechain high-pass filter is rebuilt on the helper track. A lookahead of 1 or 10 ms is reproduced by playing the helper track slightly early through FL Studio's delay compensation.
The supported case is narrow on purpose, because it was measured against real FL Studio renders:
- the Compressor sits directly on the track, not inside a rack, and is fully wet
- Peak mode with the Log envelope, Makeup and Auto release off
- the sidechain taps the key track at Post FX, with the sidechain mix fully up
- the sidechain EQ is off, or a single high-pass
- lookahead of 0, 1 or 10 ms
- no automation on the Compressor or on the key track's output
- the key track is unmuted, centred and has no track delay
Other cases are listed with a reason and left out. The notes also say where the result differs. Fruity Compressor follows the louder side of the key, while Live averages both sides, so a wide stereo key ducks somewhat more in FL Studio (mono kicks behave the same). With long releases, FL Studio recovers faster after a deep duck: about 1 to 3 dB shallower between hits on 20 to 35 dB ducks in real FL Studio tests. Details: Fruity Compressor and Live's Compressor.
Shaper pumping
Some Live producers duck with a Max for Live Shaper that moves a Utility's gain. When that sits in a simple Audio Effect Rack (just the Shaper and the Utility, tempo-synced, with no automation on them), DAWPORT turns it into an FL Studio Mixer volume automation clip on that track, as an approximation. Curve tension is followed with straight lines. Since 1.0.72, Live 12 Shaper racks are read the same way as Live 11 ones.
Tips for rebuilding sidechain by hand
- In Ableton Live: put a Compressor on the track that should duck, enable Sidechain and choose the kick track (Post FX hears the kick after its effects). Start with a fast attack and a high ratio, lower the threshold until the duck is deep enough, and set the release by ear against a bounce of your original.
- In FL Studio: on the kick's Mixer track, right-click the send switch to the bass track and choose "Sidechain to this track". Put Fruity Limiter on the bass track, open the COMP section and pick the kick track with the SIDECHAIN selector. Lower the threshold and raise the ratio until the bass dips on each kick.
Check after converting
- Read the conversion notes. They name the track that triggers each converted duck, and list any sidechain that was left out.
- Solo the kick and the ducked track together and compare with a bounce of the original.
- Sidechain into third-party plug-ins is not carried in either direction. Reconnect it in the destination DAW. Routing in general is covered in mixer routing between FL Studio and Ableton.
- Hand-drawn ducking follows the automation rules.
Ready to try it? Convert FL Studio to Ableton Live or Ableton Live to FL Studio.

