Move a project between Logic Pro, Ableton Live, and Pro Tools. logic2ableton reads the DAWs' proprietary, undocumented session formats and rebuilds your project on the other side: audio placed on the timeline with clip trims intact, tempo, time signature, per-track colors, and note-accurate MIDI that lands as real MIDI tracks.
Wait — how is that possible? Logic stores its MIDI in an undocumented binary blob, and Pro Tools sessions are an obfuscated binary container with no public spec. So they got reverse-engineered — Logic's format verified against Apple's own shipping demo songs, and Pro Tools' against real studio sessions.
📖 Deep-dive: reverse-engineering Logic's binary format → 📖 Deep-dive: inside the Pro Tools session container →
It ships six production workflows in one repo, one desktop app, and one release train:
logic2ableton— convert Logic Pro projects into Ableton Live setsableton2logic— turn Ableton Live sets into Logic-ready transfer packagesprotools2ableton— convert Pro Tools sessions into Ableton Live setsprotools2logic— turn Pro Tools sessions into Logic-ready transfer packagesableton2protools— turn Ableton Live sets into Pro Tools-ready transfer packageslogic2protools— turn Logic Pro projects into Pro Tools-ready transfer packages
The product goal is speed with evidence: every run emits a report showing exactly what transferred cleanly, what needs manual cleanup, and where the source project exceeds what any cross-DAW workflow can preserve.
- One maintained project instead of separate one-off scripts for each DAW direction
- Desktop app for non-technical users, CLI for power users and automation
- Output built for real sessions: copied audio, timeline metadata, and explicit compatibility reporting
- Reports are first-class artifacts, not an afterthought
| Workflow | Input | Output | Best For |
|---|---|---|---|
logic2ableton |
Logic Pro .logicx |
Ableton Live .als + native MIDI tracks + copied media + conversion report |
Moving Logic sessions into Ableton Arrangement View |
ableton2logic |
Ableton Live .als |
Logic import package with track stems, timestamped clip WAVs, Logic timeline MIDI, and transfer report | Rebuilding Ableton sessions inside Logic with much cleaner layout recovery |
protools2ableton |
Pro Tools .ptx |
Ableton Live .als with trimmed clips at session positions + native MIDI tracks + conversion report |
Opening Pro Tools sessions directly in Ableton |
protools2logic |
Pro Tools .ptx |
Logic import package with timestamped clip WAVs and MIDI + transfer report | Rebuilding Pro Tools sessions inside Logic |
ableton2protools |
Ableton Live .als |
Pro Tools import package with spot-to-timestamp WAVs, MIDI files, manifest, and import guide | Handing an Ableton session to a Pro Tools studio |
logic2protools |
Logic Pro .logicx |
Pro Tools import package with spot-to-timestamp WAVs, MIDI files, manifest, and import guide | Handing a Logic session to a Pro Tools studio |
- Audio tracks into Ableton Arrangement View
- Timeline placement from bundled WAV BWF timestamps and Logic AIFF
MARKchunks - Tempo and time signature
- Overlap resolution for takes and comp bounces
- Distinct per-track colors, with arrangement clips matching their track color
- MIDI notes decoded from Logic's binary project data land as native Ableton MIDI tracks inside the
.als(and as Standard MIDI file exports), placed at their absolute arrangement positions - Optional mixer overrides from JSON
- Plugin identification with VST3 suggestions in the report
- Audio-track and clip discovery from
.als - MIDI-track and arrangement note extraction, exported as importable Standard MIDI files
- Tempo, locators, and a documented base time signature
- Logic-ready transfer package with:
Track Stems/for the fastest arrangement-faithful importLogic Timeline/Logic Timeline.midfor tempo and locator importMIDI Tracks/with one Standard MIDI file per Ableton MIDI track, notes placed at their arrangement positionsAudio Files/grouped by Ableton track with timestamped WAV clip exports where supportedtimeline_manifest.jsontimeline_manifest.csvlocators.csvIMPORT_TO_LOGIC.md- a saved transfer report
- Reads
.ptxsessions directly (Pro Tools 10 through current.ptxsaves, plus legacy.pts), including the XOR-obfuscated container - Audio clips with their exact source trims (a clip that plays 8.6 s from the middle of a take stays that clip), placed at their session positions
- Stereo tracks reassembled from Pro Tools' per-channel lanes
- MIDI notes decoded from the session and created as native Ableton MIDI tracks or Logic-importable MIDI files
- Session sample rate and format version detection
- Crossfade render files are recognized and skipped so they don't appear as phantom clips
- Pro Tools import package with per-track folders of timestamped WAV clip exports
- BWF
TimeReferencestamped for Pro Tools' Spot > Original Time Stamp workflow (session start00:00:00:00, no SMPTE hour offset) - One Standard MIDI file per MIDI track
manifest.json, a transfer report, and a step-by-stepIMPORT GUIDE.txt
- MIDI notes transfer as native MIDI tracks (and
.midexports), but the software instruments, their settings, and MIDI effects are not recreated — reload instruments in Ableton - MIDI tracks are named
MIDI 1,MIDI 2, ... (binding Logic's track names to its binary note sequences is still being reverse-engineered) - Notes placed before Logic's bar-1 anchor fall back to relative placement, with a warning in the report
- Older Logic save formats store notes in a binary variant this project cannot decode yet; the report says so explicitly instead of pretending
- Automation is not recreated
- Bus and send routing are not recreated
- Plugin parameters are not recreated
- Imported audio without embedded timestamps defaults to bar 1
- Media outside
Media/Audio Filesis not copied automatically
- The reverse lane does not synthesize a native
.logicxpackage - MIDI note data transfers, but instruments, devices, racks, MIDI effects, and plugin state do not — reload those in Logic
- Looping MIDI clips export only their first pass of notes; repeat them manually in Logic if needed
- Ableton devices, racks, plugin state, and return-bus processing are not transferred
- Warped clips are exported with best-effort timing, but they still need review inside Logic before delivery
- Tempo and markers are exported into the Logic Timeline MIDI file; do not assume time-signature changes are fully reconstructed unless you verify them in Logic
- Non-PCM sources that cannot be rendered to timestamped WAV in-process are copied as references and flagged in the report/manifest
- The transfer package covers audio and MIDI; use the stems and MIDI files first, then clip exports and the manifest if you need finer reconstruction
- Session tempo is not recoverable from
.ptxyet. Audio positions are sample-exact regardless, but beat positions are computed at an assumed tempo (default 120 BPM, override with--tempo). Keep the destination set at that tempo, or pass the real session BPM - Plugins, inserts, sends, automation, clip gain, and fades are not transferred; crossfade renders are skipped
- Elastic Audio state is not reconstructed; clips reference their source audio directly
- The source session's
Audio Files/folder must sit next to the.ptxfor media to be copied - MIDI regions anchor to their first note (a leading-silence offset inside a region is not preserved)
If a project lands imperfectly, the first thing to inspect is the generated report. It is the primary support artifact for this project.
For ableton2logic, the cleanest path is:
- Import
Logic Timeline/Logic Timeline.midinto a new empty Logic project at the project start. - Drag every file from
Track Stems/into Logic starting at bar 1. - If you need clip-level editing, import
Audio Files/and use Logic'sEdit > Move > To Recorded Positioncommand on timestamped WAV clips. - Use the transfer report and
timeline_manifest.csvto review warped clips, copied-source files, and any manual cleanup.
| Method | Command / Link | Description |
|---|---|---|
| PyPI | pip install logic2ableton |
CLI tool, any platform with Python 3.11+ |
| Windows | Installer | Desktop app, standard Windows installer |
| Windows | Portable | Desktop app, single exe, no install needed |
| macOS (Apple Silicon) | DMG (arm64) | Desktop app for M1/M2/M3/M4 Macs |
Download the latest installer or portable build from GitHub Releases:
- Windows: NSIS installer and portable
.exe - macOS: Apple Silicon
.dmg
Notes:
-
macOS builds are ad-hoc signed but not notarized, so Gatekeeper quarantines them on first download. If macOS says the app "is damaged and can't be opened," clear the quarantine flag once after copying it to Applications:
xattr -dr com.apple.quarantine "/Applications/Logic Ableton Transfer.app"Alternatively, right-click the app and choose Open, then confirm in the dialog.
-
Intel macOS users currently need a self-hosted packaging flow or a local source build (release DMGs are Apple Silicon only).
-
The desktop app bundles the converter binary, so end users do not need Python installed.
pip install logic2abletonIf you prefer an isolated global CLI install:
pipx install logic2abletonThen run from anywhere:
logic2ableton "path/to/MySong.logicx" --output ./outputShow the installed version:
logic2ableton --version- Launch the app.
- Drop any session file —
.logicx,.als, or.ptx— into the window; the app detects the source DAW. - Pick the destination DAW and review the preview.
- Select an output directory, run the transfer, and inspect the report if anything looks off.
Choose the command that matches the route:
Logic to Ableton:
logic2ableton "/path/to/MySong.logicx" --output ./outputAbleton to Logic:
ableton2logic "/path/to/MySet.als" --output ./outputPro Tools to Ableton (pass the session tempo so beat positions line up):
protools2ableton "/path/to/MySession.ptx" --output ./output --tempo 128Pro Tools to Logic:
protools2logic "/path/to/MySession.ptx" --output ./output --tempo 128Ableton or Logic to Pro Tools:
ableton2protools "/path/to/MySet.als" --output ./output
logic2protools "/path/to/MySong.logicx" --output ./outputFastest Logic import after the package is created:
- Open
IMPORT_TO_LOGIC.md. - Import
Logic Timeline/Logic Timeline.midinto an empty Logic project at the timeline start. - Drag
Track Stems/*.wavinto Logic starting at bar 1. - Use
Audio Files/only when you want clip-level reconstruction instead of full-track stems.
The original logic2ableton command also auto-detects .als and .ptx input:
logic2ableton "/path/to/MySet.als" --output ./output # runs ableton2logic
logic2ableton "/path/to/MySession.ptx" --output ./output # runs protools2abletonPreview-only / report-only:
logic2ableton "/path/to/MySong.logicx" --report-only
ableton2logic "/path/to/MySet.als" --report-onlyGenerate a Logic mixer template:
logic2ableton "/path/to/MySong.logicx" --output ./output --generate-mixer-template --report-onlyApply mixer overrides:
logic2ableton "/path/to/MySong.logicx" --output ./output --mixer ./output/mixer_overrides.jsonEmit JSON progress for app or automation integration:
logic2ableton "/path/to/MySong.logicx" --output ./output --json-progress
ableton2logic "/path/to/MySet.als" --output ./output --json-progress| Option | Description |
|---|---|
--version, -V |
Show version |
--mode |
Force any of the six lane names (logic2ableton, ableton2logic, protools2ableton, protools2logic, ableton2protools, logic2protools) |
--output, -o |
Output directory |
--report-only |
Write the transfer report without generating output files |
--no-copy |
Do not copy audio files into the generated project/package |
--json-progress |
Emit JSON progress lines for GUI or automation use |
| Option | Description |
|---|---|
--alternative, -a |
Logic alternative index (also on logic2protools) |
--template |
Use a specific DefaultLiveSet.als (also on protools2ableton) |
--vst3-path |
Override the VST3 scan directory |
--mixer |
Apply mixer overrides from JSON |
--generate-mixer-template |
Write a starter mixer_overrides.json |
| Option | Description |
|---|---|
--tempo |
Tempo (BPM) used to convert sample positions to beats; .ptx does not expose its tempo yet (default 120) |
output/
MySong Project/
MySong.als <- audio tracks + native MIDI tracks
Samples/
Imported/
*.wav / *.aif / *.aiff / *.mp3 / *.m4a
MIDI/
01 - MIDI 1.mid
MySong_conversion_report.txt
output/
MySet Logic Transfer/
Track Stems/
01 - Drums.wav
02 - Vocals.wav
Logic Timeline/
Logic Timeline.mid
MIDI Tracks/
01 - Bass.mid
02 - Lead.mid
Audio Files/
01 - Drums/
02 - Vocals/
timeline_manifest.json
timeline_manifest.csv
locators.csv
IMPORT_TO_LOGIC.md
MySet_logic_transfer_report.txt
output/
MySet Pro Tools Transfer/
Audio Files/
01 - Drums/
001 - Kick Loop - *.wav <- BWF TimeReference stamped for Spot > Original Time Stamp
02 - Vocals/
MIDI/
01 - Bass.mid
manifest.json
IMPORT GUIDE.txt
MySet_protools_transfer_report.txt
MySet_protools_transfer_report.txt
- Repeated validation across parser tests, package builds, standalone converter builds, and desktop packaging
- Windows desktop smoke coverage in CI before tagged release packaging
- Reports emitted on both success and failure paths so support starts with evidence instead of guesswork
- Desktop app safety rails around approved files, active jobs, and artifact opening
- Ableton to Logic now ships multiple reconstruction layers instead of a single manifest-only package
- The Pro Tools parser is validated against a real Pro Tools 2023 studio session (96 kHz, comped vocals, stereo lanes) and a synthetic obfuscated fixture that runs in CI
- All six conversion lanes ship from the same repo and version together
Pay close attention to COMPATIBILITY WARNINGS.
Typical warnings include:
- Audio referenced by the source project but missing on disk
- Logic audio with no embedded timeline timestamp
- Ableton clips that rely on warping or other live processing that cannot be rendered faithfully by this project
- Reverse-lane sources that were copied as references instead of rendered into timestamped WAV files
Warnings generally mean one of two things:
- the converter needs a parser/generator improvement
- the source session needs manual cleanup or a more deliberate export/import path
Known deficiencies, open reverse-engineering threads, and the prioritized improvement plan live in HANDOFF.md. Feature phases live in ROADMAP.md.
Run tests:
python -m pytest tests -qNo third-party Python dependencies. The Ableton template is bundled, so no Ableton installation is needed to generate Live sets.
Build the Python package:
python -m buildBuild the standalone converter:
pyinstaller logic2ableton.spec
dist/logic2ableton.exe --versionRun the desktop app in development:
cd app
npm ci
npm run devBuild the desktop app:
cd app
npm ci
npm run buildBuild the Windows release artifacts locally:
pyinstaller logic2ableton.spec
copy dist\logic2ableton.exe app\resources\logic2ableton.exe
cd app
npm ci
npm run dist:winGitHub Actions validates:
- Python tests on Windows and macOS
- Python package builds
- Windows desktop smoke builds before release tags
- Tagged release packaging for Windows and macOS
Publishing a release is done by pushing a v* tag. The workflow uploads the generated installers to GitHub Releases automatically.
Useful issues include:
- The Logic Pro or Ableton Live version used to save the project
- The exact generated report
- A minimal failing project if one can be shared
- Whether the issue is in the desktop app, CLI, or packaging
Open issues here: https://github.com/Evilander/logic2ableton/issues
MIT