Ableton Linux: a Wine runtime you update by hand, with PipeASIO underneath
Run Ableton 12 and Push on Linux
At a glance
- What is it?
- shibco/ableton-linux packages Ableton Live 11 and 12, Cycling 74 Max and Push 1 to 3 into a Wine runtime with low latency PipeASIO audio and desktop integration. It deliberately refuses to update Live for you, and the PipeWire and NTSync floors decide whether it installs at all.
- Who is it for?
- Use this runtime if you produce or perform with Live on x86-64 Linux and can meet the PipeWire 1.4.2 and Linux 6.14 NTSync floors without fighting your distribution. Pass if you need automatic updates, a Mac, or an Ableton Move workflow, since none of those are in the supported set.
- Can I use it commercially?
- Yes, with conditions. LGPL-2.1 is a weak copyleft licence: you can use it inside commercial and closed-source software, but if you distribute changes to its own files, you must publish those changes under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 21 days ago.
- What is it written in?
- Mainly Shell, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- shibco/ableton-linux905 ★ · +367
| Repository | 2026-09-17 | 2026-11-15 |
|---|---|---|
| shibco/ableton-linux | 538 | 905 |
367 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Updating is deliberately left to you
Ableton Live ships its own application updater, and this project keeps its hands off it on purpose, to protect your privacy. That means no silent download and no restart on a Tuesday; the update is a deliberate command you run from a terminal:
sh ~/Downloads/install-ableton-latest.run updateThe update applies the fixes and features listed in CHANGELOG.md and preserves your Live installation, your authorisation and your projects. The instruction to read the newest entry first is not ceremony. A release can change a launcher default or ask you to select a renamed audio device again, so skipping the changelog is how a working setup turns into a silent problem. The last three tags published were 2026.08.24.2 on 2026-08-24, 2026.08.26.1 on 2026-08-26, and 2026.08.30.1 on 2026-08-30, and the last push to the main branch is dated 2026-09-22.
PipeWire 1.4.2 and an active NTSync are the real gate
The main installer needs an x86-64 Linux system that already meets Ableton Live's own hardware requirements, and on top of that it checks glibc 2.35 or newer, PipeWire 1.4.2 or newer, Linux 6.14 or newer with active NTSync, GStreamer with its base and good plugin sets, and GNU coreutils with `tar`, `zstd`, and `flock`. You also need your own Ableton installation files and activation details, because the runtime never ships a licence.
The audio stack is where installs fail. NTSync support varies between distributions, so some systems need newer system or kernel packages, and a linked check tells you when it is ready for Live. Debian 12, Linux Mint, and Pop!_OS 24.04 and earlier ship an older PipeWire and need it updated before the installer will proceed. SteamOS, Ubuntu, CachyOS and Arch already satisfy the userspace side for most people.
The installer hunts for an Ableton ZIP beside itself
The short version is three steps: take the Live installation ZIP from Ableton.com, download the latest `install-ableton-latest.run`, and double-click it. Once started, the install is mostly automatic. From a terminal the same run is:
sh ~/Downloads/install-ableton-latest.run installIf you have several Ableton Live installers lying around, point the command at the one you want rather than letting it guess:
sh ~/Downloads/install-ableton-latest.run install \
--live-installer "$HOME/Downloads/Ableton Live 12 Installer.zip"Without that flag the installer searches the directory it was run from, so the filename of the archive matters: double-check the name of the Ableton installer you downloaded before you start.
Audio setup is two fields inside Live itself
On first launch there is no separate mixer panel to learn. You open Settings, go to Audio, set Driver Type to ASIO, and set Audio Device to PipeASIO. That is the entire routing step, and it exists because the runtime exposes PipeASIO as the ASIO implementation rather than leaving Live to fall back on a generic backend.
Everything else the runtime claims to smooth over sits underneath that choice. MIDI controllers and audio interfaces can appear, disconnect and return while Live stays open, which is the failure mode that normally forces a restart mid set. On the visual side there is automatic light and dark theme detection, native file types and dialogs, advanced font rendering that reuses your own desktop fonts inside application windows, and handling for fractional scaling on HiDPI displays. VST-specific display, audio and stability problems get fixes, and startup time and resource use are tuned for running reliably under Wine.
Uninstall keeps the Wine prefix unless you say otherwise
Removing the runtime while keeping your work is the default behaviour, and it is spelled two ways that do the same thing:
sh ~/Downloads/install-ableton-latest.run uninstallsh ~/Downloads/install-ableton-latest.run uninstall --keep-prefixThe first form selects `--keep-prefix` for you. It removes the recorded Linux files and the Wine runtime while leaving the prefix, Live, your authorisation, installer settings and shared records in place. To go further and remove the ableton-linux prefix, Live, its authorisation and plug-ins installed inside that prefix as well, name the other option:
sh ~/Downloads/install-ableton-latest.run uninstall --delete-prefixTwo details make that last one less destructive than it sounds. If a recorded Linux file or link changed after installation, uninstall asks whether to remove it and Keep is the default answer. And if Link opened a firewall port or enabled the user service, run `link disable` before you uninstall.
The launcher prints its own defaults on request
Live starts the way any other application starts on your desktop, but the launcher takes arguments when you want them. A Set can be opened straight away:
ableton-live "/path/to/Your Set.als"Environment variables change how the command behaves, and rather than leaving you to guess their names, the launcher explains every available setting together with its default:
ableton-live --configCommand-line options are listed separately with `ableton-live --help`. Live 11 users are pointed at their own instructions, since the same runtime covers both major versions. Having a printable config dump is what makes a launcher script debuggable when a session behaves differently from the desktop start.
Apple Silicon and NixOS each need a different route
The installer targets x86-64, which excludes a specific set of machines rather than being a general limitation. Experimental AArch64 work for Apple Silicon computers running Asahi Linux is tracked in draft PR 259, so it is in progress and not part of a released build.
NixOS is the other special case. Installation there requires using the flake, with the details in FLAKE.md, and the repository carries flake.nix, flake.lock and a `nix/` directory to support that. The same flat build surface is visible elsewhere: a Containerfile and vendor/ for pinned inputs, build.sh producing into dist/, a `bench/` directory with a `test-bench` target, and a Makefile whose single `test` target fans out into more than twenty shell gates including `test-check-ntsync.sh`, `test-pipeasio-installer.sh`, `test-link-boundary.sh` and `test-bench-suite.sh`.
Support is listed edition by edition, and Move is not there yet
The supported surface is enumerated rather than implied. Software covers Live 12 in its Intro, Standard, Suite, Lite and Trial editions, Live 11 in the same five, Cycling 74 Max 8, Max 9 and Max for Live on Live 11 and 12, Live 12+ Beta, Splice integration, Ableton Cloud, Ableton Link, and experimental Extensions SDK support. Hardware covers Push 1, Push 2 and Push 3. Ableton Move support is marked as coming soon, which means it does not work today.
Two constraints sit outside that list and are worth reading first. The project states it is not affiliated with or endorsed in any way by Ableton AG and that it respects the Ableton terms of service, so your own installation files and activation details are what make it work. And the licence is LGPL-2.1, covering the runtime this project builds rather than Live itself. Where the README points elsewhere for depth, the documents exist: INSTALLER.md for the full command list, TROUBLESHOOTING.md for the NTSync and PipeWire checks, CHANGELOG.md for release notes, and BUILDING.md for the build.
Editorial conclusion
Use this runtime if you produce or perform with Live on x86-64 Linux and can meet the PipeWire 1.4.2 and Linux 6.14 NTSync floors without fighting your distribution. Pass if you need automatic updates, a Mac, or an Ableton Move workflow, since none of those are in the supported set. Before your first update, read the changelog entry, because a release can move a launcher default or require you to pick a renamed device again.
Frequently asked questions
How do I install Ableton Live on Linux?
Download the Live installation ZIP from Ableton.com, download install-ableton-latest.run, then double-click it or run sh ~/Downloads/install-ableton-latest.run install from a terminal. If you keep several Live installers, add --live-installer and point at the exact archive you want.
Is Ableton Linux compatible with my version of Live?
It covers Live 12 and Live 11 in the Intro, Standard, Suite, Lite and Trial editions, plus Cycling 74 Max 8, Max 9 and Max for Live, and Push 1, Push 2 and Push 3. Ableton Move is listed as coming soon, and Apple Silicon AArch64 support is experimental work in draft PR 259.
What does Ableton Linux need before it will install?
An x86-64 Linux system meeting Live's hardware requirements, glibc 2.35 or newer, PipeWire 1.4.2 or newer, Linux 6.14 or newer with active NTSync, GStreamer base and good plugin sets, and GNU coreutils with tar, zstd and flock. You supply the Ableton installation files and activation details yourself.
Does Ableton Linux update itself automatically?
No, and that is intentional so Live's own updater is left alone for privacy. You run sh ~/Downloads/install-ableton-latest.run update yourself, which applies the changelog entries and preserves your Live installation, authorisation and projects.
How do I uninstall Ableton Linux without losing my Live projects?
Run sh ~/Downloads/install-ableton-latest.run uninstall, which selects --keep-prefix and leaves the Wine prefix, Live, authorisation and installer settings alone. Uninstall --delete-prefix removes those too. Uninstalling asks about files that changed after installation, with Keep as the default answer.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/shibco-ableton-linux)Star history chart for your README
[](https://hysenlabs.com/projects/shibco-ableton-linux)Was this useful?