What audio ducking is
Ducking is music automatically getting quieter while something else plays over the top of it, then coming back up on its own. The music ducks out of the way. Nobody touches a volume control.
Put another way: it is the one thing a sound engineer would be doing for you, done for you. Watch anyone competent on a desk during a show and you will see the same gesture over and over — the music fader eased down as the microphone opens, held there, eased back up when the moment has passed. That is the job. Ducking is that hand, on every cue, without the hand.
You already know what it is
Somebody is playing music. You start to speak, so they turn it down. You finish, and they turn it back up. That is ducking — and the only difference here is that nobody has to remember to do it.
You hear the same thing done properly every time an announcement comes over music in a shop or a station, or a radio presenter talks across the intro of a song and the song sits politely underneath them. Two things are playing at once, and one of them has been told to give way.
The word comes from broadcasting, where an engineer would literally pull a fader down — duck the music — as the microphone opened. The idea is old; only the automation is new.
Why it is not the same as turning the music down
Three things separate ducking from just being quieter:
- It is automatic. It happens because the other sound started, not because somebody reached for something. That matters when both your hands are busy.
- It comes back. The music returns to its proper level when the thing on top finishes, without you remembering to restore it — which is the step people forget under pressure.
- It is temporary and specific. Only the moment that needs clearing is cleared. The music is at full level either side of it.
The two numbers that matter
How far it ducks — how quiet the music gets. Usually expressed as a percentage of its normal level. A quarter is a sensible default: obviously out of the way, still clearly there. If you cannot hear the music at all during the dip, you have gone too far, and the audience will notice the hole.
How fast it ducks — how long the drop and the recovery take. Too fast and it sounds like a fault, a click or a lurch. Too slow and the first words are buried before the music gets out of the way. A short ramp of a fraction of a second in each direction is what makes it sound deliberate rather than broken. Studio tools call these attack and release.
The soundman you do not have
Most people reading this do not travel with an engineer. There is a laptop, a cable to whatever the venue calls a desk, and you. In that situation the music has exactly two settings — on, and off — and both are wrong at the moment you need to be heard over it. Off leaves a hole. On means talking over your own backing track and losing.
What an engineer would give you is the third option: the music still there, still carrying the room, just underneath you for as long as it needs to be. You can buy that as a person, or you can have the software do the one gesture the person would have made. It is not judgement — it will not ride a level because the room got loud, or catch a singer who has drifted off mic. It is one movement, made correctly, every time, on cue, for nothing.
And unlike an engineer, it cannot be looking the other way when the moment arrives. The dip starts because the pad started; they are the same instant.
When a performer needs it
Ducking is normally discussed by podcast editors and video editors, working after the fact. Live, on a stage, it matters more, because there is no second take:
- A magician whose act is a music bed with moments on top of it. The build runs, the reveal sting lands over it, the build carries on carrying the room. Stopping the music for each beat would take the act apart.
- A hypnotist running a twenty-minute induction bed who needs a wake cue, a countdown or a sting to land clearly over the top — without stopping the bed, which would undo the whole induction.
- A children’s entertainer with party music running and a boing, a crash or a fanfare to fire every thirty seconds. Stopping the music for each one would leave the room in silence a dozen times an hour.
- An MC or compere with walk-on music playing who needs to be heard over it for a sentence.
- A venue playing background music that has to carry an announcement without anybody running to the desk.
The alternative in all four cases is stopping the music, and silence is louder than music — a sudden stop pulls every head in the room toward the sound system, which is precisely where you did not want them looking.
How Queue Up does it
Each instant-play pad is set to one of two modes. Interrupt stops the playlist and plays instead — for a track that replaces what is on. Overlay plays on top while the playlist keeps running, and ducks it automatically for exactly as long as the pad sounds.
The depth is a single setting — Dip to, defaulting to 25% — and it can be turned off entirely if you would rather ride the levels yourself. The ramp down and back up is deliberately short rather than instant, because an instant change of level is audible as a click. Every pad remembers which mode it is, so a wall can mix the two: stings that duck the music, and one track that replaces it.
There is nothing to route, no sidechain to configure and no audio interface required — it is two settings, and the rest happens because you pressed a pad.
Questions people ask
What is audio ducking in simple terms?
Ducking is when one sound automatically drops the volume of another while it plays, then lets it come back up. Think of somebody turning the music down while you speak and turning it back up when you have finished — that, but nobody has to remember to do it. It is the same movement a sound engineer makes on a desk, easing the music fader down as a microphone opens and back up afterward, made automatically on every cue.
Is ducking a substitute for having a sound engineer?
For this one job, yes, and that is the point of it. Easing the music down under a voice or a cue and bringing it back afterward is the movement an engineer makes more than any other, and ducking makes it identically every time, at the instant the cue starts, for nothing. What it does not replace is judgement — it will not ride a level because the room has got louder, rescue a performer who has drifted off microphone, or decide that tonight the music should sit higher. It does one thing an engineer would do, not the thinking behind the rest of it.
Is ducking the same as sidechain compression?
Sidechain compression is the classic studio way of achieving ducking, and in dance music it is used as an effect in its own right — the pumping you hear under a kick drum. Ducking is the result; sidechain compression is one way to get it. A player like this does it far more simply, by ramping the volume down and back up, because the goal is intelligibility rather than a sound.
How much should the music duck by?
Enough to hear the thing on top clearly and no more. Dropping to roughly a quarter of the original volume is a common starting point and is what this app defaults to. Too little and the two fight each other; too much and the room notices the music vanishing, which is more distracting than the music itself.
Why not just stop the music instead?
Because silence is louder than music. Stopping a track dead in front of an audience draws attention to the sound rather than to whatever you wanted them to hear, and leaves you with the problem of restarting it. Ducking keeps the bed running underneath, so the moment passes without a hole in it.
See it working
The magic act page and the hypnosis show page are the clearest examples — a music bed with cues landing over the top is the case this behavior exists for. Or read about the instant-play pads generally, look at the screenshots, or try it on your own show.
Something here unclear, or wrong? Say so — this page exists to be useful rather than to be found.