How to Fix a Web Audio Master Volume That Doesn't Affect All Sounds

Your master slider lowers most sounds but a few stay loud. Any node wired straight to the destination skips the master gain entirely.

How to fix it

1. Funnel through one gain

Create a single masterGain, connect masterGain.connect(ctx.destination), and route every source into masterGain instead of destination.

2. Audit stray connections

Search for any .connect(ctx.destination) on source or effect nodes and re-point them at the master bus.

3. Use sub-buses under master

Create music/SFX gains that feed the master, so category and master volume both work and nothing bypasses the chain.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every HTML5 error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.