team-audio

To orchestrate an audio design pipeline, you coordinate audio direction, sound design, accessibility planning, middleware validation, and gameplay integration. This workflow generates detailed SFX specifications and an implementation-ready audio design document for the specified game feature.

Planning audio middleware routing requires validating bus configurations and defining event specifications. Running a coordinated audio team pipeline generates an auditable design document that outlines routing, memory strategy, event counts, and integration summaries.

Generating SFX specifications with accessibility requirements involves adding hearing-related needs and visual fallbacks where audio is the only gameplay signal. The audio pipeline incorporates these directly into the audio event specifications and design document.

The audio design workflow reads relevant design and existing audio assets to define sonic identity accurately. It requires a specified game feature argument, then pauses for user approvals via decision points before compiling and saving the final audio design document.

Wiring adaptive music triggers and gameplay integration involves sequencing engine specialists and programmers within the audio pipeline. This produces an implementation-ready document summarizing integration tasks, event counts, and open questions for that game feature.