Skip to content

Sound files

Every sound spot, ambient zone, and entry/exit/maintenance zone can have one or more sound files. This page covers the upload flow, the per-place library, and how localised files work.

Uploading a sound file

You can upload from several places, all of which queue the same shared upload pipeline:

  • The spot's Sound files section — drag a file in, or click to pick from disk.
  • The library dialog — click Upload and select files; they're added to the library without being assigned to any spot.
  • Drop a file onto the cue list — the admin offers to either create a new spot for that file or assign it to an existing one.

The admin shows a small badge while uploads are running, and surfaces the queue so you can cancel anything that's still pending.

The per-place sound file library

Every place has a library of audio files that have been uploaded to it. The library tab on a spot's sound file slot lets you pick an existing file instead of re-uploading the same audio.

The library shows:

  • Original file name
  • File size
  • Duration
  • When it was last used in a published version
  • Which published version that was

This makes it easy to spot files that are no longer referenced and can be cleaned up.

Sound slots on a spot

A spot can have a main sound file plus optional ambient files. Each slot supports:

  • Fade in / fade out — milliseconds. Useful for smooth transitions between ambients.
  • Delay — wait this many milliseconds after the trigger fires before starting the file.
  • Play once — the file fires only the first time the spot is triggered (until the listener resets the place or starts a new session).
  • Keep playing after main file — for ambient slots, keeps the audio going after the main file finishes.
  • Synchronise — for group-sync setups, requires the audio to align with the group's timeline.
  • Volume offset — dB adjustment relative to the place default.

Localised sound files

If your place has multiple languages configured (Settings → Languages), each sound slot can have a default file plus optional localised files per language code. The mobile app picks the localised file if available, otherwise falls back to the default.

To add a localised version: open the slot, click Add localised version, pick the language, and upload or select from the library.

Backwards compatibility

Some older Android clients expect a flat soundFiles[] list with one entry per language. The backend continues to emit that shape from the localised model so that clients on older app versions keep working without re-publishing.