Video Summary - Reverb in a Film Mix

Main ideas / lessons

Use reverb only when it has a clear purpose. The creator argues beginners often use too much reverb “because it’s there,” such as adding reverb to all dialogue. Instead, they emphasize asking “why” before changing anything (reverb, EQ, compression, etc.).
You don’t always need reverb at all. With properly chosen tracks/processing, dialogue can sound right with no reverb—you shouldn’t add reverb merely to justify effort.
Reverb in film mixing is primarily about “space,” not the lush tail. The key technique is to prioritize early reflections (to convey the room) while keeping the reverb tail lower to avoid washiness/muddiness.
Separate reverb tools by audio category and use cases. They organize routing and reverbs by stems (dialogue, Foley, sound effects, etc.), rather than relying on one setting for everything.
Matching ADR/production requires processing the reverb consistently with the source audio. For ADR or cleaned/processed dialogue, they often render (“AudioSuite”) the reverb and copy it so the reverb can be treated the same way as the tracks (e.g., noise reduction with Cedar), and copied/matched more reliably.
Context matters: music and layered sound design can mask reverb. Once music/backgrounds are in, you may end up needing so much reverb to hear it that it becomes excessive. Often, keeping dialogue clean works better, and reverb becomes part of the soundscape when music is absent or low.
Simplicity and portability beat “plugin lists.” They prefer using Pro Tools stock tools and a manageable setup so the workflow remains fast and transferable across studios.

Method / workflow described (structured)

1) Guiding philosophy (“always ask why”)

Before applying any processing, ask:

Why am I adding reverb / EQ / compression?
What does this change do for the film/story/character (space, emotion, realism)?

Don’t feel forced to “touch” every track:

Sometimes the right move is nothing (leave it clean).
Sometimes a small adjustment (EQ/volume) is enough.

2) Template organization (Pro Tools stems and sends)

Use stem/bus structure by categories such as:

Dialogue
PFX
Music
Sound Effects

Further break down sound effects into things like:

Foley (treated separately)

Set up a reusable reverb system:

Four mono reverbs (“general purpose” bread-and-butter)
Two 5.0 reverbs (for wider/multi-channel placement needs)

3) Mono reverb timing presets (earlier → longer)

For each mono reverb send, they define “types” primarily by time / early reflections intent:

Slap: early reflections only (for distant outdoor/spacey placement like woods or alleys)
Short reverb: ~400 ms (small room / bedroom / boxy room)
Medium reverb: ~1 second (bigger room like kitchens, offices)
Long reverb: ~2.5 seconds (examples given: parking garage; possibly longer like gymnasium—time may effectively need to match the scene)

4) Assign which stems use which reverbs

Sound effects / PFX / Foley: receive mono reverb sends.
Music: generally not treated with the same mono reverbs. They discuss using a 5.0 reverb strategy for music/backing contexts (and/or minimal reverb approach), and they mention treating music with its own approach rather than the mono room reverbs.

They also note they keep the system simple:

Example: don’t rely heavily on stereo reverbs anymore.

5) 5.0 reverb usage

Use two 5.0 reverbs:
- One may be inactive/not frequently used depending on the show.
These are set up per program/show needs and may sometimes sit unused unless needed.
They automate changes based on scene geography/scale (example: a large church, characters far back).

6) Control changes via sends (automation-friendly)

Instead of automating many reverbs or switching plugins constantly:

Adjust the send level for a scene/line (automation or control surface).

Example concept:

For a specific dialogue line that should sound more distant: increase the relevant send to add “slap/early reflections,” etc.

7) Prioritize early reflections over tail (core mixing technique)

On the reverb settings:

Increase early reflections to establish room/spatial cues.
Decrease the actual reverb tail to avoid:
- “buttery tail”
- wash/modulation/overly lush reverb that muddies dialogue

Optionally:

Use EQ/damping to remove excess “wash” and keep reflections intelligible.

8) Handling ADR / production matching with “AudioSuite + render”

When matching ADR or production:

AudioSuite the reverb and copy it down to another track.

Rationale:

Dialogue may need additional processing (e.g., Cedar noise reduction).
To keep reverb consistent with the processed audio, they want the reverb to be processed the same way.

They also:

Copy automation from the original track to the rendered/matched track so timing stays aligned.

9) Reverb decision-making checklist (implicit)

Ask whether you need reverb for:
- Space / scale (big empty room → add reflections/reverb)
- Story/character emotion
Check against mix balance:
- If music/backgrounds are active, reverb can become hard to hear without overdoing it.
- If music is present and you can’t hear reverb well, removing reverb can be the better outcome.

10) Flexibility / alternatives mentioned (not required)

Other studios use:

pre-fade sends / post-fade sends

They personally prefer:

100% wet reverb handling on-track when needed (especially for certain sources)

They also mention options like:

freezing reverbs (as an alternative workflow), though not the focus.

Speaker / sources featured (as mentioned)

Speaker/creator: Unspecified individual (“hey guys…”—no name given in the subtitles)
Requesting person mentioned: Daniel Brown (asked about reverb in 5.1 mixes)

Software / plugin sources referenced

Avid Pro Tools (primary DAW)
Reverb plugins/tools mentioned:
- Revive (Pro Tools)
- Altiverb
- PhoenixVerb
- Chameleon
- D-Verb (mentioned as an alternative)
Cedar (used for noise reduction / processing consistency)
Lexicon 480 (mentioned as an example of lush tails to avoid/make less dominant)

Reverb in a Film Mix

Key takeaways