Sound Report

A sound report is the recordist's take-by-take log of everything captured on the sound recorder.

What this is about

For each take the report lists timecode, file name, which mic sits on which track, and remarks: plane overhead, line off-mic, wild track follows. Modern recorders generate much of this digitally, but the remarks are human judgement and remain the valuable part. In post, the dialogue editor reads the report before opening a single file — it says which takes are worth loading and where a clean alternative exists. A missing report turns that into archaeology.

A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.

What runs differently here

Where this differs from the general case:

  • Track layout notes save post from guessing which channel carries which mic
  • Remarks about noise events are worth more than any auto-generated metadata
  • Hand the report over with the sound files — not weeks later

With TillyGen

When scene numbers in the sound report match TillyGen's plan, production paperwork and post logs line up without translation.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.

Frequently asked

Do digital recorder metadata replace the sound report?

They replace the typing, not the judgement. File names and timecode come free; the note that take three has a plane in it still needs a human.

How long does it take to get started with TillyGen?

A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.

Can the results be exported?

Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.