Module 6

Sound

Module 6. The half of your film that decides whether anyone believes it. It arrives after picture for a reason, it is the cheapest thing in your pipeline, and almost nobody in this market does the layer that actually works.

6 · Claude Code for Filmmakers1 / 16

The test you already know

Cut your best shot against silence. Then cut it against a room tone, a coat rustle and a distant street.

Same frames. One of them is footage and one of them is a film.

Nothing else in this pipeline changes perceived production value as cheaply as sound does, and nothing else is skipped as often.

6 · Claude Code for Filmmakers2 / 16

Why it comes after picture

You score to picture. You do not generate picture to fit a track you already love.

The moment the music exists first, every timing decision in the film is hostage to it, and you will cut a good shot to protect a bar.

6 · Claude Code for Filmmakers3 / 16

Three layers, and they are not equal

LayerWhat it costs youWhat it buys
Voicethe most attentionthe story, if there is dialogue or narration
Musicthe most tastethe emotion, and the pace
Effectsthe least of boththe belief

Effects are the highest return and the most skipped. A room tone under every interior and a footstep on every step will do more for your film than a better music cue.

6 · Claude Code for Filmmakers4 / 16

Off the same file, again

Your dialogue is already in shots.json if you wrote it there in Module 2. If it is not, it belongs there now, not in a separate script document that will drift.

"Add a dialogue field to every shot that has a line, taken from the script. For each one, note who says it and the delivery in three words or fewer. Flag any shot where the line is longer than the shot's duration can hold."

That last clause catches the thing you would find in the edit. A nine second line in a four second shot is a problem you want in Module 6, not Module 7.

6 · Claude Code for Filmmakers5 / 16

The delivery note is the whole job

Voice models take direction badly when the direction is vague and well when it is physical, which is the same rule as the camera notes in Module 4.

VagueSurvives
"emotional"quiet, almost whispered, breath before the last word
"angry"clipped, faster than normal, no pauses
"tired"slower, dropping at the end of every phrase
Tip

Generate three takes of every line, not one. Voice is the cheapest thing you will generate and the one where take three is most often the one.

6 · Claude Code for Filmmakers6 / 16

The thing to be careful about

Watch out

A voice is a person. Cloning one you do not have permission to use is not a technical question, it is a rights question, and it is the kind that follows a film.

Get permission in writing for any real voice, including your own actors, and keep it with the project. If you are using a synthetic voice, note which model and which settings in the log, the same as a seed. You will be asked, at delivery, what is in your film.

6 · Claude Code for Filmmakers7 / 16

Music: decide the shape before you generate

The mistake is generating sixty seconds of "cinematic emotional" and cutting your film to whatever came back.

"From shots.json, write me a music map: where a cue starts, where it stops, what changes in the film at that point, and the total seconds of each cue. One row per cue."

Then generate to that map. You are commissioning a cue with a length and a job, which is what a composer would have asked you for.

6 · Claude Code for Filmmakers8 / 16

Effects: the list you would never write by hand

This is where the file pays off completely. Every shot already describes its own world.

"For every shot, read the action line and list the sounds that must exist for it to be believable. Separate them into room tone, foreground actions and background world. Write it to audio/spot-list.md, grouped by shot."

That is a spot list, the thing a real sound editor builds first, and you now have one for a forty shot film in about a minute.

6 · Claude Code for Filmmakers9 / 16

It cannot hear

Same limit as Module 5, in the other sense.

It cannot tell you the read is flat. It cannot tell you the cue is wrong for the scene, or that the footstep sounds like a different floor.

It can tell you:

  • Which shots have dialogue but no voice file
  • Which files are silent, clipped, or the wrong sample rate
  • Which cues are longer or shorter than the map said
  • Total runtime of every layer against the length of the film
"Check the audio: every shot with dialogue has a take, nothing is zero-length or clipping, everything is 48 kHz, and every cue matches the length in the music map."
6 · Claude Code for Filmmakers10 / 16

Loudness is a spec, not a taste

Every platform has a delivery loudness, and "it sounds fine on my laptop" is not a spec.

"Read my delivery spec and check the mix against it: integrated loudness, true peak, and whether we are inside tolerance. Tell me the numbers and whether it passes. Do not change anything."

Numbers, then a pass or fail, then you decide. Your studio ships a loudness check for exactly this, and it reports rather than fixes, on purpose.

Do this

Ask for the measurement before you ask for the fix. A tool that normalises without showing you the number has taught you nothing and may have flattened your dynamics.

6 · Claude Code for Filmmakers11 / 16

The mix is still yours

Everything in this module prepares, lists, generates, checks and reports.

The balance between her voice and the street is a creative decision, and it is yours.

6 · Claude Code for Filmmakers12 / 16

Do it now

6 · Claude Code for Filmmakers13 / 16

The exercise

Your film from Module 5. Sound is the fastest module in this course.

  1. *"Add dialogue to every shot that has a line, with a three word delivery note. Flag lines too

long for their shot."*

  1. Fix the flags. Usually this is trimming words, and it improves the writing.
  2. "Write the music map from shots.json, one row per cue, with lengths."
  3. "Build audio/spot-list.md: room tone, foreground, background, grouped by shot."
  4. Read the spot list. Cut half of it. A spot list is always too long on the first pass.
  5. "Queue it all. Three takes per line. Log everything. Report at the end."
  6. "Check the audio and report anything missing, silent, clipping or off spec."
6 · Claude Code for Filmmakers14 / 16

What you should have now

  • Dialogue living in shots.json with the picture, not in a document beside it
  • A music map with real lengths, so you commission cues instead of hoping
  • audio/spot-list.md, a genuine spot list for the whole film
  • audio/<shot_id>/ with takes, versioned, and a log of what made each one
  • A loudness measurement against your actual delivery spec

Your film has a sound track that was designed rather than found.

6 · Claude Code for Filmmakers15 / 16

Next: Module 7

Edit. Assembling the thing, the paper edit that gets you there in one sitting, and the point where the tool hands the film back to you for good.

Verified against Claude Code 2.1.220 · 2026-07-30.

6 · Claude Code for Filmmakers16 / 16
Keys space next  ·  back
Or click the arrows, the sides of the frame, or the bar along the bottom
Home / End first / last
S presenter notes
A scroll-all view, then ⌘P to make a PDF
F fullscreen  ·  ? this help
NextEditContinue ›