How to give feedback on a mix

Your engineer wants your real opinion. What they can't use is "something feels off in the middle," sent at midnight, followed by four more texts over three days. The difference between feedback that fixes a mix and feedback that spawns another round isn't taste or technical knowledge. It's a handful of habits, and they take less effort than the vague version.

Listen before you write

Play the whole mix once, start to finish, without touching your phone. First impressions of a mix are unreliable in a specific way: your ear needs a full pass to stop comparing it to the demo you've heard two hundred times. Then listen again where you actually live with music: the car, your earbuds, the kitchen speaker. A note that survives three listens in two places is a real note.

One condition: listen to the real file. A voice memo of a speaker, or a low-quality bounce forwarded through a chat app, adds its own distortion on top of the mix. If your engineer sent a streaming link with lossless playback, use it; that's the actual record you're judging.

Point at the exact spot

This is the single highest-value habit. "The vocal feels buried at 1:12" can be fixed this afternoon. "The vocal feels off somewhere" costs a full round of guessing, and the guess might land on the wrong chorus. Every note gets a timestamp, or a range ("2:10 to 2:25, the guitars crowd the vocal"). If the review page lets you drop a comment directly on the waveform, even better: the note and the moment can't drift apart.

Describe the feeling, not the tool

You hired an engineer for the how. Your job is the what: "the chorus should hit harder," "the verse feels empty," "her voice sounds far away." Those are perfect notes. What backfires is guessing at the technical fix: asking for "more compression on the vocal" when what you mean is "the vocal should feel more upfront" can send the mix somewhere you didn't want. Plain language about feelings and places is not amateur feedback. It's the professional format.

If you catch yourself writing a plugin name, delete it and write what you want to feel instead. The engineer will find the tool.

Use references (and say what you mean)

"The drums on this record, that's the energy I want" is worth three paragraphs. Send the reference with a timestamp too, and say what specifically you're pointing at: the drum sound, the vocal level, the overall darkness. One caveat: a commercial release has been mastered and yours may not be yet, so expect your mix to sound a little quieter and softer next to it. Which brings us to the trap.

The volume trap

Louder sounds better. Not as an opinion, as biology: as playback gets louder, your ear hears more bass and more treble, and everything reads as fuller and more exciting. One decibel is enough to swing a comparison. This matters twice: when you compare the mix against a reference, and when you compare version 2 against version 1. If one is louder, you may be choosing the volume, not the music. Compare at matched loudness when you can (here's why this fools everyone, engineers included), and be suspicious of any preference that appears only when one version is louder.

Batch your notes, speak with one voice

Ten messages over four days is the most expensive way to deliver ten notes. Each one interrupts, each risks being missed, and together they can burn through your included revision rounds one small fix at a time (most mix agreements include two or three rounds, with more billed). Instead: listen, collect everything, send one organized round. And if the band, the manager and the label all have opinions, merge them into one list first. An engineer served three conflicting sets of notes has to guess whose record it is.

Say yes clearly

The most underrated feedback is the approval. When the mix is right, say so explicitly: approve the version, name it, close the loop. Going quiet is not a yes; it leaves the engineer holding the session, unsure whether to bounce finals or wait for a fifth text. A clear sign-off is also in your interest, because it marks which version is the record and protects everyone from "wait, which file did we agree on" three weeks later. If your engineer's review page has an approve button, that button is the whole job.

The short version

Listen twice before writing. Timestamp every note. Describe the feeling and the place, not the plugin. Use references, compare at matched volume, send your notes as one batch with one voice, and when it's right, approve it in so many words. Your engineer will love working with you, and the record gets where you imagined it faster.

Frequently asked questions

How do I give good feedback on a mix?

Listen to the whole mix at least twice before writing anything, then anchor every note to a timestamp and describe what you want to feel at that spot. Collect all your notes into one message instead of a trickle, and when a version is right, approve it explicitly. Specific, batched feedback gets you the record you imagined in fewer rounds.

What if I don't know the technical terms?

You don't need them, and guessing at them can backfire: asking for "more compression" when you mean "the chorus should feel bigger" sends the engineer toward the wrong fix. Plain words about feelings and places ("the verse drags", "the vocal feels far away at 0:45") are exactly what an engineer can act on.

Why does the louder version always sound better?

Human hearing perceives more bass and treble as level rises, so even one decibel of extra volume reads as fuller and more exciting. When you compare two versions, make sure they're at matched loudness before you pick, or you may be choosing the volume rather than the mix.

How many rounds of feedback are normal?

Two or three rounds of revisions is the common norm for a mix, and most agreements price extra rounds separately. That's another reason to batch your notes: ten separate messages can burn through the included rounds on things one careful listen would have caught together.

What should I listen on when reviewing a mix?

Start with the best speakers or headphones you know well, then check the places you actually hear music: the car, earbuds, a phone speaker. Listen to the real file on a lossless link rather than a voice memo or a low-quality bounce, because you can't judge a mix through a second compression step.