AudioIntermediate

Audio Muffle

A low-pass filter swallows the highs — the world sounds like it's behind a wall, underwater, or inside a pause menu.

audiofilterlow-passmixing

Examples

Captured from this page's own interactive demo below.

Overview

Ducking turns the volume down; muffling changes where the sound IS. Sweep a low-pass filter over the mix and the high frequencies vanish first — exactly what physics does to sound behind a wall, under water, or through the ringing ears of a stunned soldier. The brain decodes it instantly and for free: the action is still happening, but you've been moved away from it.

The classic use is the pause menu: gameplay audio dives to a cutoff around 600–1000 Hz while menu clicks stay crisp on an unfiltered bus, making the pause feel like stepping into a soundproof booth with the game visible through glass. The same move sells underwater sections, flashbangs, near-death states, and interiors heard from outside.

Always sweep the cutoff, never snap it — 100–300 ms from 20 kHz down reads as a smooth dive; an instant switch reads as an audio glitch. And route it on the mixer, not on individual sources: one filter on the gameplay bus muffles a thousand sounds coherently, while per-source filters drift apart and triple your DSP cost.

Interactive Demo

press Play to start the musiclowshighs

684

10k

Cutoff800Hz

Sweep Time250ms

Use Cases

Pause and inventory menusUnderwater sectionsFlashbang and stun statesMuffled combat behind walls and doors

Best Practices

Do

✓Sweep the cutoff over 100–300 ms — a dive into the muffle, not a switch flip.
✓Filter the gameplay bus on the mixer and leave UI sounds on a clean, unfiltered bus.
✓Compensate with a slight volume lift if the muffled state lasts — low-passed audio also reads as quieter.

Don't

✕Don't snap the filter in one frame; an instant spectrum change reads as broken audio, not a state.
✕Don't muffle sounds the player must still react to — danger cues should cut through or be re-routed.
✕Don't stack a muffle on top of heavy ducking; taking both the highs and the volume leaves nothing to hear.

Common Mistakes

⚠Filtering every AudioSource individually instead of the bus — expensive, and the sources sweep out of sync.
⚠Forgetting to release the filter on unpause, leaving the whole game sounding underwater until restart.
⚠Muffling the music along with the SFX when the design brief was 'the world recedes, the score stays with you'.

Implementation

Paste this into your AI assistant (Cursor, Copilot, Claude) to add the effect to your project.

Prompt

Add the "Audio Muffle" game-feel effect to my project: A low-pass filter swallows the highs — the world sounds like it's behind a wall, underwater, or inside a pause menu.

How it works: Ducking turns the volume down; muffling changes where the sound IS. Sweep a low-pass filter over the mix and the high frequencies vanish first — exactly what physics does to sound behind a wall, under water, or through the ringing ears of a stunned soldier. The brain decodes it instantly and for free: the action is still happening, but you've been moved away from it.

Guidelines:
- Sweep the cutoff over 100–300 ms — a dive into the muffle, not a switch flip.
- Filter the gameplay bus on the mixer and leave UI sounds on a clean, unfiltered bus.
- Compensate with a slight volume lift if the muffled state lasts — low-passed audio also reads as quieter.

Avoid:
- Don't snap the filter in one frame; an instant spectrum change reads as broken audio, not a state.
- Don't muffle sounds the player must still react to — danger cues should cut through or be re-routed.
- Don't stack a muffle on top of heavy ducking; taking both the highs and the volume leaves nothing to hear.

Implement the effect in whatever engine/stack the project already uses and follow its existing code style. Wire it up where it makes sense.