DAW extensions

Extensions

An extension works inside your DAW itself, not on a single track. It can add its own panel, read your session and change it, so it feels like part of the software.

More DAWs now publish an SDK for building them. Wherever one does, we will build for it.

Installing

How to install
an extension

REAPER

  1. In REAPER, choose Options › Show REAPER resource path in explorer/finder.
  2. Open the UserPlugins folder inside it.
  3. Copy the extension file in: a .dylib on macOS, a .so on Linux or a .dll on Windows.
  4. Restart REAPER. Extensions load at startup, so a restart is always needed.

SWS has installers for Windows and macOS that do this for you, and ReaPack can install many extensions from inside REAPER. On macOS, if REAPER says an extension could not be loaded, macOS may have blocked the downloaded file: allow it under System Settings › Privacy & Security, then restart REAPER.

To uninstall an extension, quit REAPER, delete its file from UserPlugins and start REAPER again.

When they launch, our own extensions install with ReaPack from the Kerf Audio repository, https://raw.githubusercontent.com/Kerf-Audio/reapack/main/index.xml, and need REAPER 7.8 or later, 64-bit.

Ableton Live

  1. Download the extension’s .ablx file.
  2. In the Live 12 Suite beta, open Settings › Extensions (Preferences › Extensions on some systems).
  3. Drag the .ablx file onto the panel.
  4. Restart Live if it does not appear straight away. Live loads extensions when it starts.
  5. Right-click the kind of item the extension works on, such as an audio clip, and choose it from the menu.

Not in the menu? Most extensions work on one kind of item, for example audio clips or MIDI clips, so they only appear when you right-click that kind. If an extension does not load at all, check that Developer Mode is off in the Extensions settings, and try turning other extensions off for a moment: the beta can struggle to load many at once.