Noise Gates in Live Sound: Threshold, Attack, Hold, and Release

TL;DR — A noise gate reduces a signal when its detector falls below a chosen threshold, helping control spill or noise between wanted events. It cannot separate wanted and unwanted sounds that occur together, and an aggressive setting can remove quiet notes or natural decay. Fix the source first, set the gate with representative performance dynamics, check every destination, and document only verified show-critical behaviour.

Table of contents

1. What a noise gate does
2. What the gate controls mean
3. Where gates help—and fail
4. How to set a gate
5. How to document gating
6. FAQ

What a noise gate does

A noise gate is a dynamics processor that reduces a signal when its detector indicates the wanted source is absent or below a set level. When the source crosses the opening condition, the gate moves toward its open state; when it falls below the closing condition, the gate eventually returns toward attenuation.

A gate does not know which sound is musically wanted. It reacts to its detector. Cymbal spill can open a tom gate, speech can open a lectern microphone, and noise can remain audible whenever the wanted source is present. Improve microphone selection and placement, repair noisy equipment, and establish correct gain before adding a gate.

Devices use these names differently. Read the processor documentation and listen to the result instead of assuming that two controls with the same label behave identically.

What the gate controls mean

Threshold and hysteresis

The threshold is the detector level used to decide when the gate opens or closes. Some gates use separate open and close thresholds, or hysteresis, so the signal must rise to a higher level to open than it must maintain to stay open. This reduces chatter when the detector hovers near one boundary.

A threshold value has meaning only relative to the signal reaching that processor. Changing microphone position, preamp gain, source output, insert point, or upstream processing changes the detector relationship.

Attack, hold, and release

Attack controls how quickly the gate opens. If it is too slow, the beginning of a drum hit, consonant, or instrument note may disappear. Hold keeps the gate open for a minimum period after the closing condition is met. Release controls how quickly attenuation returns after hold. These controls work together to preserve the intended event and decay.

Range or depth

Range, sometimes called depth, limits how much the closed gate attenuates. Full muting can sound unnatural and make mistakes obvious. Moderate attenuation often controls spill while preserving room tone and making transitions less distracting.

Sidechain and key filter

The sidechain is the detector path. A key filter can make the detector more responsive to the wanted source without applying that filter directly to the audible path. For example, a tom gate may use a detector band that responds more strongly to that drum than to nearby cymbals. A filter cannot create complete separation when sounds overlap substantially.

Lookahead

Some digital gates delay the audible path briefly so the detector can begin opening before a transient arrives. Lookahead may preserve attacks, but it adds latency and is not available or appropriate on every path. Check system timing and manufacturer documentation before relying on it.

Where gates help—and fail

Drums and percussion

Gates can reduce cymbal spill and stage noise in close microphones between hits. They can also miss soft strokes, chop resonance, open from adjacent drums, or change the perceived groove. Test rolls, ghost notes, rim sounds, hard hits, and the quietest intentional playing—not only isolated soundcheck hits.

Speech and vocal microphones

An expander or gentle range-limited gate may reduce room noise between speakers, but automatic microphone mixing is a different process designed for multiple open speech microphones. A hard gate can remove quiet words and make ambience jump. Microphone technique, placement, and the number of open microphones remain primary.

Guitar rigs, effects, and playback

A gate can reduce hiss or hum between intentional passages, particularly when a source rig already includes one. It cannot remove noise underneath the wanted signal. Sustain, reverb tails, delay repeats, swells, and quiet intros may be part of the performance, so the gate must be tested across patches and songs.

Monitors, buses, and streams

A channel gate may feed FOH, monitors, recording, and stream depending on console tap points. Sudden ambience changes that are acceptable in the audience mix may be distracting in IEMs or a broadcast feed. Check whether destination-specific processing or an ungated split is required.

Problems a gate will not solve

Use the live sound troubleshooting checklist to isolate faults before processing around them. A gate may hide a symptom between events while leaving the actual failure unresolved.

How to set a gate

1. Define what should pass

List the quietest wanted event, the loudest unwanted event, and the natural decay that must remain. If those levels overlap heavily, a gate alone may not separate them reliably.

2. Fix the source and signal path

