Control & scripting¶
For integrators, script authors, and hardware vendors. Gloopy exposes everything it can do over a control API so external programs can build, edit, perform, and render compositions.
Read this first¶
Everything here assumes the shared vocabulary and, especially, the two-lane control model:
The short version: gRPC is the structural, scheduled lane (build and edit the
composition, query state, render); OSC is the live, low-latency lane (play
notes, turn knobs, start/stop). gRPC creates the stable ids; OSC performs on
them. See the two control lanes.
Get moving¶
Drive Gloopy from Python Drive Gloopy from Common Lisp
This section¶
- Concepts — the domain model and the two control lanes, defined once, language-agnostic. Every reference page links here.
- Tutorials — end-to-end lessons, in Python and Common Lisp.
- How-to guides — task recipes: let an AI agent drive Gloopy, or subscribe to the playhead and meters.
- Reference — the interfaces themselves: gRPC · OSC · Python · Common Lisp.
- Explanation — why two protocols instead of MIDI-only.
Endpoints at a glance¶
| Lane | Endpoint | Transport | Use for |
|---|---|---|---|
| gRPC | 127.0.0.1:50051 |
TCP, request/response + streams | structure, edits, queries, render |
| OSC | 9000 |
UDP, fire-and-forget | live notes, knob moves, transport |