Using AAF Bridge, AAF in and out of Ableton Live.

Getting started

1. Pick a direction at the top: AAF / XML → Ableton (import) or Ableton → AAF / XML (export).
2. Choose or drop the source file. AAF Bridge shows tracks, clips, markers and media type before anything happens.
3. Turn the individual features on or off under What transfers.
4. Click Convert. A conversion report is written next to the result and lists exactly what was transferred and anything that needs your attention.

The app runs entirely on your computer, no files ever leave your machine, and there is nothing extra to install (the MXF converter is built in).

Requirements: macOS 13 or newer (Apple Silicon) or Windows 10/11. Created projects open in Ableton Live 11 and Live 12.

Install & first run

Move AAF Bridge to your Applications folder (macOS) or run the installer (Windows), then launch it.

Choosing a format

Prefer AAF. It is the audio-post standard and the format we test hardest: sample-accurate, with embedded fades, clip gain and a solid relink chain. Reach for an XML format only when the app on the other side cannot read AAF.

What each format carries

• AAF, richest. Sample-accurate positions and handles, embedded or linked audio, real crossfade transitions, clip gain, volume automation, pan, markers, and colors on the round trip back to Ableton. MXF audio auto-converts on import.
• Premiere XML (Final Cut 7 XML, .xml), for Premiere Pro. Frame-quantized (not sample-accurate); sequences arrive with real stereo tracks; crossfades travel as real transitions, fades and clip gain as volume keyframes. Moving volume automation is left out (never averaged); no pan or colors. Media is always linked.
• FCPXML (.fcpxml), for Final Cut Pro. Sample-accurate (rational time); keeps fades and clip gain; volume automation travels as real Final Cut volume keyframes; crossfades travel as true overlapping blends on a paired lane (no level dip); tracks arrive grouped by audio role. No pan or colors. Media is always linked.
• FCPXMLD (.fcpxmld), the same FCPXML as a bundle (Final Cut Pro 10.6 +, the format Final Cut itself exports today). Works in both directions; with Collect media the audio files pack right into the bundle, one movable package.

On import, the format is detected from the file extension, just choose or drop it. On export, pick the target under Deliver to.

Import, AAF / XML → Ableton Live

Accepts an AAF (Resolve, Pro Tools, Media Composer, Premiere’s own AAF export etc., the recommended, sample-accurate way in), an FCPXML / FCPXMLD (.fcpxml / .fcpxmld bundle, Final Cut Pro) or, as a fallback, a Premiere XML (Final Cut 7 XML, .xml; frame-quantized, prefer Premiere’s AAF export instead). Creates a new Ableton project folder next to the source file: the .als, a Samples/ folder for any extracted or converted audio, and the project marker Ableton uses. The result behaves exactly like a session you saved from Ableton yourself.

Video: opening an AAF in Ableton Live, start to finish.

What transfers

• Audio clips, position and source offset, sample-accurate.
• Track layout, track names and order.
• Clip gain, fades & crossfades, pan, volume automation, markers, track/clip colors, each switchable. Pan (static and automated) and colors exist only in AAF sources. Volume automation arrives from AAF curves, from FCPXML volume keyframes and from Premiere XML volume rides, and DaVinci Resolve doesn’t write pan or volume automation into its AAFs at all (a known Resolve limitation; Pro Tools, Nuendo etc. do).
• Crossfades in detail, they become Live-native crossfades: full blend length and no level dip. By default the edit point sits exactly where your editor or DAW cut it; an optional Acoustic crossfade compensation shifts it by half the blend instead, so Live’s waveform lines up with what you hear (for editors that place crossfades symmetrically), the crossfade transfers either way. Acoustically this is as close as Ableton can render, one nuance: Ableton blends with its own curve, so with very different material the blend character may differ slightly from your NLE’s render; positions and material stay sample-exact, and a round trip restores the original transition precisely.
• Video reference track, the picture cut comes in on its own video track, so Ableton’s video window follows the edit while you mix to image.

