quest'n'click 4.5.0 · r1

Built for quest'n'click 4.5.0, revision r1. Whether it is published, and which one is current, is recorded at publication.json.

Music

Français · Type: how-to · Audience: author · Context: local Studio · Status: ready · Applies from: 4.2.1

The local Studio · contract: stable · verified by CI (support matrix of 4.4.0, 2026-10-23): Chromium end to end (the Studio's checks); Windows: the unit suite only · automated checks: jobs e2e, windows; CI plan e2e, windows; 2 test files · people's passes: studio-hero-matrix not run (#238) · known limits: music-read-only

Voices and music · contract: stable · verified by CI (support matrix of 4.4.0, 2026-10-23): The music director in Chromium and WebKit · automated checks: jobs e2e; CI plan e2e; 2 test files · people's passes: voices-listening not run (#87) · known limits: music-read-only

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

Where to run the commands

In the browser, on the Music tab.

Steps

  1. Pick a score and play it.
  1. Choose a state: its mix is heard on the next bar, as in the game.
  1. Mute or solo a stem by hand to hear what each one brings. The bar and the beat show where the music is.

Limit · music-read-only Nothing is written: a score's states are content in game.ts (audio.scores), edited with the rest of the game.

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

SymptomCauseFix
A score is silentIts files are not preparednpm run assets, then reload
A sound id shows no file in the Assets tabIt is declared but not made yetAdd it (Sound effects)

Files or data changed

None.

References


Edit the source of this page · Report an error