Remote development and performance

Studio accepts connections from development tools on the same machine. This page covers them, along with Studio’s runtime requirements and preparing for a performance.

Alongside the language, audio backend, native canvas, and sample tools, the Studio launcher includes two separate development interfaces: SLYNK and a local MCP server.

The MCP server exposes inspection and structured session operations. Session mutations are marshaled onto the session thread. Unrestricted Lisp evaluation is off by default and must be explicitly enabled.

Studio renders with OpenGL 4.1 core and GLSL 410. The language and the non-GL editor model are separable from the renderer.

Native GLFW/OpenGL libraries are required for Studio, along with libffi and font libraries; see Installation and setup. SuperDirt, audio capture, MIDI devices, and optional model services each have their own setup:

• SuperDirt: From pattern to audio
• Audio capture: Machine listening
• MIDI devices: MIDI and other outputs and Inline controls
• Optional model services: Generation and neural instruments and Learned search

Studio supplies mechanisms for guarded reload (Cmd+Shift+R), state restoration, error containment, and cached rendering. Before a show, rehearse the score you will play with its sample library, devices, audience output, and resolution.

On macOS, ,syphon on publishes the composited Studio window, code and visuals together, as MoraCanvas for a Syphon receiver, such as a projector display. It carries video only.