Combine split-stereo tracks (AAF → Ableton)

Some editors export stereo tracks as two mono tracks, either by default or as an option. Nuendo, Cubase and Pro Tools, for example, write two identically named neighbour tracks for left and right. AAF Bridge detects these pairs when you load an AAF and combines them back into stereo tracks.

The Combine split-stereo tracks toggle turns itself on when pairs are found, and a review window opens before converting: it lists every pair, lets you uncheck any of them, rename the combined track, or pair two tracks manually if a split wasn’t detected automatically. Each combined clip becomes one interleaved stereo file at the original sample rate and bit depth.

Tips

• Set tempo and time signature before converting. AAF files carry neither, so enter them for your Ableton session; otherwise the Set opens at 120 BPM / 4·4.
• MXF audio is handled automatically. Resolve often wraps audio in MXF containers, which Ableton cannot read. AAF Bridge converts them to WAV on the fly (into Samples/Converted/), nothing to install.
• Extract video audio (a switch, off by default), only needed when a clip takes its sound directly from a video file (.mov/.mp4). Turned on, that audio is decoded to a video-free WAV so Ableton shows one clean, continuous picture instead of the movie’s frames cutting at every audio edit. Most footage delivers audio and video separately, leave it off then.
• Collect media into project makes the folder fully self-contained: every referenced file is copied into Samples/, so the project can be moved or archived as one folder.
• Keep the project folder together. Ableton resolves audio relative to the .als first; if you move only the .als, clips may show offline.

Limitations

• No devices or mixer settings. The new session is intentionally “bare”, AAF carries no plugins, EQ or effects. Ableton re-analyses the audio on first open.
• Pan only appears if the source app wrote it. DaVinci Resolve does not export pan, a known Resolve limitation. Nuendo and Pro Tools AAFs carry it.
• Volume automation depends on the source. Resolve has a known bug and does not write volume automation to AAF; Pro Tools and others do.
• Referenced (not embedded) audio must stay reachable at its path, unless you use Collect media. Clips whose audio lives inside a video file (.mp4/.mov) load in Ableton, but that video file must remain reachable.
• XML imports carry less than AAF. Premiere XML and FCPXML always link their media (no embedded audio), and neither carries track/clip colors. MXF audio still auto-converts, and Collect media still works. If the source app can write AAF, prefer it.
• Ableton Live version: sessions open in Live 11 and 12. They do not open in Live 10 or earlier (Ableton changed the session format).

Export, Ableton Live → AAF / XML

Pick a target under Deliver to, AAF, Premiere XML, FCPXML or FCPXMLD, and AAF Bridge writes that file next to your .als. Audio is placed sample-accurately (AAF and FCPXML) or frame-quantized (Premiere XML); the chosen frame rate drives the timecode track for the editor or DAW.

Video: exporting an AAF from Ableton Live, Live Set to AAF, opened in Resolve.

What transfers

• Audio clips, position and source handles, sample-accurate, with correct track names.
• Clip gain, fades & crossfades, pan (static and automated), volume automation, markers, colors, video reference, each switchable.
• Channel counts, mono stays mono, stereo stays stereo, and multichannel stems keep all channels in AAF and FCPXML. Premiere XML is built on stereo pairs, so mono arrives as a centered pair and >2-channel material is delivered as stereo, the report says so per clip.

One track per channel (Ableton → AAF)

This export option splits stereo audio into one mono file per channel, the split-file layout some editors work with internally. Your stereo tracks stay stereo tracks in the timeline; only the media files are delivered per channel. Turn it on for Pro Tools, Nuendo and other NLEs / DAWs that work that way; leave it off for Resolve and Media Composer, which expect ordinary interleaved files.

Tips

