Giving Feedback on Music
Feedback is the single biggest lever you have in the composing process — and how you give it decides whether the score gets better or the collaboration gets worse. The golden rule: describe the problem, not the solution. Tell your composer what isn't working and why; let them find the fix.
When your composer sends a cue and it isn't quite right, what you say next matters enormously — because feedback is the mechanism by which the score improves, and bad feedback can stall or sour the whole collaboration. The golden rule of giving music notes is the same one that governs directing any creative collaborator: describe the problem, not the solution. Your job is to identify what isn't working and, crucially, why — what the cue is failing to do for the scene — and then let the composer, the expert, find the musical fix. When a filmmaker jumps to prescribing solutions ("add more strings," "make it faster," "change the melody"), they usually misdiagnose the real issue and box the composer into a fix that may not solve it, whereas describing the actual problem ("this doesn't feel as tense as the scene needs," "the emotion here should be sadder, more resigned") gives the composer the information to find a solution you'd never have thought of. Good feedback is also specific (point to the exact moment and the exact issue, not "I don't love it"), timely (respond promptly so the process keeps moving), and constructive and kind (your composer is a creative partner, often an emerging artist doing great work for a modest fee — treat them accordingly). And remember the lessons of the last two chapters: don't give feedback about a demo's rough sound quality (judge the idea), and check that your "wrongness" isn't just temp attachment. Feedback done well is how a good cue becomes a great one.
How to give great music feedback
The rules of useful notes:
- Describe the problem, not the solution. Say what isn't working and why ("this doesn't feel dangerous enough"), not how to fix it ("add drums"). You identify the issue; the composer, the expert, finds the musical answer.
- Be specific. Point to the exact moment and the exact issue — "from 1:12 the energy drops when the scene should be building" beats "I don't love the middle." Vague notes get vague revisions.
- Frame it by function and emotion. Use the language from Chapter 6 — what the cue should do for the scene. "The love theme should feel more tentative here" is direction a composer can act on.
- Be timely. Respond to demos and drafts promptly. The process is iterative and often on a schedule; slow feedback stalls the whole score and frustrates your composer.
- Be constructive and kind. Lead with what's working, be honest about what isn't, and stay respectful. Your composer is a partner pouring heart into your film — good feedback protects the relationship.
- Consolidate and prioritize. Gather your notes into a clear, organized list rather than a stream of scattered messages, and separate must-fix issues from minor preferences. Respect the revision rounds you agreed to.
The problem is yours; the solution is theirs
The principle at the center of this chapter — you own the problem, the composer owns the solution — is the most important collaboration skill in the whole course, and it applies far beyond music. It works because of the same division of expertise from Chapter 6: you are the authority on what your film needs to feel and do, so you're perfectly positioned to identify when a cue isn't achieving that; but the composer is the authority on music, so they're perfectly positioned to figure out how to fix it. When you respect that division in your feedback — describing the problem clearly and leaving the solution to them — you get the best of both, and you often get a fix better than anything you could have prescribed, because the composer has musical options you don't know exist. When you violate it by prescribing solutions, two bad things happen: you frequently misdiagnose (the real problem with a cue that "needs more strings" might actually be its tempo or its harmony, which more strings won't fix), and you constrain your expert collaborator to your non-expert idea, wasting their skill. So train yourself, when a cue disappoints, to ask "what is this cue failing to do for the scene, and why?" and communicate that — "it's not landing the sadness," "the tension releases too early," "this feels generic when the moment should feel specific to her" — and then trust the composer to solve it. Layered on top of that core rule are the qualities that make feedback land well: specificity, so the composer knows exactly what and where; framing by function and emotion, so notes are actionable; timeliness, so the iterative process keeps moving; and above all kindness and constructiveness, because your composer is a creative partner, usually an emerging artist giving your film enormous value for a modest fee, and feedback delivered with respect (leading with what works, honest about what doesn't) keeps them motivated and generous, while harsh or scattershot feedback demoralizes them and degrades the work. Two guardrails from earlier chapters also belong in every feedback moment: don't critique a demo's rough sound (judge the musical idea, not the sample quality), and before you declare a cue "wrong," check whether it's genuinely failing the scene or just isn't your beloved temp. Finally, be organized and fair about revisions — consolidate your notes into a clear list, prioritize must-fixes over nitpicks, and honor the revision rounds you agreed to in the deal, because endless disorganized change requests are how a collaboration turns sour. Master this — describe the problem not the solution, be specific, timely, and kind, and respect the process — and your feedback becomes the tool that turns good cues into great ones and keeps your composer happily doing their best work for you. With the music dialed in through feedback, the next stage is making it sound its richest — recording and producing the score, which is next.
I used to give composers "solutions" — add strings, make it faster, change that note — and I was usually wrong about the fix, and always in their way. The cue that finally taught me better: I said "add drums to make it more exciting," she tried it, it was worse. Then I described the actual problem — "the tension keeps releasing when the scene needs it to keep building" — and she solved it with a rising sustained line and no drums at all. It was perfect, and nothing I'd have thought of. Now I only ever describe what's wrong and why, and let her find the how. State the problem, be kind and specific, and trust your expert to fix it.
Prep your collaboration in the Filmmaker Toolbox — build a spotting list, gather reference tracks and mood notes, and track cues and revisions — so working with your composer is organized and clear from the first conversation.