Short answer
Fruity Convolver is FL Studio's convolution reverb: it plays your sound through an impulse response (IR), a short recording that captures how a room, hall, plate or speaker sounds. In Ableton Live, the device that can do the same is Hybrid Reverb, using its convolution section. Live's classic Reverb is algorithmic and can't load an IR.
2 free conversions every month. No card required.
When DAWPORT converts an FL Studio project, a Fruity Convolver with static settings becomes an Audio Effect Rack built around a Hybrid Reverb, with Utility devices for the levels and the stereo width. The impulse response has to be part of the upload.
How DAWPORT rebuilds it
Fruity Convolver does more than load an IR. Its editor can shape the IR with a volume envelope, an EQ curve, pre-delay and normalising. Hybrid Reverb has no editor like that. So DAWPORT does that shaping ahead of time:
- It reads the impulse response from your upload.
- It applies Fruity Convolver's normalising, volume envelope, pre-delay, self-convolution and (where used) EQ curve, using laws measured from real FL Studio renders.
- It saves the result as a new impulse response file in the converted project and loads it into Hybrid Reverb. Your original IR file is packaged with the project too.
Hybrid Reverb is then set to play only its convolution section, fully wet, with its own EQ, pre-delay, Vintage and Bass Mono off, so the prepared IR is what you hear.
How the controls correspond
| Fruity Convolver | Ableton Live (converted) | How DAWPORT carries it |
|---|---|---|
| Impulse response | Hybrid Reverb convolution IR | A prepared copy of the IR |
| Normalize | Built into the prepared IR | Measured FL normalising level |
| Volume envelope | Built into the prepared IR | Simple envelopes only (see below) |
| Pre-delay | Silence at the start of the prepared IR | At measured pre-delay settings |
| Self-convolution | Built into the prepared IR | Carried |
| EQ envelope | Built into the prepared IR | Approximation, labelled in the notes |
| Wet level | Utility gain in the Wet convolution chain | Measured FL level curve |
| Dry level | Utility gain in the Internal dry chain | Measured FL level curve |
| Mixer slot mix knob | Utility gain in the Host dry chain, and scales the other two | Linear crossfade, as in FL |
| Input stereo separation | Utility Width before Hybrid Reverb | Measured FL law |
| Wet stereo separation | Utility Width after Hybrid Reverb | Measured FL law |
| Stretch | — | Must be at its default to convert |
The dry chains also get a two-sample Align Delay. Hybrid Reverb's convolution output runs two samples behind a plain rack chain, and this keeps the dry and wet paths lined up.
What converts and what doesn't
Converted. A Fruity Convolver whose impulse response is available, with settings in the measured range, becomes the rack above. If its EQ envelope is in use, that EQ is applied to the prepared IR as an approximation, and the notes say it "may sound slightly different".
Left out, listed in the notes and kept in the recovery data, when:
- the impulse response wasn't uploaded. The note says the device "could not be reproduced because its impulse response was not uploaded", and suggests including the IR in a project archive.
- any of its controls are automated
- Stretch is moved from its default
- manual latency compensation is set
- the pan or stereo envelopes are not flat
- the volume envelope is more complex than a simple two- or three-point shape
- pre-delay is set to a value outside the measured settings
- the impulse response is extremely long
The rest of the project still converts.
Get the impulse response into your upload
FL Studio projects store the path to your IR, not always the audio itself. If you upload only the .flp file, the IR stays on your computer and DAWPORT can't use it. To include it, copy the IR into your project folder and upload the folder as a .zip, .rar or .7z archive. If you use FL Studio's zipped project package, check that the IR file is inside it. Upload limits: .flp and .als files up to 16 MB, or .zip, .rar and .7z archives up to 512 MB. See samples and missing media for the details.
What sounds the same, and what differs
Close:
- the space and the tail, because they come from the same impulse response
- the dry and wet balance and the stereo width, from measured FL laws
- the envelope and pre-delay shaping that is built into the prepared IR
Can differ:
- the tone when Fruity Convolver's EQ curve is used, which is labelled an approximation
- anything you change later in Hybrid Reverb, since the shaping now lives in the IR file
DAWPORT checked this setup on held-out test settings and by saving and reopening the converted Sets in Live 12.4.5. It is still a rebuild with a different device, so compare by ear.
Ableton Hybrid Reverb in FL Studio (the other direction)
DAWPORT doesn't convert Hybrid Reverb's convolution section to Fruity Convolver. Going from Ableton to FL Studio, a Hybrid Reverb that uses convolution is reported as not converted. A Hybrid Reverb that uses only its algorithm section, with the Dark Hall algorithm and a few other conditions, can become Fruity Reeverb 2. See Fruity Reeverb 2 in Ableton for that mapping.
Tips for matching by hand
- Drag the same IR file into Hybrid Reverb's convolution section and set the routing so only convolution is heard.
- Put Hybrid Reverb in an Audio Effect Rack with a dry chain if you want FL-style separate dry and wet levels.
- Rebuild Fruity Convolver's volume envelope with Hybrid Reverb's IR attack, decay and size controls, or render the shaped IR from FL Studio and load that.
- Use Utility's Width before or after the reverb to match FL's stereo separation.

