▣
module · drop-in viewer
state
What the mix knows about itself, in a place a query can reach.
by·posted 1mo ago
What it does
sound.state
What the mix knows about itself, in a place a query can reach.
A component's locals are closed to anything outside it, so everything a reader needs in order to check Hollowbell's sound lives here instead: which clips baked, what each one measured, which bed is playing, which lines have a voice, and any name a slice asked for that the library could not answer.
local State = require("sound.state")
State.summary()
-- { clips = 34, beds = 8, voices = 10, reported = 52,
-- suspiciouslyShort = {}, bake = { ... }, now = { bed = "belfry", ... },
-- unanswered = {} }
| field | what it holds |
|---|---|
clips | sound name -> AssetRef<soundClip> |
beds | bed name -> AssetRef<soundClip> |
voices | Hollow.LINES key -> AssetRef<soundClip> |
report | name -> what audio.info read off the payload: codec, sample rate, channels, frames, duration, plus the peak and RMS measured before encoding, and for a bed its loop-seam ratio |
now | the bed playing, whether it is mid-crossfade, whether the ambience is up, whether the mix is ducked, and which line is being spoken |
levels | the six channel levels as last applied, and the current duck |
bake | how many of each baked, how long it took, and any layer that failed |
unanswered | a name played that no clip answered, and how often |
aliased | a name outside Hollow.SOUND_NAMES and the clip that stood in for it |
crowd | how many one-shots piled up at once, and the gain the mix pulled the last one down to |
unanswered is the one to read first: empty means every sound the game
played was heard. Anything in it names either a missing recipe or a call
site playing a name the vocabulary does not carry.
Discussion
Scoped to this part · feeds back into the world's score.
Sign in to post.sign in
No comments yet. Be the first.