Short answer

Fruity Limiter is three tools in one: a limiter, a compressor and a noise gate. In Ableton Live they are three separate devices:

Convert now

2 free conversions every month. No card required.

When DAWPORT converts an FL Studio project, Fruity Limiter becomes a Live Limiter. If its compressor section is doing something, it becomes a Compressor followed by a Limiter. Both are labelled as approximations in the conversion notes.

One thing most people don't know

The LIMIT / COMP / NOISE GATE buttons only change which panel you see. In DAWPORT's FL Studio test renders, all sections stayed active whatever panel was on screen. A compressor you set up and then "left" by switching to LIMIT is still compressing.

So DAWPORT reads every section's settings and ignores which panel is showing.

How the controls correspond

Fruity Limiter Ableton Live How DAWPORT carries it
LIMIT: Gain Limiter Gain (or Compressor output gain when a compressor stage is added) Measured FL gain curve, converted to dB
LIMIT: Ceiling Limiter Ceiling Measured FL ceiling curve
LIMIT: Release, Sustain, release curve Limiter Release Measured timing law, up to 3000 ms
LIMIT: Attack Limiter Lookahead 3 ms, or 6 ms for slow FL attacks
COMP: Threshold Compressor Threshold Measured law, nudged by the Sustain setting
COMP: Ratio and Knee Compressor Ratio, Knee 3 dB Measured ratio law; FL's knee steepens the ratio
COMP: Attack / Release Compressor Attack / Release Measured timing tables
Sidechain input (another insert) Compressor sidechain from that track See the next section
Saturation — Must be at its default to convert
NOISE GATE — Not converted (see below)

The values are converted through curves measured from real FL Studio renders, instead of copying knob positions. A 50% knob in FL doesn't mean the same thing as a 50% knob in Live.

Sidechain: Fruity Limiter keyed from another track

This is the classic FL sidechain: a kick insert routed into a bass insert as a sidechain, with Fruity Limiter on the bass in COMP mode.

Since DAWPORT 1.0.72, when the compressor section is in use, this becomes:

Only the compressor section listens to the sidechain. DAWPORT's FL Studio renders showed the same thing in FL. If only the limiter section is in use, the sidechain has nothing to drive, so you get just the Limiter.

The conversion notes say which track triggers the ducking. In real Live renders of the converted sets, the ducking was usually within about 0.1 to 0.4 dB of FL on average, and up to about 1 dB at the deepest point of each duck.

Very deep or slow-releasing ducking can differ by about 1 to 2 dB on average, and the notes tell you when that applies. If the sidechain sound is wide or only in one speaker, Live ducks a little less.

The sidechain is not rebuilt when the source track:

In those cases DAWPORT leaves that Fruity Limiter out, and its settings stay in the conversion's recovery data.

For sidechain made with Fruity Peak Controller instead, see Fruity Peak Controller in Ableton.

How close it sounds

These numbers come from rendering the same settings in real FL Studio and real Live:

Without a sidechain, the notes say: "Limiting/compression is present; transient punch and release can differ slightly."

What DAWPORT does not convert

DAWPORT leaves a Fruity Limiter out (keeping its settings in the recovery data, and listing it as not converted in the notes) when any of these apply:

Ableton Limiter in FL Studio (the other direction)

Converting from Live to FL, Live's Limiter becomes Fruity Balance → Fruity Limiter:

Lookahead and auto release are not carried. Release is carried only in one narrow measured case (a standard 100 ms release); otherwise it is left out too. An automated Limiter is not converted.

FL's ceiling law was measured at 48 kHz. Live Sets usually don't store their sample rate, so DAWPORT assumes 48 kHz and says so in the report.

Tips for matching by hand

  1. In FL, check all three panels before you judge the sound. Another section may be active.
  2. In Live, put the Compressor before the Limiter, the same order FL uses inside one plug-in.
  3. Use Live's Limiter Lookahead at 3 ms as a starting point for FL's default attack.
  4. For sidechain, route the kick into Compressor's sidechain at Post FX and set the sidechain gain to match the kick's fader.

Related

Questions

What is the Ableton equivalent of Fruity Limiter?

Live's Limiter covers Fruity Limiter's LIMIT section. Live's Compressor covers its COMP section, and Live's Gate covers its NOISE GATE section. DAWPORT converts Fruity Limiter to Limiter, or to Compressor followed by Limiter when the compressor section is active.

Does sidechain compression from Fruity Limiter carry over to Ableton?

Yes, since DAWPORT 1.0.72. A Fruity Limiter keyed from another Mixer track, with its compressor section in use, becomes a Live Compressor whose sidechain listens to that track (Post FX, at that track's fader level), followed by a Limiter. It is labelled as an approximation.

Does the Fruity Limiter noise gate convert?

No. In real Live tests, Live's Gate did not follow FL's noise gate closely enough. If the noise gate is active, DAWPORT leaves that Fruity Limiter out and keeps its settings in the recovery data.

What happens to Ableton's Limiter when converting to FL Studio?

It becomes a Fruity Balance (for the input gain) followed by a Fruity Limiter (for the ceiling), as a labelled approximation. Lookahead and auto release are not carried, release is carried only in one narrow measured case, and an automated Limiter is not converted.

Convert now