export const meta = { title: "How to Set Up Audio Reference Mixes for Editorial Review", description: "Learn how to build a clear editorial audio reference mix, balance dialogue with temp music and effects, export it with picture, and communicate intent to audio post.", tldr: "Build an editorial reference mix that lets reviewers judge the cut, not the unfinished audio: stabilize dialogue first, pull music and effects around it, and avoid processing that hides problems. Export it with the correct picture version, timecode, and naming, and tell the sound team which choices are temp, approved intent, or only there for review.", slug: "how-to-set-up-audio-reference-mixes-for-editorial-review", publishedAt: "2026-08-26", readingTime: 9, thumbnail: "https://cdn.aspectlabs.dev/blog/how-to-set-up-audio-reference-mixes-for-editorial-review/cover-d8ea33dbde2e.png", authors: ["gurish"], primaryTopic: "post-production", topics: ["post-production"], tags: ["audio-post"], faq: [ { "question": "What is the purpose of an audio reference mix in editorial review?", "answer": "An audio reference mix helps reviewers judge whether the cut is working. It should make dialogue clear, support the emotional shape of the scene, keep sync reliable, and communicate intent without pretending to be a final mix." }, { "question": "How loud should music be in an editorial reference mix?", "answer": "Music should usually sit under dialogue and be automated around important lines. Temp music is often mastered and much louder than production dialogue, so it usually needs to be pulled down early. If music is meant to overpower dialogue for a story reason, that choice should be intentional and noted for the sound team." }, { "question": "Should an editorial reference mix use stereo, 5.1, or immersive audio?", "answer": "Stereo is usually safest for broad editorial review because it translates across laptops, conference rooms, streaming links, and 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 just the edit." }, { "question": "When should editorial export dialogue, music, and effects splits?", "answer": "Splits are useful when reviewers or downstream teams need control over specific elements, such as dialogue, music, effects, narration, or sound design. They should be clearly labeled as rough editorial splits if they aren't final stems. A single stereo reference mix is often better when extra files would create confusion." }, { "question": "What notes should be sent with a reference mix to the sound team?", "answer": "Notes should separate creative intent from temporary fixes. Useful examples include whether temp music is approved for tone only, whether a sound effect motivates a cut, whether a dialogue line likely needs ADR, whether a music dip is intentional, or whether noise reduction was added only to make the scene playable for review." }, { "question": "How do we keep audio notes tied to the correct cut when picture and mix versions change separately?", "answer": "Keep clear file names, but 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 distinguish a picture change from an audio-only reference mix update." } ], } The reference mix should answer one question: “Is this rough cut working?” not “Is this the final sound of the show?” For editorial review, the best audio reference mix is clear, stable, synced, and honest about intent. Dialogue leads, and music and effects support the scene without hiding problems. Label anything speculative so the sound team knows whether they're hearing a creative direction, a temp idea, or just a survival mix from picture editorial. That sounds obvious until reviewers watch the rough cut in a conference room, on laptop speakers, over a streaming review link, and then in a producer’s car. A reference mix that only works on the editor’s headphones isn't doing its job. It needs to carry enough of the scene’s rhythm, energy, and emotional shape that reviewers can respond to the edit instead of asking whether a line is missing. ## 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](https://krotos.studio/blog/audio-balancing). If reviewers can't follow the words, nothing else in the reference mix matters. Start by getting production dialogue, ADR, scratch VO, and guide narration into a consistent listening range before touching music or effects. For an editorial reference, you usually don't need heavy cleanup. You do need enough level, clarity, and continuity that the scene plays. Keep voices centered unless there's a specific story reason not to. Use clip gain and broad automation before reaching for complex processing. If a line is buried, fix the level first. If a line is boomy, boxy, or thin, use gentle EQ 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 The takeaway is restraint. The sound team can do better repair later if you don't bake in aggressive noise reduction, strange EQ, or over-compression. If the 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 often arrives mastered, loud, wide, and compressed. Production dialogue isn't. If you drop music under a scene and leave it near source level, the scene may feel exciting but the review becomes useless because every note is fighting the words. Pull temp music down early and automate around lines. Let the cue rise in gaps, transitions, 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. Effects come after that. Hard effects, backgrounds, Foley, design elements, and production effects should give the scene shape without turning 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 probably 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](https://blog.prosoundeffects.com/how-to-build-a-professional-sound-editorial-session-step-by-step-video). It doesn't have to look like a final Pro Tools session, but it should have enough structure that another person can understand what they're hearing. For picture editorial, a simple layout usually 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. First, it makes the mix faster because you can adjust groups instead of hunting clips. Second, it helps the handoff because the sound team can see what was meant to be dialogue, music, effects, or design. That matters when your team exports an AAF or XML later. 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 is important enough to survive multiple reviews, it's important enough to name. ## Use levels as guardrails You don't usually measure editorial reference mixes like final delivery masters, but you still need level discipline. If every export is wildly 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](https://partnerhelp.netflixstudios.com/hc/en-us/articles/360001794307-Netflix-Sound-Mix-Specifications-Best-Practices-v1-6), 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 but don't confuse the reference with the master. A streamer, broadcaster, or distributor may have detailed requirements for final files, such as dialog-gated LKFS targets, true peak limits, channel layouts, sample rates, and stem requirements. Those specs are vital later. For editorial review, they're guardrails. The bigger risk is usually making bad creative decisions because the temp mix was unintelligible or misleading. Monitoring matters here. If the editor mixes on headphones at midnight, the music may end up too loud because dialogue still feels comfortable. If the assistant exports from a different machine with different pan law, limiter state, or routing, the review file may not match the timeline. Pick a repeatable monitoring setup and stick with it as much as possible. When using another mix as a reference, [level-match it](https://www.izotope.com/community/blog/13-tips-for-using-references-while-mixing). 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, can pull the edit in different directions. ## Export the reference mix with the picture For editorial review, the reference mix usually travels with picture. That picture file is what producers, directors, showrunners, clients, and network teams will actually watch. You need to marry the audio to the correct edit, at the correct frame rate, with the correct start time, and with no mystery offset. Aspect gives reviewers frame-accurate comments and annotations on the review file, so audio notes land on the exact frame. Editors don't have to translate emailed timecodes before checking whether a line, dip, or effect is working. A typical review export should carry: - The current picture cut - A [stereo reference mix](https://partnerhelp.netflixstudios.com/hc/en-us/articles/4407928815379-Critical-Mix-Reviews-Audio) - 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 usually the safest choice for broad editorial review because it survives more playback environments. If the team is reviewing in a calibrated room, or if the team is reviewing immersive or 5.1 intent, then you may need separate audio deliverables. Some high-end review workflows accept Pro Tools sessions, BWAV ADM, 5.1 stems, or separate video guides. That's a different review mode than “send a rough cut to the team.” Match the export to the room and 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, proper timecode, and media that matches the native picture frame rate. If production audio metadata is wrong, that wrong information tends to travel downstream. A reference mix doesn't replace the [proper AAF](https://www.forte-ai.com/blog/aaf-workflow-in-pro-tools-from-import-to-mix-ready-session), production WAVs, turnover notes, cue sheets, or 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, but there are times when 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'll confuse the handoff. A stem means something specific in finishing. If you export rough editorial splits, call them rough editorial splits. Don't label them as final stems, printmasters, M&Es, or deliverables unless they're actually built to that spec. Also remember that changing stems and recombining levels creates a [new mix version](https://www.barryrudolph.com/extras/pe_guidebook_2025.pdf). If a producer reviews a stereo export and an assistant later rebuilds it from splits with slightly different music levels, the team may no longer be discussing the same thing. Version the files clearly. ## Make versioning boring Audio reference mixes cause trouble when nobody knows which file belongs to which edit. The best versioning system is boring, predictable, and visible inside the file name and burn-in. Aspect stacks every version on one asset, so the newest reference movie and the notes on it stay together. Reviewers always open the current cut instead of comparing notes against an old audio pass. A useful name usually 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 because 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, dialogue editor, music editor, sound designer, and re-recording mixer will all listen differently. Good notes help them preserve the right things and ignore the noise. 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, and they also prevent the most common rough mix problem: the sound team spends time preserving artifacts that 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 because it captures what the director, editor, or producer has been living with. That doesn't mean the final should copy it, but the rough mix contains decisions, habits, and approvals that the sound team should understand before they improve 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, or making the audio post team 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 watching in the edit room, a client reviewing a web export, and a studio team sitting in a calibrated room aren't making decisions 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 more formally. If your team intends the review to generate in-progress notes for a mix team or approve a near-final mix, confirm the required audio format, channel layout, loudness approach, video guide, session format, and naming convention in advance. That may involve a Pro Tools session, discrete 5.1 files, 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 clear: the reference mix fails when it stops being a reliable guide. It needs to be trustworthy. ## The best reference mix is easy to outgrow A good editorial reference mix gives reviewers confidence and gives the sound team direction. It keeps the dialogue intelligible, supports the emotional shape of the edit, preserves sync, travels with the right picture version, and makes clear what is temp versus 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. Editorial reference mixes make sure everyone is reacting to the same edit, the same intent, and the same story.