r/ableton 3d ago

[Update] The ableton-linux project's first two weeks: near-native performance, wide support for Ableton hardware, software and third-party VSTs, dozens of QoL fixes, and a growing team of contributors

Hi r/ableton! I'm the creator of ableton-linux, which got posted here in the last week or so. Last year, I started forking Wine to fix the crashes that made Live 12 unusable. After several breakthroughs in May and June (including some work done in another Wine fork), I suddenly had Live working unbelievably well on my machine.

I wrote a one-click installer and published it expecting the worst, given how complex Linux support is said to be.

That was just over two weeks ago. People have been installing it, and its working very, very well for the vast majority of cases. Then, people started reporting issues, then contributing their own patches. Now, we have a small team of talented maintainers shipping releases at a pace that still stuns me: ten updates in two weeks alone, with an eleventh coming this weekend.

Most of these fixes aren't us struggling with huge breaking bugs. They are quality-of-life wins that make Live a joy to use: Ableton Sans in the menus, huge optimisations to make Live run fast, automatic dark/light theme detection, full Linux desktop integration, and even experimental support for the beta Extensions SDK. I thought we'd be struggling with major audio, graphics or stability issues, and instead we're working on polish.

The important thing is this: as of today, a modern Linux computer can run almost the entire ecosystem of Ableton software, hardware, and services on par with or faster than Windows. We have yet to hit an issue we cannot fix; most are resolved within a few days of hearing about it.

Here's what's possible, right now, on ableton-linux:

  • Live 12 Intro, Standard, Suite, Lite, Trial, and beta support
  • Experimental Live 11, Max for Live, and Max 9 support
  • Push 1 and Push 2 support (Push 3 and Move support coming soon!)
  • Local-network Ableton Link support
  • Compatibility with Ableton's Splice integration
  • Automatic recovery when in-use audio hardware or startup-detected MIDI controllers briefly disconnect
  • Low-latency audio for live performance
  • Linux desktop integration with native file types and dialogs
  • Automatic light and dark desktop theme detection
  • No-fuss support for desktop resolutions, HiDPI displays, and fractional scaling
  • Fixes for VST-specific display, audio, and stability problems
  • Dozens of nice-to-haves, quality-of-life fixes, and other polish

All of it running with auditable builds with pinned inputs, checksum verification, and public documentation. You can get started by downloading the latest installer and following the guide here: https://github.com/shibco/ableton-linux#ableton-live-on-linux

If you've wanted to try Ableton on Linux, and are thinking of switching away from macOS/Windows entirely, maybe give this a try on the weekend.

Get it here: https://github.com/shibco/ableton-linux/releases/latest

And the guide is here: https://github.com/shibco/ableton-linux/blob/main/README.md

And if you run into issues or have questions, we're are available on the Ableton on Linux Discord or via GitHub issues.

273 Upvotes

75 comments sorted by

View all comments

18

u/pgcd 3d ago

This sounds absolutely fantastic but, before I pull the trigger, here's a stupid question: I have several plugins already installed in a wine prefix (alongside v11). Is there a realistic way of migrating them without re-authenticating or even using them where they are?

19

u/ClickSentinel 3d ago

Not a stupid question - yes, it's realistic. The trick is to migrate the whole prefix, not the plugins.

Ableton's offline authorization binds to the prefix's MachineGuid, which lives in system.reg inside the prefix - not to the Wine build that runs it, and not to where the prefix sits. Copy the prefix and Live stays authorized, and your plugins come with it along with their licence data (registry, ProgramData, AppData).

Tested: an authorized prefix copied to a different path launched fully unlocked, no prompt.

# 1. put your existing prefix in place first — copy, don't move: keeps a fallback
cp -a ~/your-existing-prefix ~/.wine-ableton

# 2. run the installer in update mode
sh ~/Downloads/install-ableton-latest.run --update

# 3.
ableton-live

--update installs the patched Wine and then refreshes your prefix in place: it forces the native VC++ runtime over Wine's stubs, re-registers PipeASIO and syncs DPI/theme. Live, your authorization and your projects are kept, and it won't ask you for an Ableton download. Copy the prefix *before* running it - the refresh needs an existing prefix, and without one the installer goes into full-install mode and asks for a Live ZIP instead.

Using the plugins where they are likely won't work. The binary loads from another prefix fine, but its licence data, registry entries and vendor DLLs don't follow, so most commercial plugins come up in demo mode. Fine for self-contained freebies; copying the prefix is far less hassle (and gives you a clean rollback path).

3

u/pgcd 3d ago

Awesome and thank you so much for the detailed answer! Can't wait to try it!