How-to guides¶
Task recipes for driving Gloopy from code or hardware. Each assumes you've read The Gloopy model and done one of the quickstarts (Python or Common Lisp).
Available now¶
- Let an AI agent drive Gloopy (MCP) — expose the control API to an assistant over the Model Context Protocol.
- Write a script-clip generator — generate a clip's notes from Common Lisp or Python code, materialised or live-driven.
- Develop generators live in Emacs (Sly) — attach Emacs to the resident kernel and redefine generators without a restart.
- Live script clips from a Jupyter notebook — attach a notebook as Gloopy's live Python generator; redefine a cell and hear it next loop.
- Subscribe to the playhead and meters — a live push feed of transport position and levels, in Python, Lisp, and raw gRPC.
- Add and control effects from a script — put an effect on a track, set its parameters, bypass it, or host a plugin — Python, Lisp, and grpcurl.
- Play Gloopy live over OSC — fire notes, sweep knobs, and drive the transport in real time from Common Lisp or any OSC sender.
- Bulk-import a generated MIDI sequence — hand Gloopy a whole part as JSON in one call.
- Bind a hardware knob to any parameter (MIDI-learn) — map a CC or OSC source to any parameter, scaled and invertible.
- Render export profiles from a script or CI — named, repeatable bounces (mix / range / track / stems).