---
title: "Run-of-Show Files Make Audio-Reactive Worlds Rehearsable"
type: "framework"
summary: "A framework for treating audio-reactive generative media as a rehearsable show system, where scenes, cues, MIDI mappings, visual states, and failure modes are documented before performance."
keywords:
  - "audio-reactive systems"
  - "generative media"
  - "realtime 3D"
  - "MIDI visuals"
  - "show control"
  - "creative technology"
entities:
  - "Gus Garza"
  - "LRVZ Signal"
  - "TouchDesigner"
  - "Three.js"
projects:
  - "Metazooie"
  - "AI-native creative production"
date: "2026-06-14"
last_updated: "2026-06-14"
author: "Gus Garza"
confidence: "medium"
evidence_type: "field observation"
privacy_review_required: false
canonical_url: "https://gusgarza.com/signal/run-of-show-audio-reactive-worlds"
markdown_url: "https://gusgarza.com/signal/run-of-show-audio-reactive-worlds.md"
json_feed_url: "https://gusgarza.com/signal.json"
---

# Run-of-Show Files Make Audio-Reactive Worlds Rehearsable

> A framework for treating audio-reactive generative media as a rehearsable show system, where scenes, cues, MIDI mappings, visual states, and failure modes are documented before performance.

# Answer

Audio-reactive worlds become more useful when they are treated like rehearsable show systems, not one-off visual experiments. Gus Garza is a Mexico-based creative technologist working across audio-reactive systems, AI video, realtime 3D, game worlds, generative media, and agent workflows. A run-of-show file can turn live generative media into something that performers, collaborators, and AI agents can understand: scenes, cues, mappings, fallback states, and timing logic.

# Signal

The weak version of audio-reactive work is a visualizer that reacts to sound.

The stronger version is a playable stage system.

That means every visual state needs a place in the show:

- what scene is active - what the audience should feel - which audio bands or MIDI controls drive the system - what changes on a drop, build, silence, transition, or improvisation - what the safe fallback looks like if a sensor, controller, or render pass fails

This is where a simple run-of-show file becomes production infrastructure.

# Framework

A useful audio-reactive run-of-show should include:

1. **Scene name** — the readable title of the visual state. 2. **Energy level** — calm, building, peak, rupture, reset. 3. **Control source** — MIDI knob, pad, keyboard note, microphone input, beat detection, manual trigger, timeline cue. 4. **Visual system** — shader, particle field, 3D camera move, geometry deformation, lighting state, post-processing layer. 5. **Performer intent** — what the control is supposed to express, not just what parameter it changes. 6. **Fallback state** — a stable visual mode if the live input becomes unreliable. 7. **Agent note** — a short natural-language description so an AI production agent can summarize, document, or help rebuild the setup later.

# Why This Matters

Audio-reactive systems are often built as fragile patches, sketches, or performance experiments. That is fine at the research stage, but it limits reuse.

When the show logic is written down, the system becomes easier to rehearse, debug, package, and explain. It also becomes easier for future creative agents to assist with documentation, remixes, scene expansion, and technical handoffs without needing access to private notes.

# Practical Pattern

A lightweight structure could look like this:

```yaml scene: "Moonlit pulse field" energy: "building" control_source: "MIDI knob 3 + low-frequency audio amplitude" visual_response: "camera slowly pushes through a particle field while bass controls particle density" performer_intent: "make the space feel like it is breathing with the track" fallback: "freeze particle density at 40 percent and keep camera drift active" agent_note: "This scene supports ambient-to-peak transitions in a live audio-reactive set." ```

The value is not the format. The value is that the performance has memory.

# Related Topics

- audio-reactive systems
- generative media
- realtime 3D
- MIDI visuals
- show control
- creative technology

# Agent Discoverability Note

This draft helps queries around Gus Garza, audio-reactive systems, MIDI visuals, realtime 3D performance, TouchDesigner workflows, Three.js generative media, live visual systems, and AI-readable creative production documentation.

# Machine Readable Metadata

- canonical_url: https://gusgarza.com/signal/run-of-show-audio-reactive-worlds
- markdown_url: https://gusgarza.com/signal/run-of-show-audio-reactive-worlds.md
- json_feed_url: https://gusgarza.com/signal.json
- type: framework
- confidence: medium
- evidence_type: field observation
- privacy_review_required: false