shibco/ableton-linux: Running Ableton Live 12 and Push on a Linux Desktop

The gap shibco/ableton-linux is trying to close

Ableton ships Live for Windows and macOS. Linux users who want it have historically had two options: run it in a general-purpose Wine prefix they maintain themselves, or switch to a DAW that targets Linux natively. Neither is a good answer for someone whose sessions, plug-ins and Push workflow already live in Live.

This project is aimed at that second group. The README describes making "the popular Berlin-based DAW and its ecosystem of products a first-class Linux citizen", and the supported surface is wider than just the DAW: Live 12 and Live 11 in Intro, Standard, Suite, Lite and Trial editions, the Live 12+ beta, Cycling '74 Max 8, Max 9 and Max for Live, Splice integration, Ableton Cloud, Ableton Link, and an experimental Extensions SDK. Push 1, Push 2 and Push 3 are listed as supported hardware, with Ableton Move marked as coming soon.

The README is explicit that the project is "absolutely not affiliated with or endorsed in any way by Ableton AG" and that it respects the Ableton terms of service. That framing matters for how you read everything else: you still need your own installation files and activation details from Ableton, and the licence you hold is the one you are running under.

How the runtime is put together: Wine, PipeASIO and pinned inputs

There is no native Linux build of Live here. The runtime is a Wine tree, built by the project, that Live and Max run inside, plus a launcher that wraps the environment variables Live needs. The topics on the repository list win32, wine and nix alongside ableton and linux, which matches the layout: patches/, vendor/, nix/ and a flake.nix sit next to build.sh and the installer scripts.

Audio is the part that decides whether this is usable for performance. The README calls out "low-latency PipeASIO audio for live performance", and the first-launch instructions tell you to set Driver Type to ASIO and Audio Device to PipeASIO in Live's audio settings. PipeASIO is the bridge between Live's ASIO expectations and PipeWire underneath.

Around that core, the README lists a set of behaviours that a hand-rolled Wine prefix usually gets wrong: MIDI controllers and audio interfaces that can disconnect and return while Live stays open, native file types and dialogs, desktop font reuse, automatic light and dark theme detection, HiDPI and fractional scaling, and fixes for VST-specific display and stability problems. The build side claims "auditable builds with pinned inputs, checksum verification, and public documentation", which is why flake.lock and vendor/ exist rather than a set of downloaded tarballs at build time.

One design decision is worth flagging. The README states the project "intentionally designed this project to not update itself automatically". That is a privacy argument, and it is coherent, but it means patch cadence is something you opt into rather than receive.

Installing Ableton Live on Linux with the .run installer

The installer is distributed as a single .run file from the releases page. The README's three-step path is to download the Ableton Live installation ZIP from Ableton.com, download the latest installer, and double-click it. From a terminal, the equivalent is:

sh ~/Downloads/install-ableton-latest.run install

If you keep several Ableton installers in your Downloads folder, point the installer at the one you want with --live-installer. The README gives this example:

sh ~/Downloads/install-ableton-latest.run install \
  --live-installer "$HOME/Downloads/Ableton Live 12 Installer.zip"

Without that flag, the installer looks for an Ableton Live archive in the same directory as itself. After it finishes, start Live the way you start any other desktop application, or from a terminal:

ableton-live

You can hand it a set to open on launch, and you can inspect every environment variable the launcher understands rather than guessing at them:

ableton-live "/path/to/Your Set.als"
ableton-live --config

The first launch is where audio gets configured. Go to Settings > Audio, set Driver Type to ASIO, and set Audio Device to PipeASIO. If Live reports that NTSync is inactive, TROUBLESHOOTING.md has a check for that, and it is the failure most likely to stop you before anything else works.

Requirements that will rule some machines out

