Pro Tools session to Logic Pro, via FCPXML (Beta)

Bring a Pro Tools session into Logic Pro with its tracks, clips, fades and crossfades, and the tempo map as a MIDI file.

Opens: PTX, PTF, PTS, ZIP
Saves: RPP (REAPER), XML (Premiere, Resolve), FCPXML (Logic Pro), OTIO, EDL, MIDI, XLSX, CSV, HTML, PNG

Convert

Pro Tools session

Choose a file… or drop it here

.ptx, .ptf, .pts, .zip · up to 4096 MB

Replace file

The session file (.ptx from Pro Tools 10 and later, .ptf from 7 to 9, .pts from 5 and 6), or a .zip of the whole session folder with its Audio Files folder. With the folder, the audio is checked and can be packed with the REAPER project.

Options

Session folder on your computer (optional)

Where the session folder is on the computer you will open the results on, for example D:\Sessions\My Song or /Users/me/Music/My Song. The Premiere, Logic and OTIO files then point at the audio there. Left empty, they point where it was when the session was saved. The REAPER project finds the audio when it is saved in the session folder either way.

Render each track as a WAV file (ZIP uploads)

When the session folder was uploaded as a .zip with its audio, also render every track to one WAV file (clips, fades and crossfades as edited; volume, pan and plug-ins are not applied). All files start at the same point, so they line up in Ableton Live, Studio One, Cubase, FL Studio or any other program.

More options

Pack the REAPER project with the audio (ZIP uploads)

When the session folder was uploaded as a .zip, also make a .zip of the REAPER project with every audio file it plays in place, ready to unpack and open.

Your files are deleted after processing.

Tell us how this tool could be better

Open a Pro Tools session in Logic Pro

Logic Pro has no import for Pro Tools sessions, but it does import Final Cut Pro XML. This tool writes the session as FCPXML, so Logic Pro gets the edit itself: every clip on its track at its exact place, with its crossfades and fades, rather than a folder of loose audio files.

Steps

Upload the .ptx session file, or the whole session folder as a .zip.
If the session folder is in a different place on your Mac than on the computer that made the session, enter its path under "Session folder on your computer", for example /Users/you/Music/Song, so the FCPXML points at the audio where it now is.
In Logic Pro choose File > Import > Final Cut Pro XML and pick the .fcpxml file.
For the tempo, open the MIDI file from the same download: it carries the tempo, meter and key changes and the markers, and the notes of every MIDI and instrument track.

How the session is laid out

Each Pro Tools track becomes its own lane, with the track name as the audio role, so the tracks stay apart. Times are written in samples, not rounded to video frames, so music edits stay sample accurate. Crossfades are written as audio crossfades between the two clips, fades from and to silence as clip fades, and muted clips come in disabled.

What to redo in Logic

Volume, pan and automation, plug-ins and their settings, and sends are not carried over. The session report lists the plug-ins on every track, and the spreadsheet lists every clip with its start, end and source file if you need to check something by hand.

Not using Logic's import?

The same download has every track rendered as one WAV file when you upload the session folder as a ZIP. Drag them all in at the start of a Logic project and they line up, with the edit, fades and crossfades as they were.

More about what this tool reads and writes: Pro Tools Session Converter (PTX, PTF, PTS).