How to Set Up Audio Reference Mixes for Editorial Review

Reviewers will watch the rough cut in a conference room. Then on laptop speakers, then over a streaming review link, then in a producer’s car. A mix that only works on the editor’s headphones isn't doing its job. It has to carry enough of the scene’s rhythm and emotional shape. Reviewers should be responding to the edit, not wondering whether a line is missing. So the mix answers one question: “Is this rough cut working?” It does not answer “Is this the final sound of the show?” That makes it clear and stable, synced, and honest about intent. Dialogue leads. Music and effects support the scene without hiding problems. Label anything speculative. The sound team should know whether it is hearing a creative direction, a temp idea, or a survival mix from picture editorial.

Start with the job of the mix

A reference mix for editorial review sits between raw timeline audio and the final mix. It isn't a delivery master, and it shouldn't pretend to be one. Its job is to preserve the editorial experience. That means the mix should make these things clear:

What the audience is supposed to hear first
Which music cues are temp, licensed, original, or undecided
Which effects are story-critical versus placeholder sweetening
Where dialogue has known problems that need repair later
Whether a sound choice is approved intent or just coverage for review

The mistake is treating a review mix as either disposable or overly finished. If it's too rough, people review the audio problems instead of the edit. If it's too polished, the sound team may spend time reverse-engineering temp processing that was never meant to survive. Aim for a middle ground: good enough to support decisions, simple enough to hand off cleanly.

Build from dialogue outward

Dialogue is the anchor. If reviewers can't follow the words, nothing else in the reference mix counts. Get production dialogue into a consistent listening range first, then ADR, scratch VO, and guide narration. Only after that should you touch music or effects. An editorial reference rarely needs heavy cleanup. It does need enough level, clarity, and continuity for the scene to play. Keep voices centered unless a specific story reason says otherwise. Reach for clip gain and broad automation before complex processing. If a line is buried, fix the level first. If a line is boomy, boxy, or thin, use gentle EQ, and only where it helps intelligibility. A light dialogue treatment might include:

High-pass filtering to remove low-end rumble
Small EQ cuts for boxiness or harshness
Light compression to smooth uneven performances
Clip gain for word-by-word fixes on critical lines
Short fades to remove edits, pops, and bumps

Restraint is the point. The sound team can do better repair later if you don't bake in aggressive noise reduction, strange EQ, or over-compression. If a line is damaged, make it audible for review and flag the problem. Don't hide it so well that nobody budgets time to fix it. Once dialogue is stable, bring in music. Music is where many editorial reference mixes go sideways. Temp music usually arrives mastered and loud, wide and compressed. Production dialogue does not. Drop that music under a scene at near source level and the scene may feel exciting. The review becomes useless, though, because every note is fighting the words. Pull temp music down early and automate around lines. Let the cue rise in the gaps and transitions, and again in montages and emotional turns. If the music is supposed to overpower dialogue for story reasons, make that intentional and note it. Otherwise the default is simple: dialogue wins.

Dialogue stays dominant while music and effects support it.

Effects come after that. Hard effects and backgrounds, Foley and design elements, and production effects give the scene shape. They should not turn the reference into a fake final. A door slam that motivates a cut should be clear. A creature design that defines the scene should be present. Fifty layers of whooshes, cloth, and room tone are not where editorial time should go, unless the sequence depends on them.

Keep the track layout readable

A reference mix is easier to make and easier to explain when you organize the timeline. It doesn't have to look like a final Pro Tools session. It does need enough structure that another person can understand what they're hearing. For picture editorial, a simple layout works:

Dialogue and production sound
ADR, scratch VO, and guide narration
Music, split by cue where possible
Sound effects and hard effects
Backgrounds and ambiences
Foley or temp Foley
Design or special story sounds
Print track or mix bus

This layout helps in two directions. It makes the mix faster, because you adjust groups instead of hunting clips. It also helps the handoff. The sound team can see what was meant to be dialogue, what was music, and what was effects or design. That pays off when your team exports an AAF or XML later.

Grouped audio lanes make the rough mix easier to adjust and hand off.

Naming helps too. “MUSIC_TEMP_SadPiano_v3” is more useful than “Audio 37.” “SFX_story_radio_interference” is more useful than “zap new new.” Nobody needs perfect taxonomy during offline. But if a sound survives multiple reviews, it's important enough to name.

Use levels as guardrails

Editorial reference mixes aren't measured like final delivery masters. They still need level discipline. If every export lands somewhere different, reviewers lose trust. If the mix clips, distorts, or gets crushed by the review platform, the notes become contaminated. For most review exports, use conservative settings:

Leave true peak headroom, commonly around -2 dBTP when specs are unknown
Avoid brickwall limiting as a substitute for balance
Keep dialogue consistent scene to scene
Monitor at a repeatable level instead of chasing volume
Compare against previous approved cuts at matched playback level

