Atlas node · Scenes / Systems · working prototype

live-rig

Performance system that coordinates audio, control, and video as one rig with explicit setup, recovery, and validation logic.

Repository →

What keeps the scene recoverable

live-rig treats performance as a system that must survive contact with the room. Audio, control, and video become one scene only when setup, recovery, and validation are visible enough to be rehearsed.

A rig is not just what works when everything is calm. It is also the map of what can be checked, restarted, rerouted, and trusted when the room is already moving.

Runbooks, preflight notes, scene files, and validation tooling turn the rig from private operator memory into a shared operating surface.

The public page should stay redacted and method-facing. It can show the recovery logic without exposing private machines, venues, networks, or people.

What it is

live-rig is a documented hybrid scene system for audio, video, MIDI, and OSC. It matters publicly as a field manual and operational topology, not only as a one-off performance setup.

What it lets people do

It lets performers and maintainers coordinate media lanes, preflight a setup, and recover from failure without treating the rig as private operator folklore.

What is public now

  • Project repo Current runbooks, preflight notes, scenes, and validation tooling.
  • Source evidence already surfaced Repo docs support cautious architecture and runbook claims while the public-safe routing capture is still missing.

Evidence status

Status: working prototype. The public repo supports field-manual and validation claims, but a public-safe routing diagram or setup capture is still needed before the page should sound more field-tested than it is.

Next proof object: Redacted routing diagram or short setup tour using generic endpoint names instead of venue-specific or private infrastructure details.

Boundary note

This project should be shown as a documented performance method without exposing private machine names, network details, venues, or personnel.

What remains unresolved

  • The page should not imply every configuration is reproducible from public material alone.
  • A redacted visual proof object is still missing.
  • The minimal-rig versus full-rig story is not yet surfaced clearly in public.

Methods surfaced

Proof objects

  • Project repo documentation Status: public. Runbooks, preflight notes, scenes, and validation tooling are public now.
  • Public-safe routing diagram or setup tour Status: needed. Still needed before the page should imply stronger field use than the current public proof supports.
  • live-rig-control The control-layer companion that makes the larger rig intelligible and operable.
  • MOARkNOBS-42 A flagship instrument that can feed directly into the rig’s control language.
  • drone-chorus Extends the same control and performance questions into telemetry-driven systems.

Source trail

  • Project repo — Implementation truth.
  • Last reviewed: 2026-05-15

The Atlas is the relationship layer. Use the repository for current project-specific truth, and use studio-notes when methods, decisions, or teaching material need to travel across the fleet.

Where to go next