BGC: NOTES
Soundworks

BGC: NOTES / Sound in Use

Sep 29, 2026Sound in Use5 min read

Waiting sound cannot shorten time, but it can reduce uncertainty

As processing grows longer, the screen shows progress while the ear asks whether the system is still alive. Good waiting sound does not hurry impatience; it gives motion to time.

In Brief

Sound during a process is not decoration that fills a gap. It is an interface that translates beginning, continuation, and completion at different densities.

Silence sounds like space only when it is brief

When the screen stops changing during an export, payment confirmation, or image generation, it becomes difficult to tell processing from failure. Sound does not need to calculate the remaining time. It needs to communicate two states: the request arrived, and the process continues. A short, firm attack can mark the arrival of the action, followed by a softer texture that leaves the system in motion. Give both moments the same timbre and weight, and the confirmation cue immediately becomes an insistent repeating cue. Separate their density, and the listener does not need to keep checking the screen. Waiting sound is not music tasked with making time entertaining; it is an interface for keeping uncertainty small. The first question is therefore not “what should we play?” but “which state is the listener beginning to doubt?”

Design the expression of a cycle, not just a loop

The longer a wait lasts, the more clearly a perfectly seamless short loop exposes its boundary. It may feel rhythmic for two or three passes, then begin to suggest that the system is trapped in place. The answer is not automatically a longer piece of music. Keep the central pulse interval stable while slightly changing attack, brightness, or tail length on each pass, and time begins to read as progress rather than repetition. A low body can stay fixed while a high particle arrives one cycle later; the last of four pulses can open a slightly longer tail to breathe into the next group. The change should not be large enough to demand melodic memory, but it must be present enough to avoid sounding static. In the mix, clear a path through the midrange and round the transient instead of solving presence with level. Once waiting sound moves to the foreground, the user starts counting repetitions instead of trusting the process.

Completion needs a different motion, not merely a louder sound

The common choice at the end of a process is a completion cue that is higher, brighter, and louder than the waiting sound. After a long wait, however, the ear has adapted to the repeating pattern. What matters now is a change in the direction of motion, not the size of the celebration. A circling pulse can land, an open filter can close, or a texture moving across the stereo field can gather in the center. Each makes the transition legible at a modest level. Failure can follow the same principle. Instead of making a dark copy of the success sound, interrupt the ongoing phrase, leave a short gap, then place a low cue that waits for the next action; the relationship between failure and retry becomes audible. Sound should not carry all information alone. The same state must remain clear through screen and haptics when audio is muted, the environment is noisy, or hearing differs. Product sound is not the only guide—it speaks the same sentence as the other senses. A good completion cue does not shout “well done”; it briefly gives permission to move on.