How to give feedback on a mix

You do not need technical vocabulary to give useful feedback. Describe what you hear, identify the passage and explain what you would like to change.

Listen before you write

Listen to the whole mix before writing your notes, then return to the passages you want to discuss. Start on speakers or headphones you know well and check another familiar listening setup if needed.

Use the file or review link your engineer sent. A phone recording of a speaker or a re-encoded copy adds changes that can make it harder to judge the mix itself.

Point at the exact spot

Include a timestamp or range with each request. “The vocal feels buried at 1:12” is easier to locate than a general comment about the vocal. If the review page supports waveform comments, mark the passage there.

Describe the change you want

Describe the result you want, such as a more prominent vocal or a stronger chorus. You can discuss a particular processor if you have one in mind, but explain the intended effect too. That gives the engineer room to suggest an appropriate change.

Use references (and say what you mean)

Send a reference with a timestamp and explain what you want to compare: drum tone, vocal level, dynamics or another feature. A mastered reference may be louder than an unfinished mix, so match the listening level before comparing.

Match the listening level

A louder version can seem fuller or more detailed in a quick comparison. Match the playback loudness when comparing a revision with an earlier mix or a reference. Read more about loudness bias and gain matching.

Send one agreed set of notes

Collect your notes into one list before sending them. If a band, manager and label are all involved, resolve conflicting requests and agree who will send the final list. This gives the engineer a complete set of changes for the next round.

Say yes clearly

When you are happy with the mix, confirm the version you approve. Use the approval button if the review page has one, or name the file in your reply. The engineer can then prepare the final delivery.

Phrases that work

Borrow these as they are, with your own timestamps:

• "The vocal feels buried at 1:12."
• "2:10 to 2:25, the guitars crowd the vocal."
• "The chorus should hit harder."
• "Her voice sounds far away in the verse."
• "The drums on this record, that's the energy I want, especially around 0:40."
• "Version 2 is the one. Approved."

Frequently asked questions

How do I give good feedback on a mix?

Listen to the whole mix, then describe the changes you want with timestamps or marked ranges. Gather the notes into one list, clarify any conflicting requests and confirm the version you approve.

What if I don't know the technical terms?

Describe the sound you want in ordinary language. For example, say that the vocal should feel closer or that the chorus needs more impact. Ask the engineer about technical options if you want to discuss how to achieve that result.

Why can a louder version sound better?

Differences in playback level affect how we perceive tonal balance and detail. Match the loudness of the two versions before deciding which one you prefer.

How many rounds of feedback are normal?

Check your agreement with the engineer. Two or three rounds is one possible mixing package, but the allowance and price of further changes depend on the job. Collecting notes together makes each round easier to plan.

What should I listen on when reviewing a mix?

Start with speakers or headphones you know well, then check another familiar system, such as earbuds or a car stereo. Use the review file your engineer supplied; avoid judging tone or distortion from a voice memo or an additional low-quality encode.