• Frame rate sets the AAF’s timecode track, and the timecode start next to it says where the timeline begins in the editor, 01:00:00:00 by convention, but any HH:MM:SS:FF works. The clips still start at the beginning; only the timeline’s own count changes. Audio placement is sample-accurate at any rate. Choose none only for a DAW-to-DAW handoff that is not going to a video editor, no timecode track is written then, and the start value is switched off with it.
• Collect media next to AAF puts the export and its media into one package folder, Name/Name.aaf plus Name/Media/, a complete, movable turnover the editor can open without access to your drive (a .fcpxmld bundle packs the media inside itself instead).
• Muted tracks & clips are left out by default (the export delivers what is audible). Turn the switch on to include muted tracks and clips Ableton has deactivated.
• Target editors: the export is built for DaVinci Resolve, Pro Tools and Avid. In Resolve: File → Import → Timeline; if clips show offline, right-click → Relink.

Limitations

• Time-stretched (warped) clips. AAF cannot represent Ableton’s warping. Clips you have genuinely time-stretched are flagged; the package contains their original audio, so in the target app they play at their original speed. Consolidate these clips in Ableton first (select them, press Cmd+J) so the stretched audio becomes a real file. Clips merely warped 1:1 (not stretched) export correctly.
• Only real fades are exported. Ableton adds an inaudible ~4 ms click-protection fade to every clip edge; these are not exported (they would otherwise become audible fades in the target app). The same rule applies to sub-frame crossfades: instead of a fake blend against silence they become a clean butt cut. The fades you created are transferred at their exact length, never rounded to frames.
• Pan travels via AAF, the static track pan and pan automation are both written as a standard Mono Audio Pan curve that Pro Tools, Nuendo and Avid read (DaVinci Resolve ignores pan on AAF import). The XML formats have no pan field.
• Fade curves are transferred as linear with the exact length; non-linear skew/slope shapes are approximated.
• Colors are written for the round trip back to Ableton; other editors ignore them.
• MIDI is not supported, AAF is an audio format. Bounce MIDI to audio before exporting.
• XML formats carry less than AAF. Premiere XML is frame-quantized, with crossfades as real transitions and clip gain as a constant level, moving volume automation is left out rather than averaged to some invented value. FCPXML is sample-accurate and carries volume automation as real Final Cut keyframes; neither XML format carries pan or colors. Prefer AAF whenever the target reads it; keep your Live Set as the mix master either way.
• Adobe Premiere Pro cannot import AAF, so for Premiere, choose Deliver to → Premiere XML and import it with File → Import. (Premiere also rejects Resolve’s own AAFs, this is a Premiere limitation, not ours.)

Editor-specific notes

Each app reads and writes a slightly different format and subset, AAF for Resolve, Pro Tools and Avid; XML for Premiere and Final Cut. Here is what to expect per editor, and where a limit is the source app’s, not ours.

What reaches Ableton when you import

The table is for the import direction (editor → Ableton), because that is where the editors genuinely differ: each cell reflects what that app’s own export actually contains, not a limit of AAF Bridge. On the way back out, the Bridge writes the same rich AAF to every AAF-capable app.

¹ DaVinci Resolve does not export pan to AAF, a Resolve limitation, not the Bridge’s. ² The XML formats have no pan field at all. ³ Resolve has a known bug and writes no volume automation to AAF; Pro Tools, Avid and Nuendo do. ⁴ Premiere XML and FCPXML carry volume as keyframes when the sequence has them, they arrive as fades or ride automation. ⁵ Premiere XML doesn’t store track names; tracks come in generic (A1, A2 …).

Two things that apply to every route. Colors only round-trip Ableton → AAF → Ableton, a Resolve or Pro Tools timeline carries no Ableton-style clip colours to import. And Ableton has no mono tracks: every audio track is stereo, so a mono clip (say dialogue from Pro Tools or Resolve) plays centred on a stereo track, the audio stays mono, nothing is up-mixed. On export the Bridge writes each clip’s real channel count back, so a mono file stays mono in the AAF.

DaVinci Resolve

