Fix: Unity Audio Mixer Ducking Compressor Not Triggering

Here is how to fix Unity Audio Mixer ducking that refuses to lower the music when dialogue plays. You add a Duck Volume effect on the Music group, set a threshold, and expect the volume to drop whenever speech triggers. Nothing happens. The Music group keeps playing at full level. The fix is understanding that Duck Volume needs a sidechain signal explicitly routed to it via a Send effect on the source group.

The Symptom

Music plays continuously. Dialogue plays at the same time without lowering the music. You added a Duck Volume effect to the Music group, set a Threshold of -30dB, a Ratio of 4:1, and expected ducking to happen automatically. The mixer’s VU meters show audio passing through both groups, but Music never attenuates.

What Causes This

No Send on the source group. Duck Volume listens on a sidechain input, not the group’s normal audio path. Without a Send effect on the source (Dialogue) group routing to the Duck Volume on the destination (Music), the sidechain receives nothing.

Send target is wrong. A Send can target any Receive or Duck Volume effect in the mixer. If you accidentally pointed the Send at a Receive on the SFX group, the Music duck does not trigger.

Threshold too low. If Threshold is -60dB but your dialogue is mixed at -20dB, the dialogue is well above threshold and will trigger ducking continuously even when silent (because room tone exceeds -60dB). Conversely, a -10dB threshold rarely triggers because dialogue rarely peaks that loud.

Exposed parameter override. If the Music group’s volume is overridden by a script through SetFloat("MusicVolume", x), the duck’s attenuation is added on top of your override but can be hidden by ongoing volume changes from your code.

The Fix

Step 1: Add a Duck Volume to the destination. Right-click the Music group in the Audio Mixer window, choose Add Effect → Duck Volume.

Step 2: Add a Send to the source. Right-click the Dialogue group, Add Effect → Send. Place the Send after the volume fader so the post-fader signal feeds the sidechain.

Step 3: Route the Send to the Duck Volume. Click the Send effect, open the Receive dropdown, and pick the Duck Volume on the Music group. Set Send level to 0dB (full).

Step 4: Tune the Duck Volume parameters.

Reasonable starting values for dialogue ducking music:
Threshold    = -20 dB
Ratio        = 4 : 1
Attack       = 100 ms
Release      = 500 ms
Make-up Gain = 0 dB
Knee         = 10 dB

Step 5: Test in Play mode with a real dialogue clip. Hit Play, trigger a dialogue line, and watch the Music group’s gain reduction meter on the Duck Volume effect. If you see the meter dip, ducking works. If not, recheck the Send target.

Triggering Ducking From Code

If your dialogue plays through an AudioSource not routed through the Dialogue group, the Send never fires. Always assign the AudioSource’s Output field to the correct mixer group:

using UnityEngine;
using UnityEngine.Audio;

[RequireComponent(typeof(AudioSource))]
public class DialogueLine : MonoBehaviour
{
    [SerializeField] private AudioMixerGroup dialogueGroup;
    [SerializeField] private AudioClip clip;

    void Start()
    {
        var src = GetComponent<AudioSource>();
        src.outputAudioMixerGroup = dialogueGroup;  // Critical for ducking
        src.PlayOneShot(clip);
    }
}

Bypass the duck during cinematics. If a cutscene needs music at full volume regardless of dialogue, expose the Duck Volume’s threshold and raise it to 0dB during the cutscene:

mixer.SetFloat("DuckThreshold", 0f);   // Effectively disable duck
// ...later
mixer.SetFloat("DuckThreshold", -20f); // Restore

Understanding the issue

Audio mixing is multiplicative. A bug in one channel's gain affects everything downstream. Bugs that cascade through the mix are hardest to diagnose.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Send sends signal. Duck reads signal. Without the Send, Duck Volume is just a quieter version of nothing.”

Related Issues

For mixer snapshot transitions, see Mixer Snapshot Not Transitioning. For audio attenuation problems, see 3D Spatial Blend Not Attenuating.

Send on source. Duck on destination. Route them together. Sidechain comes alive.