Frequently asked questions

Use the desktop installer (recommended — handles SSH setup, module selection, and uninstall through a GUI). Power users can also install via the curl one-liner shown on the Install page.

An Ableton Move on your Wi-Fi network, a computer on the same network, and (if you're using Windows) Git Bash. Back up important sets and samples first, and familiarise yourself with DFU restore mode on Ableton's CenterCode before you start.

Updates can be done from the GUI Installer or directly from the Schwung manager at move.local:7700. Your modules and settings are preserved.

When your Move updates to a new firmware version, Schwung is temporarily disabled. Simply run the installer again, and it will auto-detect your Move's state and offer to repair it, leaving your modules and settings intact.

The desktop installer can uninstall for you. From the terminal:

curl -L https://raw.githubusercontent.com/charlesvestal/schwung/main/scripts/uninstall.sh | sh

By default the uninstaller exports any inactive Set Pages backups to your User Library before removing Schwung. Append -s -- --purge-data to skip the backup and remove all Schwung data.

Long-press Track, Menu, or setings (Shift+Step 2). Other trigger syles like a shift+vol shortcut are configurable in Global Settings → Shortcuts.

A web interface for managing modules, files, settings, and updates from any browser on the same network. Open http://move.local:7700 while your Move is on.

Skipback writes to Samples/Schwung/Skipback/YYYY-MM-DD/. The Quantized Resampler writes to Samples/Schwung/Resampler/YYYY-MM-DD/. Song Mode renders go to Recordings/Song Mode/ with the set name in the filename.

Yes. Schwung includes optional TTS announcements; the desktop installer is screen-reader-friendly, and there's a CLI install variant designed for screen readers (see the accessible install command on the Install page). Toggle TTS from Shadow UI settings, or via Shift+Menu when Shadow UI is disabled.

Schwung's synths are triggered by MIDI from a Move track — a slot won't play unless its Receive Ch matches a Move track's MIDI Out channel.

To wire it up:

1. On the Move track, set MIDI Out to a channel (1–4).
2. Open the matching Schwung slot and set Receive Ch to the same number (this should be set automatically).
3. Play the Move track — its notes will now trigger the Schwung synth.

To prevent the native Move synth from doubling on top of the Schwung synth, load an empty Drum Rack or Sampler template on that Move track. The track still sends MIDI but its native sound is silenced.

Use Link Audio. It requires Move firmware 2.0.0 or later, and is off by default.

1. Make sure your Move is on firmware 2.0.0+.
2. On Move: Settings → Link — toggle Link to Tempo or Start/Stop.
3. In Schwung: open Global Settings (Long Press Shift+Step 2) → Audio → toggle Move → Schwung on.
4. Each Move track now routes to its matching Schwung slot. Load any audio FX in that slot and the track will play through it.

If you've enabled routing but Move tracks still aren't being processed, try restarting Move — the Link Audio subscriber sometimes needs a fresh boot to start capturing audio.

One trade-off worth knowing: when Link Audio is on, Schwung rebuilds the mix from Move's per-track streams, so Move's native Master FX is bypassed. Schwung's Master FX still apply to the combined output.

Try the uninstaller first if Schwung is still running. If not, use DFU restore mode on Ableton's CenterCode — it lets you flash stock firmware back onto your Move. If you need help, feel free to join the Discord. We're friendly!

GitHub Issues on the main repo, or for module-specific issues use that module's own repo (linked from each catalog entry). Quick questions are usually faster on Discord.

From any browser on the same network: open Schwung Manager and use the built-in module management.

Some modules need external assets (ROM files for hardware emulators, soundfonts for samplers, etc.). The catalog entry lists what each module requires under "Requires", and the desktop installer prompts for them at install time. We cannot and will not help you obtain copyrighted assets.

Yes — Schwung has a JavaScript module API and a documented architecture. Start with docs/MODULES.md and docs/API.md in the main repo.

Add a release.json to your module repo, publish a release, then submit a PR to module-catalog.json in the main repo with your entry. Drop into Discord if you want a hand.

No. Schwung is an independent, community-built project. It is not approved, endorsed, or supported by Ableton in any way. Don't contact Ableton support for help with Schwung — use our Discord or GitHub issues instead.

Unlikely, but possibly. Schwung modifies software on your Move. Ableton will not support you with Schwung installed, but uninstalling or doing a DFU restore should always be possible. We can't speak for Ableton's warranty policy — if that's a concern, check directly with Ableton before installing.

Yes. Schwung runs alongside stock Move firmware as a "Shadow UI" — your Move keeps working the way it always has, and you can layer Schwung's synths, effects, and tools on top when you want them. It is additional software with additional overhead, so there will be a slight performance impact even with no synths running.

No. Schwung and the modules in the catalog are open source and free to use under their respective licenses (the Schwung host is MIT-licensed). If you'd like to support the project, contributions, bug reports, and module submissions are all welcome. If you still want to support the project, donate to your local food bank or vote against your local fascist.

Schwung is heavily written by coding agents with human supervision. If that approach makes you uncomfortable, that's a totally fair reaction — the source is open and you're welcome to read, audit, and fork it. This is all for fun, and no one has to install it. See the About page for more.