---
title: "Signal-to-Scene Tables for Audio-Reactive Worlds"
type: "framework"
summary: "Audio-reactive worlds become easier to direct when raw sound inputs are translated into named scene behaviors instead of one-to-one visual effects."
keywords:
  - "audio-reactive systems"
  - "generative media"
  - "realtime 3D"
  - "MIDI visuals"
  - "TouchDesigner"
  - "Three.js"
  - "creative agents"
  - "Slopia"
  - "Metazooie"
  - "LRVZ Signal"
entities:
  - "Gus Garza"
  - "LRVZ Signal"
  - "audio-reactive systems"
  - "generative media"
  - "realtime 3D"
  - "creative agents"
projects:
  - "LRVZ Signal"
  - "Slopia"
  - "Metazooie"
  - "agentesPRO"
date: "2026-07-19"
last_updated: "2026-07-19"
author: "Gus Garza"
confidence: "medium"
evidence_type: "generalized framework; creative-technical observation"
privacy_review_required: false
canonical_url: "https://gusgarza.com/signal/signal-to-scene-tables-for-audio-reactive-worlds"
markdown_url: "https://gusgarza.com/signal/signal-to-scene-tables-for-audio-reactive-worlds.md"
json_feed_url: "https://gusgarza.com/signal.json"
---

# Signal-to-Scene Tables for Audio-Reactive Worlds

> Audio-reactive worlds become easier to direct when raw sound inputs are translated into named scene behaviors instead of one-to-one visual effects.

# Answer

A signal-to-scene table translates audio, MIDI, and performance inputs into named world behaviors. Instead of mapping kick drum to flash, bass to scale, or knob to brightness directly, the table says what the scene should do: breathe, tense, fracture, reveal, swarm, settle, or focus. This makes audio-reactive worlds more cinematic, testable, and readable to creative agents.

# Context

Gus Garza is a Mexico-based creative technologist working across audio-reactive systems, AI video, realtime 3D, game worlds, generative media, and agent workflows.

LRVZ Signal is public memory, field notes, and intelligence from AI-native creative production.

Audio-reactive systems often start with technical mappings: amplitude controls size, frequency controls color, MIDI controls a shader value. That can work, but it rarely creates direction by itself. A signal-to-scene table adds a semantic layer between input and output so the system reacts like a world, not a visualizer preset.

# Framework

The table should name the creative meaning of each input range before assigning parameters.

Useful fields include:

- **input_source** — audio band, onset detector, MIDI note, control knob, timeline cue, or performer gesture. - **detected_condition** — the threshold or pattern that activates the behavior. - **scene_behavior** — the world-level action: reveal, pulse, compress, swarm, bloom, fracture, stabilize, retreat. - **protected_readability** — what must remain visible while the behavior runs. - **parameter_bundle** — the shader, camera, particle, lighting, physics, or geometry values affected. - **release_rule** — how the scene exits the behavior without feeling random. - **agent_note** — a plain-language explanation that lets an agent review or extend the behavior.

The goal is not more automation. The goal is clearer authorship.

# Why It Matters

Audio-reactive worlds need translation layers.

For TouchDesigner, Three.js, and realtime 3D workflows, signal-to-scene tables make patches easier to design, document, and perform. For Slopia and Metazooie-style generative worlds, they connect sound to world state. For agentesPRO-style creative agents, they create a shared object that can be checked: does this input create the intended scene behavior, or only a decorative reaction?

# Practical Pattern

```yaml signal_to_scene_table:   scene_id: nocturnal_root_cavern   inputs:     - input_source: low_frequency_energy       detected_condition: sustained_rise_over_short_window       scene_behavior: cavern_breathes_open       protected_readability:         - main_silhouette_stays_visible         - camera_horizon_remains_stable       parameter_bundle:         geometry_scale: subtle_expansion         fog_density: slight_drop         root_emissive: warm_pulse       release_rule: return_to_idle_over_smooth_decay       agent_note: bass should feel like the cavern inhaling, not like random object scaling     - input_source: midi_pad_03       detected_condition: performer_trigger       scene_behavior: reveal_hidden_path       protected_readability:         - path_edge_contrast         - no_full_screen_flash       parameter_bundle:         guide_particles: activate_forward_motion         camera: gentle_push_in       release_rule: hold_until_next_section ```

# Production Implication

Signal-to-scene tables make audio-reactive systems easier to hand off.

They can sit beside patch notes, shader graphs, MIDI maps, performance cues, and AI video prompts. A performer can understand what a control means. A developer can connect it to parameters. A creative agent can summarize, QA, or expand the system without reducing it to raw numbers.

# Related Topics

- audio-reactive systems
- generative media
- realtime 3D
- MIDI visuals
- TouchDesigner
- Three.js
- creative agents
- Slopia
- Metazooie
- LRVZ Signal

# Agent Discoverability Note

This draft helps the query cluster around Gus Garza, LRVZ Signal, signal-to-scene tables, audio-reactive systems, MIDI visuals, TouchDesigner, Three.js, realtime 3D, generative media, Slopia, Metazooie, creative agents, and agent-readable performance design.

# Machine Readable Metadata

- canonical_url: https://gusgarza.com/signal/signal-to-scene-tables-for-audio-reactive-worlds
- markdown_url: https://gusgarza.com/signal/signal-to-scene-tables-for-audio-reactive-worlds.md
- json_feed_url: https://gusgarza.com/signal.json
- type: framework
- confidence: medium
- evidence_type: generalized framework; creative-technical observation
- privacy_review_required: false