Version 2.0 turns this project into a dual-direction transfer toolkit for Logic Pro and Ableton Live.
It ships two production workflows in the same repo, the same desktop app, and the same release train:
logic2ableton: convert Logic Pro projects into Ableton Live setsableton2logic: turn Ableton Live sets into Logic-ready transfer packages
The product goal is speed with evidence. Every run produces a report so users can see exactly what transferred cleanly, what needs manual cleanup, and where the source project exceeds what a 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 + copied media + conversion report |
Moving audio-first 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 audio sessions inside Logic with much cleaner layout recovery |
- 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
- Optional mixer overrides from JSON
- Plugin identification with VST3 suggestions in the report
- Audio-track and clip discovery from
.als - 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 importAudio Files/grouped by Ableton track with timestamped WAV clip exports where supportedtimeline_manifest.jsontimeline_manifest.csvlocators.csvIMPORT_TO_LOGIC.md- a saved transfer report
- MIDI and software instrument tracks are not recreated
- 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 - 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 is audio-first; use the stems first, then clip exports and the manifest if you need finer reconstruction
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 unsigned. Gatekeeper may require opening them manually the first time.
- Intel macOS users currently need a self-hosted packaging flow or a local source build.
- 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.
- Choose
Logic to AbletonorAbleton to Logic. - Drop a
.logicxor.alsfile into the window. - Review the preview and select an output directory.
- Run the transfer and inspect the report if anything looks off.
Choose the command that matches the source DAW:
Logic to Ableton:
logic2ableton "/path/to/MySong.logicx" --output ./outputAbleton to Logic:
ableton2logic "/path/to/MySet.als" --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 input:
logic2ableton "/path/to/MySet.als" --output ./outputPreview-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 logic2ableton or ableton2logic |
--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 |
--template |
Use a specific DefaultLiveSet.als |
--vst3-path |
Override the VST3 scan directory |
--mixer |
Apply mixer overrides from JSON |
--generate-mixer-template |
Write a starter mixer_overrides.json |
output/
MySong Project/
MySong.als
Samples/
Imported/
*.wav / *.aif / *.aiff / *.mp3 / *.m4a
MySong_conversion_report.txt
output/
MySet Logic Transfer/
Track Stems/
01 - Drums.wav
02 - Vocals.wav
Logic Timeline/
Logic Timeline.mid
Audio Files/
01 - Drums/
02 - Vocals/
timeline_manifest.json
timeline_manifest.csv
locators.csv
IMPORT_TO_LOGIC.md
MySet_logic_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
- Both conversion directions 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
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