A few shared ideas
The same scene concepts connect the integrations, while each runtime has a specific set of capabilities.
Read as MarkdownScene, hosts, events and controls
- scene.satie describes the sounds: recordings, timing, levels, placement and acoustic behavior.
- A host is a real object or node in your project. Stable host IDs let a sound follow the right object as the scene changes.
- An event is something that happened: a door opening, a contact or a trigger. Send it from the actual gameplay callback.
- A signal is a continuous value, such as speed or engine load. A state selects a scene mode. Their names and ranges come from the scene contract.
- samples.json names the recordings. Keep the referenced files and their attribution with your release.
If a sound is silent
- Check that its recording loaded. In a Lens, check Tracks; in Unity, check the compiled scene and supported native library; in a browser, check the Start sound gesture.
- Check that the source is unmuted and its event has fired. A recurring one-shot may simply be between events.
- Check controlling signals and states before turning up the volume. A zero control or inactive state can intentionally keep a source silent.
- Check the listener, host binding, distance and scale. Move near the intended source and read the runtime’s warnings.
Capabilities differ by platform
The web runtime, Unity’s portable core and the Godot/Lens placement loaders are different playback paths. Always read notCarried in a native export before assuming a browser scene sounds identical in another engine.
Unreal, Roblox and other native engines do not currently have a maintained Satie install path in this release. They need a custom integration; the browser runtime is not a drop-in native plug-in.
Portable core reference · Full MCP reference