← BackFull Manual →

Automation & MIDI Control

Draw or record automation (or have the AI write it), and map hardware controllers with profiles, MIDI Learn and Lua.

Automation lanes in the MAGDA arrangement
An absolute Cutoff lane on Pad, and a clip lane on Arp holding three automation clips.

Every parameter MAGDA knows about, from track faders, pan and sends to any plugin parameter, can be driven two ways: by automation curves, or by hardware.

Automation lives in per-parameter lanes on the arrangement, with snap to time and value grids. There are four ways to get a curve onto a lane: draw it, record your moves in Write, Touch or Latch mode, or ask the AI agent, which understands shapes, ranges and bar counts and writes the curve onto the selected lane. A lane can also be clip-based: it holds automation clips, named and coloured, that you move, loop and duplicate like any other clip. Tempo and the master channel automate too, with hard-corner curves and a point inspector for typing exact values.

Controllers map in three layers. Profiles, small JSON files, bind a controller's knobs to the focused device's macros, so plugging in a Launchkey and focusing a Poly Synth maps its eight knobs at once, and they follow as you focus other devices. A profile can also point a control at the selected track's or the master's volume and pan. MIDI Learn is a right-click away on any plugin parameter, macro or modulator rate, and the bindings are saved with the project.

Lua scripts take over where a profile stops: modes that change with what MAGDA is doing, pads lit to match the session, faders and displays that want feedback. A script is a plain .lua file in a sandboxed Lua 5.4, with on_load(), on_midi(event) for every message from its input, and on_tick(dt) about 30 times a second. Through the magda.* API it drives the transport, launches clips and scenes, sets track volume, pan, mute, solo and arm, follows the selection, moves the focused device's macros, and sends notes, CCs and SysEx back to the controller.

Factory scripts cover the Novation Launchpad MK1 and MK2, the Launchkey Mini MK4, any 8-knob controller and a sustain pedal. Add one in Settings › Controllers › Lua Scripts, or drop your own into the scripts folder and press Reload to pick up edits without restarting. One script runs at a time, and owns the controller while it does.

Don't see your controller? Describe it to the AI panel with /controller and it writes a profile; share it on the community page so the next person with the same hardware doesn't have to.

The manual has the Controller Profile Format and Lua Scripting references.