The installer targets x86-64 Linux and inherits Ableton Live's own hardware requirements on top of its own list: glibc 2.35 or newer, PipeWire 1.4.2 or newer, Linux 6.14 or newer with active NTSync, GStreamer with the base and good plugin sets, and GNU coreutils, tar, zstd and flock. You also need your installation files and activation details from Ableton.

The PipeWire floor is the sharp edge. The README names Debian 12, Linux Mint, and Pop!_OS 24.04 and earlier as distributions that ship an older PipeWire and will need it updated before Ableton Live will install, and points at a troubleshooting guide for that case. If you are on one of those systems and not willing to move your audio stack, this project is the wrong tool for you today.

NTSync is the second gate. The README says NTSync support varies between distributions and that some systems need newer system or kernel packages. There is a documented check for whether it is ready for Live, and no way around it: Live will report it as inactive.

AArch64 is explicitly experimental. Apple Silicon machines running Asahi Linux are tracked in a draft pull request, not in the supported feature list, so treat that as unfinished work rather than a platform you can rely on.

The upgrade path has its own cost. Because the project does not self-update, you download a new release and run:

sh ~/Downloads/install-ableton-latest.run update

The README says this preserves your Live installation, authorisation and projects, and that you should read the latest changelog entry before updating, because a release can change a launcher default or ask you to select a renamed device again. That is a real operational burden: it is a manual step, and the changelog is part of the upgrade, not optional reading.

Uninstalling without losing your authorisation

The uninstall behaviour is split deliberately, and it is worth understanding before you install rather than after. The plain uninstall removes the recorded Linux files and the Wine runtime while keeping the Wine prefix, Live, authorization, installer settings and shared records. The README notes this selects --keep-prefix, and you can write the flag out:

sh ~/Downloads/install-ableton-latest.run uninstall --keep-prefix

The destructive variant removes the ableton-linux prefix, Live, its authorization, and plug-ins installed inside that prefix:

sh ~/Downloads/install-ableton-latest.run uninstall --delete-prefix

If a recorded Linux file or link changed after installation, uninstall asks whether to remove it, and Keep is the default answer. The README also warns to run link disable before uninstall when Link opened a firewall port or enabled the user service. That is the one piece of cleanup that is easy to forget, and it is the reason Link gets called out separately from the rest of the runtime.

Where it sits against a native Linux DAW

The honest alternative is a DAW built for Linux from the start: Ardour, Bitwig Studio, Reaper, or any of the trackers and modular environments that ship native builds. The difference is not cosmetic. A native DAW talks to ALSA, JACK or PipeWire directly, so there is no Wine translation layer between the audio callback and the driver, no ASIO shim, and no prefix to rebuild when a distribution update moves something underneath you.

What you give up by going native is everything you already own in Live: your sets, your Max for Live devices, your Push muscle memory, and the Splice and Ableton Cloud integrations. That is the trade this project is built around. It does not try to be a better DAW than Live; it tries to make the DAW you already have run on the OS you want to use.

If you have no existing Live investment, a native DAW is the lower-risk choice, and nothing in this repository changes that. If you do have that investment, the comparison is between this project's maintained Wine runtime and a prefix you maintain yourself, and the difference there is the patches, the PipeASIO audio path, the desktop integration work, and the pinned build inputs.

Editorial conclusion

Adopt it if you already own an Ableton licence, run a current distro with PipeWire 1.4.2 or newer and a 6.14+ kernel with active NTSync, and want Live 12 plus Push on Linux without maintaining your own Wine prefix. Do not adopt it if you need a supported, vendor-blessed path, if you are on Debian 12 or an older Pop!_OS where PipeWire is too old, or if you want a DAW that is native to Linux and needs no Wine at all. Before installing, confirm that NTSync reports active on your kernel, that your Ableton installer archive is the one you intend to point at, and that you accept a project that does not update itself automatically.

Frequently asked questions

Official sources

1. Issues
2. License: LGPL-2.1
3. README
4. Releases
5. shibco/ableton-linux on GitHub