Automation & MIDI Control
Drive any parameter — draw or record automation curves (or have the AI write them), and map hardware controllers via profiles, MIDI Learn, and Lua.
Every parameter MAGDA knows about — track faders, pan, sends, 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 and live playback during transport. Four ways to get a curve onto a lane: draw it directly, record your moves with Write, Touch, or Latch mode, or ask the AI agent — it understands shapes, ranges, and bar counts and writes curves straight onto the selected lane. Full undo across draw, record, and AI passes.
Controllers map in three layers. Profiles — small JSON descriptions — bind a controller's knobs to MAGDA's focused-device macros, so plugging in a Launchkey and focusing a 4OSC maps the eight knobs instantly, and they follow as you focus other devices. MIDI Learn is a right-click away on any plugin parameter, macro, or LFO Rate slider, with bindings that persist with the project. And a sandboxed Lua 5.4 scripting layer drives two-way DAW protocols — pad grids that light up, transport feedback — via on_midi(event) and the magda.* API. Examples for Launchpad, Launchkey Mini MK4, and a foot-pedal template ship with the source.
Don't see your controller? Describe it to the AI panel with /controller and it generates a profile; share it on the community page so the next person with the same hardware doesn't have to.
- Automation lanes per parameter, with time and value snap
- Draw, record (Write / Touch / Latch), or AI-generate curves
- Controller profiles map hardware to focused-device macros
- MIDI Learn on any plugin parameter, macro, or modulator rate
- Lua 5.4 scripting for two-way DAW protocols
- AI-generated profiles via /controller, shareable on the community page