Music

The Music tab plays the game's scores through the game's own music director: you hear each state's mix as the player will, and mute or solo stems, without writing anything.

What you get

A score heard state by state, on the bar the game would change it, with the bar and beat shown as it plays; and the list of the music and sounds the game declares, with those still missing.

Context and versions

The local Studio (engine repository or created project) and the demo Studio. True from 4.2.1. How scores, states and stems are written: Music in stems.

Prerequisites

• The Studio running (overview).
• A game with scores (audio.scores in game.ts) and their prepared files (npm run assets).

Where to run the commands

In the browser, on the Music tab.

Steps

1. Pick a score and play it.

2. Choose a state: its mix is heard on the next bar, as in the game.

3. Mute or solo a stem by hand to hear what each one brings. The bar and the beat show where the music is.

Music and sounds in the Studio and the tools

The Assets tab lists the music and sound ids the game declares and whether a file exists for each, with a player per file (Assets and cutting); npm run assets ships what is there and reports what is missing. The MCP read_doc tool serves the audio pipeline's page as AUDIO (MCP tools).

Expected result, and how to check it

Switching state changes the mix on the next bar; the stems you mute fall silent.

Common errors

Symptom	Cause	Fix
A score is silent	Its files are not prepared	npm run assets, then reload
A sound id shows no file in the Assets tab	It is declared but not made yet	Add it (Sound effects)

Files or data changed

None.

References

• src/studio/music.ts (through the game's director, src/engine/dom/director.ts).
• Music in stems, Audio toolchain.