# How to Give Mix Feedback and Avoid Endless Revisions > Turn comments like “it needs more punch” into useful notes: the version, the moment, the intention, and a list of changes agreed on with the team. Author: Roye URL: https://wuse.works/en/blog/mix-feedback/ ## A useful note pinpoints what you're hearing When giving mix feedback, include the version, the moment in the song, what you're hearing, and the result you want. A note like “v03, 01:12: the vocal loses clarity when the guitars come in; I want to make out the line” gives more context than “turn up the vocal.” In wuse, you can keep files and versions inside the music project. In an r/audioengineering discussion about unrealistic revisions, commenters suggest clarifying the client's intention, keeping alternative versions, and agreeing on revision limits. There's no universal rule for musical taste, but you can improve how you communicate it. ## Separate the intention from the technical solution Maybe you want a vocal that feels closer, a more intense chorus, or drums that don't get in the way as much. Describe that goal before asking for a specific adjustment. The engineer may suggest another way to get there and explain the trade-offs involved. For example: “In the second chorus, the vocal feels far away; I want it to feel as close as it does in the first verse.” If you have an outside reference, point to the section and explain which quality you're after. Asking for the whole song to sound like another track can overlook differences in the arrangement or performance. ## Review a specific version Choose the file you're collecting feedback on and share its name with the team. Keep previous versions, but ask whether an old comment still applies before carrying it over to the current mix. Use a simple naming convention, like Horizonte_mix_v03.wav. When the audio changes, increase the version number. If you're only correcting a written note, you don't need to invent another mix. The goal is to know what each person listened to. If you need to hear what changed before commenting, see how to [compare versions while keeping your listening position](/en/how-it-works/#version-comparison). Switch between bounces in the same project without finding the passage again. ## Bring the feedback together before another round If one artist asks for more vocal and another asks for less, sending both messages separately doesn't settle the decision. Pick one person to gather the comments and send back a consistent list. Discuss differences of opinion before asking for changes that conflict. Once you have a consistent list, you can [organize feedback in a review round](/en/how-it-works/#review-rounds): the recipient collects timed notes and the team resolves each point before closing the round. - Identify errors you can verify: cutoffs, noises, or missing elements. - Separate balance adjustments from new arrangement decisions. - Resolve requests that contradict each other. - Agree on which changes go into this round. - Specify who will confirm the result and when. ## A feedback template you can copy Example: “File: Horizonte_mix_v03.wav. Moment: 01:12–01:24. What I hear: the last line is hard to make out. What I want: for the vocal to stay up front when the guitars come in. Priority: high. Reference: the first verse of this same version.” You can use this structure even without technical vocabulary. If your comment applies to the whole song, say so explicitly. And if you're not sure what's happening, ask a question: “Can we compare an alternative where the vocal feels closer?” ## Agree on when revisions end Before you start, define what a round of mix revisions covers, how many rounds the job includes, and how you'll handle production changes. Replacing the vocal or adding instruments can change the scope of the job; it's best to explain that before making those changes. When you receive the next version, check the agreed list first. If you want to return to an earlier decision, reference the relevant file and explain why. For a useful comparison, try to listen to the alternatives at a similar volume. ## Keep the decision close to the music In wuse, you can keep versions inside the music project and share the material with the team. Include the version name in your notes to preserve the context of each revision. When you wrap up a round, leave a note with the accepted changes and anything still pending. You don't need to call a file “final” to approve it: you need everyone involved to know what decision they've made. To record the chosen version, see how to [request approval of one exact audio file](/en/how-it-works/#final-approval). Audio approval and signing a participation agreement are separate records. ## Frequently asked questions ### How do I ask for a change if I don't know about mixing? Describe the moment, what you're hearing, and the result you want. You don't need to name a plugin or a technical adjustment to explain your intention. ### How many revisions should a mix include? It depends on the job and your agreement with the engineer. Before you start, agree on what each round covers and how you'll handle production changes. ### What should I do if two collaborators ask for opposite changes? Gather the feedback and settle the decision before sending the next list of changes. One person can coordinate the team's response. ### Are comments on an earlier version still useful? Check whether the issue is still there in the current mix. Reference the earlier file when you want to compare or return to a previous decision. ### How do I know the mix is approved? Confirm who makes the decision and keep a record of the accepted file and anything still pending. A name like final.wav doesn't communicate approval on its own. ## About Roye Roye writes wuse's guides on music production and collaboration. Under the name Dibo Roye, he has public production credits for ALE ALAS and songwriting credits for Tillaz.