how-to
How Do You Give Feedback to a Mixing Engineer?
Last Updated: October 26, 2026
Quick Summary
Give feedback to your mixing engineer by naming the timecode, describing what you hear, and stating the effect you want, all in one email per revision round. Rank your must-fix notes first, protect the parts you love, and reference one or two songs for direction rather than exact copying.
- Consolidate tracks from the song's start, name every track clearly, and include a rough mix with headroom.
- Your first message should state the song's goal, name two or three reference tracks, and note what's working.
- Write notes as timecode first, then what you hear, then what you want.
- Keep each revision round to one email with a ranked list and a do-not-change section.
- Wait a day and check the mix on at least two playback systems before sending new notes.
Table of Contents
- How to Prepare Files for Professional Mixing Before You Send Notes
- What to Include in Your First Feedback Message to the Mixing Engineer
- Common Mixing Terminology for Artists: Describing Sound Without a Studio Degree
- How to Use Timestamps and Reference Tracks in Mix Feedback
- A Mix Revision Request Template You Can Reuse Every Round
- How to Handle Disagreement and Give Constructive Criticism Without Derailing the Mix
- Book a Session at LB-Mastering Studios and Send Your First Round of Notes
- Frequently Asked Questions
How to Prepare Files for Professional Mixing Before You Send Notes
Good feedback starts before the first note gets written. If you send a cluttered session with no labeling, your mixing engineer spends the first hour untangling instead of listening, and the notes you write later will describe a mix that never had a fair shot.
Here's what a clean handoff looks like:
- Consolidate your tracks from the start of the song so every file begins at zero.
- Name every track clearly ("Lead Vox," "Kick In," "Rhythm Gtr L"), not "Audio 14."
- Include a rough mix so the engineer hears your intent, not just your parts.
- Leave headroom. A rough that clips gives the engineer nothing to work with.
- Zip the session and list the tempo and sample rate in the email body.
The rough mix matters most. It's your reference point for the whole project. Without it, the engineer guesses at your vision.
What to Include in Your First Feedback Message to the Mixing Engineer
Your first message sets the tone for the entire collaboration, so make it count. A strong opening message does three things: it states your goal for the song, names two or three reference tracks, and tells the engineer what you love about the current mix.
Here's a structure that works:
- The goal. One sentence on what the song should feel like. "This needs to hit hard on a car stereo" tells the engineer more than "make it sound good."
- What's working. Name the parts you want protected. Engineers need to know what not to touch.
- Your references. Two songs maximum, with a note on what to borrow from each.
- Your deadline and format needs. Streaming, vinyl, or both.
Skip the long backstory. Engineers read dozens of these messages, and clarity wins. If you want to go deeper on articulating creative direction, our guide on how to communicate your creative vision walks through it step by step.
Common Mixing Terminology for Artists: Describing Sound Without a Studio Degree
You don't need a studio degree to give useful notes, but a shared vocabulary saves rounds of guesswork. The real skill is translating what you hear into a request an engineer can act on without dictating their technique. Here's the plain-English version of the terms you'll hear most, paired with how to turn them into notes.
- Low end: the bass and kick region. "Muddy low end" means too much buildup down there. Instead of "clean up the low end," write: "0:45, the kick and bass are fighting, can the bass sit slightly behind the kick so the punch comes through?"
- High end: cymbals, air, sibilance. "Harsh high end" means it stings. Try: "1:12, the cymbals are sharp on headphones, can they be softened without losing air?"
- Frequency balance: how the lows, mids, and highs sit against each other. "The vocal feels buried in the chorus" describes vocal level and frequency balance at once. A stronger note: "2:05, the vocal disappears under the guitars in the chorus, can the vocal come forward without pulling the guitars down?"
- Stereo image: how wide the mix feels. Panning spreads instruments left and right (Making The Most Of The Stereo Panorama). "The mix feels narrow" becomes: "The verse feels narrow compared to the chorus, can the guitars spread wider in the verse?"
- Dynamics: the gap between quiet and loud moments. Heavy compression shrinks that gap. "The chorus doesn't lift" becomes: "The chorus should feel bigger than the verse, can we keep more dynamic range in the chorus?"
- Punch: the attack of drums and bass. "More punch" means a tighter, snappier transient. "The drums feel soft" becomes: "The kick should hit harder on the downbeats, can we tighten the attack?"
- Reverb: the sense of space. More reverb pushes a vocal back; less pulls it forward. "The vocal feels distant" becomes: "The vocal should feel closer and more intimate, can we reduce the reverb tail?"
The pattern: name the timecode, describe what you hear, and state the effect you want. Avoid naming plugins or settings, that's the engineer's job. Your job is to describe the destination, not the route.
Here is a quick reference for turning what you hear into a note an engineer can act on.
| Term | What it describes | Example note |
|---|---|---|
| Low end | Bass and kick region | 0:45, kick and bass fighting, bass behind kick |
| High end | Cymbals, air, sibilance | 1:12, cymbals sharp on headphones, soften without losing air |
| Frequency balance | How lows, mids, highs sit together | 2:05, vocal disappears under guitars in chorus |
| Stereo image | How wide the mix feels | Verse feels narrow, spread guitars wider in verse |
| Dynamics | Gap between quiet and loud moments | Chorus should feel bigger, keep more dynamic range |
| Punch | Attack of drums and bass | Kick should hit harder on downbeats, tighten attack |
| Reverb | Sense of space | Vocal should feel closer, reduce reverb tail |
How to Use Timestamps and Reference Tracks in Mix Feedback
Timestamps turn vague feedback into instructions an engineer can act on. Instead of "the bridge feels off," write "1:42, the lead guitar is too loud against the vocal." The engineer jumps straight to that second and hears exactly what you hear.
Use this format consistently:
- Timecode first: 0:58, 1:42, 2:15.
- What you hear: "snare disappears under the synth."
- What you want: "pull the synth back a touch so the snare cuts through."
Reference tracks work the same way. Pick one or two commercial songs that share your target sound, and tell the engineer which element to borrow from each. For a deeper look at how reference tracks are used in practice, see our audio mastering and mixing article. "Match the vocal warmth of this track, but keep my drums drier" is a clear, actionable note.
One caution: your references were mixed in a different room on different gear. Treat them as direction, not a target to copy exactly.
A Mix Revision Request Template You Can Reuse Every Round
Copy this template into every revision email. It keeps your notes organized and gives the engineer a clear checklist.
Revision Round: [number] Song: [title]
Overall: [one sentence on how the mix feels now]
Timestamped notes:
- [0:00] [what you hear] → [what you want]
- [0:00] [what you hear] → [what you want]
- [0:00] [what you hear] → [what you want]
Do not change: [parts you're happy with]
Reference check: [any new reference notes]
Deadline: [date]
Keep each round to one email. Scattered notes across texts and voice memos get lost. One shared document, one list, one deadline.
How to Handle Disagreement and Give Constructive Criticism Without Derailing the Mix
Disagreement is normal, and it usually means you care about the song. The trick is to criticize the mix, not the engineer, and to structure the conversation so a single point of friction doesn't derail the whole project. A clear revision and approval workflow can help structure the conversation. For process questions about revisions and communication, check the studio FAQ.
Set revision scope up front. Before the first mix arrives, agree on how many revision rounds are included, what turnaround time to expect, and what counts as a new direction versus a refinement. Put this in writing so neither side is guessing.
Consolidate and prioritize notes each round. Send one email per round with a ranked list: the two or three must-fix items first, then nice-to-haves. Scattered texts and voice memos get lost, and a wall of complaints with no priorities can make an engineer second-guess everything and flatten the mix. Rank your notes so the big items get fixed first.
Use before-and-after examples to keep criticism constructive. Instead of "you ruined the vocal," try: "In the previous version the vocal felt intimate; now it feels distant. Can we bring back that closeness?" That describes the effect, not the fault, and gives the engineer a clear target. When you're unsure, ask a question: "Could the bass sit lower here?" invites a fix without dictating technique.
Review revisions against your own notes. When a new mix arrives, listen once without notes, then listen again with your timestamped list open. Confirm what was addressed, flag anything that regressed, and note whether an issue persists across playback systems (car, phone speaker, headphones, studio monitors). If a problem only appears on one device, say so, that's useful context, not a demand.
Approve deliberately. When the mix meets the agreed scope, approve it in writing and move to mastering. If you're unsure, ask for a single targeted revision rather than reopening everything. A structured approval step reduces contradictory or repeated requests and keeps the project moving.
Book a Session at LB-Mastering Studios and Send Your First Round of Notes
Clear feedback is the difference between a mix that lands and one that drags through endless rounds.
At LB-Mastering Studios, our mixing and mastering work is led by a Latin GRAMMY Award-winning, 11x Billboard-charting engineer with more than 44 years of experience. We work from a specialized analog facility with premium outboard gear, and we offer single song, stem, album, and vinyl mastering. We also provide a free sample master.
Ready to hear your song at its best? Book a session.
Frequently Asked Questions
How do you describe what you want in a mix without using technical terms?
Describe the feeling and the specific element. Say something like 'the vocal feels buried under the guitars in the chorus' or 'the drums sound distant compared to the reference track.' Use plain language about what you hear and where you hear it, then name the song or section. A mixing engineer can translate everyday descriptions into EQ, compression, and level changes. Pairing your words with a timestamp and a reference track gives the engineer a clear target.
What is the best way to send revision notes to a mix engineer?
Put every note in one shared document or email thread, organized by song and timestamp. Number each request so the engineer can reply point by point. Avoid scattering notes across texts, voice memos, and social messages. A single organized list reduces missed changes and keeps the revision round focused.
How many revisions should I expect from a mixing engineer?
Revision policies vary by studio, so ask before booking. Clarify what counts as a revision, how long each round takes, and whether changes to arrangement or performance fall inside the scope. Getting this in writing before the first mix arrives prevents surprises.
How do I tell a mixing engineer I don't like the mix without being rude?
Focus on the sound, not the person. Instead of 'this mix is bad,' say 'the low end feels heavy on my car speakers and the vocal gets lost in verse two.' Point to what works first, then name the specific sections that need change. Use timestamps and reference tracks so the feedback reads as a shared goal rather than a complaint. Constructive criticism delivered with specifics is easier to act on.