If your project has a known delivery target, keep it in mind without confusing the reference with the master. A streamer, broadcaster, or distributor may have detailed requirements for final files. Those cover dialog-gated LKFS targets and true peak limits. They also cover channel layouts, sample rates, and stem requirements. Those specs are vital later. During editorial review they are guardrails. The bigger risk at this stage is a creative decision made against a temp mix that was unintelligible or misleading. Monitoring is part of this. Mix on headphones at midnight and the music may end up too loud, because dialogue still feels comfortable. Export from a second machine with a different pan law, limiter state, or routing. The review file may not match the timeline. Pick a repeatable monitoring setup and stay on it. When using another mix as a reference, level-match it. A mastered trailer, previous episode, or approved scene will almost always sound “better” if it's louder. Turn it down until it plays at the same perceived level as your current edit. Then judge balance, tone, and density. References are useful when they answer a specific question. Too many references, or references from the wrong genre, pull the edit in different directions.

Export the reference mix with the picture

For editorial review, the reference mix travels with picture. That picture file is what producers and directors watch. Showrunners, clients, and network teams watch it too. Marry the audio to the correct edit at the correct frame rate. Give it the correct start time and no mystery offset.

The review export keeps picture and reference audio together.

A typical review export should carry:

The current picture cut
A stereo reference mix
Matching frame rate and duration
Correct start timecode if the workflow uses it
Visible burn-ins when helpful, such as version, sequence name, date, and timecode
Head and tail format requested by the production, facility, or platform

Stereo is the safest choice for broad editorial review, because it survives more playback environments. Separate audio deliverables come into play in a calibrated room. They also come into play when the team is judging immersive or 5.1 intent. Some high-end review workflows accept a Pro Tools session or BWAV ADM, and some accept 5.1 stems or separate video guides. That is a different review mode than “send a rough cut to the team.” Match the export to the room and to the decision being made. For files your team intends to move into audio post, keep production standards intact where possible. Audio post workflows commonly expect 48 kHz, 24-bit WAV or BWAV. They expect proper timecode, and media that matches the native picture frame rate. Wrong production audio metadata travels downstream. And a reference mix doesn't replace the proper AAF. It doesn't replace production WAVs and turnover notes, or cue sheets and change lists. The review movie is for watching, while the turnover package is for working. They should agree, but they aren't the same deliverable.

Decide when to include splits or stems

A single stereo reference mix is enough for many editorial reviews. It's fast, simple, and hard to misuse. Sometimes split tracks or stems make the process cleaner. Consider exporting additional audio when the review process needs more control:

Dialogue, music, and effects splits for internal review
Music-only exports for composer or music editor review
Effects-heavy exports for sound design direction
Narration or VO isolated for script and timing review
5.1 or immersive guide files for calibrated room playback
Clean guide audio for localization, accessibility, or downstream prep

Don't create stems casually if they will confuse the handoff. A stem means something specific in finishing. If you export rough editorial splits, call them rough editorial splits. Don't call them final stems or printmasters. Don't call them M&Es or deliverables either, unless they are actually built to that spec. Also remember that changing stems and recombining levels creates a new mix version. Say a producer reviews a stereo export. An assistant later rebuilds it from splits with slightly different music levels. The team is no longer discussing the same thing. Version the files clearly.

Make versioning predictable

Audio reference mixes cause trouble when nobody knows which file belongs to which edit. The best versioning system is predictable and visible, right there in the file name and the burn-in. A useful name includes:

Project or episode identifier
Sequence or reel name
Cut version
Date
Audio mix version, if separate from picture version
Review purpose, such as director, network, client, or sound handoff

For example, a picture cut might be version 12 while the reference mix is version 12b. Only the audio changed after a review. That's fine, as long as the name says so. If the picture didn't change, don't imply that it did. If the audio changed, don't silently overwrite the old file. This matters because editorial review notes are often timecoded. If two files share the same name but have different audio, the notes become unreliable. If two files have the same cut but different start times, the notes become expensive.

Communicate intent to the sound team

The sound team needs to know what the editorial team meant. Alongside the reference mix, send notes that separate creative intent from temporary survival work. The sound supervisor and the dialogue editor listen for different things. So do the music editor, the sound designer, and the re-recording mixer. Good notes help all of them preserve the right things and ignore the noise.

Marked rough-mix choices help the sound team interpret editorial intent.

Useful notes include:

“Temp music is approved for tone, not timing”
“Door slam at 01:04:12:08 motivates the edit and should stay prominent”
“Dialogue line at 00:18:44:10 is production only, likely needs ADR”
“Client liked the dry intimacy of this scene”
“Ignore the noise reduction on interview two, added only for review”

These notes protect intent. They also prevent the most common rough mix problem, which is the sound team preserving artifacts nobody liked while accidentally changing the one temp choice everyone loved. If the rough mix is emotionally important, say so. Mixers often use the editorial rough as a creative reference. It captures what the director, editor, or producer has been living with. That doesn't mean the final should copy it. The rough mix contains decisions, habits, and approvals that the sound team should understand before improving them.

Avoid baking in problems