• Import and export both fully supported. The export uses a Resolve-style layout; in Resolve use File → Import → Timeline, and right-click → Relink if clips show offline.
• MXF audio is converted to WAV automatically on import, Resolve often wraps audio in MXF, which Ableton cannot read.
• No pan from Resolve. Resolve does not export pan to AAF, so imported clips have none. That is a Resolve limitation, not AAF Bridge’s.
• No volume automation from Resolve. Resolve has a known bug and does not write volume automation to AAF. Pro Tools and others do.

Pro Tools

• Import and export both fully supported. Pro Tools AAFs carry pan and volume automation, so more comes across than from Resolve.
• On export, open the AAF in Pro Tools via File → Import → Session Data (or drag it into the session).

Avid Media Composer

• Import and export both supported. Avid is the reference AAF implementation, named tracks and sample-accurate positions transfer cleanly in both directions.

Adobe Premiere Pro

• Delivering TO Premiere: use XML. Premiere cannot import third-party AAFs (it rejects even Resolve’s own), so delivery goes through Final Cut 7 XML.
• Export: choose Deliver to → Premiere XML. AAF Bridge writes a Final Cut 7 XML (.xml); in Premiere use File → Import and pick it. Media relinks from its original location (or the Media folder). It is frame-quantized; sequences arrive with real stereo tracks, crossfades as real transitions, fades and clip gain as volume keyframes. Moving volume automation is left out rather than averaged, keep your Live Set as the mix master.
• Importing FROM Premiere: use Premiere’s AAF export (File → Export → AAF, the audio hand-off Premiere itself offers), it is sample-accurate and the route we test hardest. A Premiere sequence exported as Final Cut XML is accepted as a fallback, but it is frame-quantized and carries less, not the recommended way in.

Apple Final Cut Pro

• Uses FCPXML (.fcpxml) or the newer FCPXMLD bundle (.fcpxmld, Final Cut Pro 10.6 +) in both directions. On export, choose Deliver to → Final Cut Pro (FCPXML or FCPXMLD); in Final Cut use File → Import → XML.
• Sample-accurate, FCPXML stores rational time, so clip positions, fades and gain come across exactly.
• Tracks arrive grouped by audio role (Final Cut groups by role, not by track). Volume automation travels as real Final Cut volume keyframes; crossfades arrive as overlapping clips with fade keyframes, that is Final Cut’s own audio blend (a Cross Dissolve transition only blends video). Pan and colors are not part of FCPXML.
• Compound, multicam and synchronized clips do not carry their contents through any converter. Select them in Final Cut and use Clip → Break Apart Clip Items before exporting, AAF Bridge flags them in the report if it finds any.

Other AAF-capable DAWs

• Apps like Nuendo or Cubase generally work in both directions when they read and write standard AAF. What transfers depends on the subset that app writes into the file.

Applies to every editor

• No MIDI, AAF is an audio format; bounce MIDI to audio first.
• No devices, plugins or mixer settings, AAF carries clips and edits, not your processing chain.
• Tempo and time signature are not stored in AAF, set them on import.
• Warped / time-stretched clips are flagged, with the original audio in the package; consolidate in Ableton first for a stretched render (see Export).

The conversion report

Every conversion writes a plain-text report next to the result:

• Direction, source, output, date.
• Transferred, what came across (tracks, clips, fades, and so on).
• Notes & actions required, anything to be aware of: muted content skipped, click-protection fades removed, clips to consolidate, media collected.

Keep the report with the delivery, it documents exactly what was converted, so your collaborators know what to expect.

Licensing

AAF Bridge is free to try without limits: the demo converts the first 120 seconds of any timeline, as often as you like, with your real files. A license unlocks full-length conversions.

• Activate once, then it works offline, no repeated online checks.
• Switching computers? Open the license panel and choose Deactivate this computer to release the seat, then activate on the other machine.
• Updates keep your license, it is stored outside the app, so installing a new version does not require re-activation.

Questions, or something unexpected in a conversion? Send the report (the .txt next to your output) to support@aafbridge.com, it tells us almost everything we need, and you’ll hear back from the person who wrote the code.