Automation is often what makes a track move: filter sweeps, volume rides, tempo changes, effect throws. It is also one of the hardest parts to move between DAWs, because FL Studio and Ableton Live store it in different ways.

Convert now

2 free conversions every month. No card required.

This guide explains what DAWPORT carries over in each direction, where it approximates, and what you may need to redraw. It only lists behaviour that the conversion engine actually implements.

How each DAW stores automation

FL Studio mostly uses automation clips. An automation clip is its own item on the Playlist, linked to a control such as a mixer fader or a plug-in knob (Image-Line manual). FL Studio can also record automation as event data inside a pattern (Image-Line manual).

Ableton Live draws automation as envelopes on the track that owns the control, in the Arrangement. Clips can also carry their own clip envelopes (Ableton manual).

So converting automation means finding the matching control in the other DAW and redrawing the movement there. DAWPORT only writes automation when it knows the destination control and how its values line up.

FL Studio to Ableton Live

Supported FL Studio automation clips become Ableton Live arrangement automation on the matching control.

What the clip controls In Ableton Live
Tempo Song tempo automation
Mixer track volume and pan, including the master Track volume and pan automation
Audio clip gain Clip gain automation
Third-party VST2/VST3 plug-in parameters and on/off The same plug-in parameter, when the plug-in and its settings carried over
Channel volume The gain of a Utility placed after the instrument, when that gain stage is created
Some converted stock effects The matching control on the Live device (see below)

For converted stock effects, supported controls include on/off, gain and pan on a gain device, filter cutoff, Fruity Parametric EQ 2 band settings on its EQ Eight approximation, and the level controls of converted reverbs and delays. Where the device itself is an approximation, its automation is an approximation too, and the conversion notes say so. See stock effect equivalents for the device mappings.

Timing and curves

Several clips on one control

FL Studio lets more than one automation clip control the same knob. Since version 1.0.72, DAWPORT joins them into one curve the way FL Studio plays them: a newer clip takes over, the value holds between clips, and a clip that is not placed in the Playlist never plays, so it is left out and noted. This is currently used for the Fruity Parametric EQ 2, reverb and delay approximations. Where clips on different Playlist tracks overlap, FL Studio itself does not always follow the newer clip, and the conversion notes say those passages can differ. In other cases, several clips on one control are reported rather than guessed.

Not converted yet

Ableton Live to FL Studio

Arrangement automation becomes FL Studio automation clips on the matching control.

What the envelope controls In FL Studio
Track volume and pan Mixer track volume and pan
Tempo (10 to 522 BPM) Tempo automation
Audio clip gain Audio clip volume
Third-party VST2/VST3 plug-in parameters The same plug-in parameter, when its range is known
EQ Eight band gain, frequency and on/off Fruity Parametric EQ 2

A few more are converted as labelled approximations:

Curved envelope segments are followed with short straight segments, the same way as in the other direction. Simple per-note pitch slides can also become FL Studio slide notes, on Sampler channels converted from Simpler and on channels built from a Drum Rack or Instrument Rack.

Not converted yet

Session View

FL Studio has no Session View, and DAWPORT converts the Arrangement. Session View clips are not converted, so a set that only uses Session View gives an FL Studio project without those clips. The conversion notes say how many Session View clips were left out. Record or drag the clips you want into the Arrangement, with their automation, before converting.

What the conversion notes tell you

Automation that cannot be converted does not stop the conversion. The rest of the project converts, and the conversion notes name the automation that is not active in the converted project, with a short hint: recreate that envelope on the matching control in the destination DAW.

Tips before you convert

  1. In FL Studio, turn important pattern event automation into automation clips.
  2. In Ableton Live, move the clips and automation you need into the Arrangement. Do not rely on Session View clips.
  3. Check that third-party plug-ins are installed where you open the converted project. Plug-in automation only works if the plug-in loads.
  4. After converting, play through the main automated moments and compare them with the original.

Ready to try it? Convert FL Studio to Ableton Live or Ableton Live to FL Studio. For plug-in questions, read will my plug-ins work after converting.

Questions

Do FL Studio automation clips work in Ableton after converting?

Supported ones do. DAWPORT writes them as Ableton Live arrangement automation for tempo, mixer volume and pan, audio clip gain, supported VST2/VST3 plug-in parameters and some converted stock effects. Automation it cannot convert is listed in the conversion notes.

Does Ableton automation transfer to FL Studio?

Arrangement automation of track volume and pan, tempo, audio clip gain, supported VST2/VST3 plug-in parameters and some mapped Live devices becomes FL Studio automation clips. DAWPORT converts the Arrangement, so move Session View clips and their envelopes into the Arrangement first.

Are automation curves kept?

Curved segments are approximated: DAWPORT follows the curve with short straight segments. The shape is close, but it is not the original curve type.

What happens to automation that cannot be converted?

The rest of the project still converts. The conversion notes name the automation that is not active in the converted project so you can redraw it on the matching control.

Convert now