Verify the microphone, placement, cable, patch, gain, routing, and equipment health. Reduce preventable noise and spill physically. Confirm that the detector receives the intended channel and that upstream processing is not moving its level unexpectedly.

3. Start with the gate bypassed

Hear the full dynamic range and identify the real problem. Reset inherited settings when their origin is unknown. If the gate offers range control, begin with moderate attenuation so opening mistakes are easier to hear and less destructive.

4. Set threshold with representative material

Have the performer play the quietest and loudest intended events as well as nearby sources. Raise the threshold enough to reject the unwanted condition while ensuring every wanted event opens the gate. If no reliable position exists, improve isolation or use gentler expansion.

5. Preserve the attack

Use an attack fast enough to keep the leading edge of the source. Slow it only when deliberately softening a transient. Compare bypass so familiarity with a chopped attack does not become the reference.

6. Set hold and release for the decay

Increase hold until the gate stops chattering within the event. Adjust release so the natural ring, word ending, sustain, or effect tail closes smoothly. Test repeated notes and the show's actual tempo; a decay that works for isolated hits may blur or pump in a pattern.

7. Refine the detector

Use hysteresis, when available, to stabilize opening and closing. Adjust the key filter while monitoring the detector safely, then confirm the audible path remains correct. Do not narrow the detector so aggressively that variations in tuning or technique stop opening the gate.

8. Check the complete show path

Listen in the full arrangement, not only in solo. Verify FOH, wedges, IEMs, recording, stream, and effects sends. Recheck after microphone movement, drum tuning, source-level changes, different performers, or a new venue.

How to document gating

Most technical riders should describe sources and constraints rather than dictate house processing. Document a gate when it is embedded in an artist rig, stored in an approved show file, essential to a special effect, or important enough that another engineer must reproduce or explicitly bypass it.

If exact settings matter, name the channel, processor or show file, detector source, range, timing, linked channels, affected destinations, and the performance material used to verify them. Threshold numbers copied between consoles are not portable when scales, gain structure, detector behaviour, or insert positions differ.

In Techrider.live, align the channel name with the stage plot and input list, add a concise note for show-critical behaviour, and invite the responsible engineer to edit and save the same Rider. Inspect history when the gate plan changes, then export a dated PDF for offline venue handoff.

Gate handoff checklist

• Define the quietest wanted and loudest unwanted events.
• Repair faults and improve microphone placement first.
• Verify gain, insert position, detector, and routing.
• Test soft, normal, and hard performance dynamics.
• Preserve attacks, sustain, decays, and effects tails.
• Prefer limited range or expansion when full closure sounds unnatural.
• Check FOH, monitors, recording, stream, and effects.
• Save only verified settings and their recheck triggers.

FAQ

What does a noise gate do in live sound?

It attenuates a signal when its detector falls below a chosen condition and opens when the wanted event crosses the opening condition. It can reduce spill or noise between events, but it cannot remove unwanted sound that occurs at the same time as wanted sound.

How do you set a noise gate?

Fix the source and set gain first. Establish a threshold that opens for the quietest wanted event but rejects the loudest unwanted event, then set attack to preserve the beginning and hold/release to preserve the natural decay. Test real performance dynamics and every destination.

What is the difference between a gate and an expander?

A gate commonly applies a defined or substantial amount of attenuation below its threshold. A downward expander reduces level progressively as the signal becomes quieter. Expansion often sounds gentler, although processor labels and control designs vary.

Should you gate live drums?

Only when it solves a specific problem without losing intentional strokes or decay. Gates can control spill in close drum microphones, but poor settings can miss ghost notes, chatter, false-trigger from adjacent drums, or shorten resonance. Test the drummer's complete dynamic range.

Can a noise gate remove microphone feedback?

It may mute a path while no wanted signal is present, but it does not fix the gain, placement, routing, or resonant condition that causes feedback. When the gate opens, the feedback path returns. Correct microphone/loudspeaker geometry and gain structure instead.

Keep gate behaviour tied to the source

Build a reusable Rider with Techrider.live, connect every physical source to its input-list row, and record only gating constraints another engineer must preserve or verify. The quietest wanted event and the recheck trigger matter more than a copied threshold number.