Some processing is useful for review, but some creates damage that follows the project. Be careful with these moves:

Heavy noise reduction on production dialogue
Flattening dynamics with bus compression or limiting
Printing reverb onto dialogue to fake a location
Extreme EQ to match mismatched mics
Stereo widening on music or effects that may collapse badly
Pitch or time changes without notes
Muting production sound that contains useful room, movement, or sync information
Exporting only the reference mix and not the source elements

These choices can sound better in the review while hiding the real condition of the material. They can also force the audio post team to rebuild around compromises they didn't choose. If you need to process something heavily so the rough cut can play, keep a clean version available and note what happened. The final mix can only improve what it can access.

Match the mix to the review environment

Not every review needs the same reference mix. A director watches in the edit room. A client reviews a web export. A studio team sits in a calibrated room. None of them is deciding under the same conditions. For casual remote review, prioritize translation. Keep the dialogue clear on laptop speakers. Avoid huge low-frequency decisions that only work on the edit room sub. Don't rely on tiny stereo details to carry story information. For internal editorial review, you can be more dynamic if everyone is listening in a known environment. Still, keep levels consistent between edits so the room isn't reacting to volume changes as if they're creative improvements. For calibrated mix review, treat the export formally. The review may generate in-progress notes for a mix team, or approve a near-final mix. Confirm all six of these in advance:

Required audio format
Channel layout
Loudness approach
Video guide
Session format
Naming convention

That may involve a Pro Tools session or discrete 5.1 files. It may involve BWAV ADM or separate video guide files, rather than a simple stereo QuickTime. The format should follow the decision. If the team is reviewing the edit, send an edit-friendly reference. If the team is reviewing the mix, send mix-review assets.

Review context	Mix priority	Practical export	Main risk to avoid
Casual remote review	Clear dialogue and translation on laptops, phones, and web players	Stereo picture file with version burn-ins	Letting music, bass, or stereo width carry story information
Internal editorial review	Consistent playback between cuts and useful creative response	Stereo reference mix, with rough D/M/E splits only if needed	Mistaking a louder or denser temp mix for a better edit
Composer or music editor review	Cue timing, tone, temp status, and music intent	Picture reference plus music-only or guide music tracks	Hiding whether a cue is temp, licensed, original, or undecided
Sound design direction	Story-critical effects, design intent, and placeholder status	Picture reference plus rough effects split and clear notes	Treating placeholder sweetening as approved design
Calibrated mix review	Channel format, loudness approach, and near-final mix intent	Agreed Pro Tools session, 5.1 or immersive files, BWAV ADM, or separate video guide	Reviewing a stereo web file as if it represented the room mix

Common ways reference mixes fail

Most bad reference mixes fail for simple communication and consistency reasons. Watch for these failure modes:

Dialogue is too low because your team never pulled down temp music
The export clips even though the timeline sounded fine
Review files have mismatched audio and picture versions
The sound team receives the reference movie but not the editable audio turnover
Timecode, frame rate, or start time doesn't match the turnover

The pattern is the same every time. The reference mix fails when it stops being a reliable guide to the cut.

The best reference mix is easy to outgrow

A good editorial reference mix gives reviewers confidence and gives the sound team direction. It keeps dialogue intelligible and supports the emotional shape of the edit. It preserves sync and travels with the right picture version. And it makes clear what is temp and what is intentional. The final mix should be better than the reference and still understand why the reference worked. If the rough music dip made the joke land, say that. If the temp ambience made the scene feel lonely, say that. If the dialogue treatment was only there to survive review, say that too. Send those notes with the file every time. That is what keeps everyone reacting to the same edit, the same intent, and the same story.

FAQ

An audio reference mix helps reviewers judge whether the cut is working. It should make dialogue clear, hold sync reliably, and support the emotional shape of the scene. It should communicate intent without pretending to be a final mix.

Music should sit under dialogue and be automated around important lines. Temp music usually arrives mastered and much louder than production dialogue, so it needs to come down early. If music is meant to overpower dialogue for a story reason, make that choice deliberately and note it for the sound team.

Stereo is safest for broad editorial review, because it translates across laptops, conference rooms, and streaming links, and it survives general playback systems. Use 5.1, immersive, or discrete audio files only when the review environment supports them and the team is specifically evaluating mix intent rather than the edit.

Splits are useful when reviewers or downstream teams need control over specific elements: dialogue, music, and effects, or narration and sound design. Label them clearly as rough editorial splits if they aren't final stems. A single stereo reference mix is often better when extra files would only create confusion.

Notes should separate creative intent from temporary fixes. Say whether temp music is approved for tone only. Say whether a sound effect motivates a cut, whether a dialogue line likely needs ADR, and whether a music dip is intentional. Say when noise reduction was added only to make the scene playable for review.

Keep clear file names, and also keep each revision attached to the same review asset so notes don't drift between exports. Aspect stacks revisions together with version history, which helps teams tell a picture change apart from an audio-only reference mix update.