Revisions work best when feedback is specific, consolidated and connected to the agreed brief. “Make it bigger” can mean more low end, a wider chorus, stronger transients or simply more level. The engineer needs to know what you hear and where it happens.
Listen before sending notes
Play the full mix on more than one system and take notes with timestamps. Separate essential issues from preferences. Instead of “the vocal is wrong,” write “the lead vocal is difficult to understand in the second verse around 1:05” or “the delay tail masks the last word of the chorus.”
Compare versions fairly
Match playback loudness when comparing revisions. A louder version can seem better even when the balance has not improved. Avoid changing several unrelated things at once; otherwise it becomes difficult to identify which decision helped.
Understand what counts as a revision
Small balance, EQ, compression or effect adjustments are usually mix revisions. Replacing a recorded part, rewriting the arrangement, recording new vocals or changing the creative direction may be additional production work. Agree on the included revision rounds and the point at which a new brief changes the scope.
Give the engineer useful context
- Describe the intended feeling and reference, not just plugin settings.
- Send one consolidated list rather than many messages throughout the day.
- Identify what must not change as well as what needs attention.
- Approve the final version only after checking the agreed formats.
Takeaway: precise feedback saves time and keeps the project focused. The goal is not to win an argument about taste, but to make the final mix serve the song.
R MUSIC RECORDS