A good ting is not just a bell. It is a controlled transient plus a decay that either clears fast for interface feedback or lingers slightly for chimes. Use prompts to lock in pitch, brightness, and tail length, then choose close or distant room feel based on whether the sound is meant to feel on-device, in a hallway, or in a real space on camera.
Match the transient to the action
For buttons, confirmations, and pickup cues, you usually want an immediate attack that reads as a single event. For foley like a desk bell press, a tiny mechanical click before the ring sells realism.
- Use words like sharp attack, clean transient, tight peak
- Ask for a click then ring when syncing to a visible press
- Avoid prompts that imply long swells for short UI taps
Control pitch and brightness for the mix
High bell pings can feel premium but can also become piercing on headphones. Mid pitch tings often sit better under dialogue. Prompt the tone so it does not compete with sibilance or music cymbals.
- Try medium-high pitch, not piercing, controlled highs
- Request reduced harsh overtones or slightly damped tone
- If it masks speech, regenerate with less brightness
Decide on tail length and space
Tail length is the main reason a bell feels like UI vs a real location. Short tails are safer for repeated triggers, while longer decays help sell distance and architecture like hallways or lobbies.
- For UI: short decay, dry, minimal room tone
- For scenes: longer decay, light reflections, subtle room tone
- If repeated often, choose tighter tails to prevent buildup
Build useful sequences without clutter
Two-note and three-hit patterns are common for elevator cues, correct answers, and countdown markers. Keep spacing and level consistent so editors can align to frames without manual cleanup.
- Specify the pattern: two-note chime, three evenly spaced hits
- Ask for consistent loudness and the same pitch each hit
- Avoid overly wide stereo if the cue must feel centered
