Professional · Production Tooling · FMOD Studio 2.02 scripting + JavaScript

FMOD Build Validation Tool

Production FMOD validator used by the audio team to catch routing and naming errors before Build Banks.

A validation failure blocks the bank build and lists both a routing and a naming problem before any bank is generated.

What I designed

  • Identified the recurring production problem
  • Defined the validation rules
  • Designed the validated bank-build workflow
  • Designed the desired error / feedback behaviour
  • Directed implementation
  • Reviewed and understood the script
  • Debugged validation and build behaviour
  • Tested pass / failure cases
  • Integrated the validator into the production workflow
  • Iterated based on day-to-day team use

What it checks

Direct-to-Master routing. Events routed directly to the Master Bus can bypass the intended group/bus structure and processing, making levels, effects and broader mix behaviour less consistent and harder to maintain.

Spaces in event names. Event names containing spaces can create problems for scripts, automation or external tools that rely on predictable naming conventions.

Each check runs and reports independently — fixing one doesn't hide the other.

Each check runs independently — fixing the routing issue doesn't hide the separate naming issue still being flagged.

Build Banks (Validated)

Fail

  1. Block build
  2. Show offending events + correction guidance
  3. Fix and retry

Pass

  1. Bank build proceeds normally
The validator writes a short [Validation] note directly onto the offending event, turning a failure into a specific next action.

Validation note

Beyond a pass/fail result, the validator reports an issue category and the affected event path, selects the offending events in FMOD, and writes a short [Validation] note directly onto the event with correction guidance — clearing any prior validation note before writing the current result.

Team use

The validator was deployed to the project's audio team of around 2–3 sound designers. It regularly caught routing and naming issues during bank builds that would otherwise have needed manual checking. It became part of the team's regular bank-build workflow.