Last Updated 1 day ago
A sound report is a production audio log that helps editorial identify recordings and understand what happened during each take. It connects audio files with scene and take information, track identities and useful recording notes. Reports may be created on paper, in software, or from a recorder's file metadata.
Why Editorial Needs It
An audio folder can contain many similar takes, multiple microphones and recordings made without picture. File names alone may not explain which track contains a particular actor or why a take has an interruption. A sound report provides a practical route into that material without requiring the editor to rediscover every production detail by listening from the beginning.
For example, a scene may have a boom microphone, two radio microphones and a production mix. If a costume rustle affects one isolated track, a clear note can direct the dialogue editor toward another option. The report does not choose the final performance. It gives the people making that choice enough information to find and evaluate the available recordings.
Typical Information
A report commonly identifies the production, shooting date, sound roll or recording folder, scene, take and file. Depending on the workflow, it may also include timecode, duration, recording settings, track names and comments. The required fields should be agreed with the receiving editorial team rather than assumed from an unfamiliar template.
Track labels are particularly helpful when several channels travel in one polyphonic audio file. “Boom,” an actor or character identifier, and a clearly identified mix track convey more than a sequence of unexplained numbers. If channel assignments change during the day, the report and associated metadata need to describe the actual recording rather than an earlier setup.
Advertisement
Useful Notes Are Specific
Describe the problem and where it occurs. “Aircraft during final line” is more useful than “bad sound.” “Wild line recorded after take” tells editorial to look for another file. A note can distinguish an interrupted take from a complete performance with a limited technical issue, or flag an unusual sound that might otherwise be mistaken for a recording fault.
Avoid treating a brief note as a guarantee. A preferred or circled take can still contain an audio problem, and another take may contain a useful replacement phrase. Record what was observed and preserve alternatives. The sound report should assist editorial judgment rather than claim that all decisions have already been made on set.
Metadata and Exported Reports
Some recorders generate reports from the metadata attached to their recordings. Sound Devices documentation, for example, describes CSV reports built from WAV metadata with configurable header information. CSV is useful for opening and reviewing the log in spreadsheet software, but its availability and exact fields depend on the equipment and workflow.
An exported report reflects the information available when it was generated. If scene names, notes or track labels are corrected afterward, check whether the report needs to be regenerated. Also confirm that it covers the intended folder or roll. A technically valid export can still be incomplete if it was made from the wrong directory.
Relationship to Other Production Records
The camera report describes camera-side material and technical information. The script supervisor's notes track performance, coverage, continuity and other editorial observations. The sound report concentrates on the recorded audio. Consistent scene and take naming makes these records easier to compare, especially when several cameras share one sound recording.
Timecode can help locate and synchronize material, but the report does not itself prove that two devices were synchronized correctly. Likewise, having a report is not evidence that every audio file was copied successfully. Recording, logging, synchronization and backup verification are connected tasks with different checks.
A Reliable Handoff
Before handing over the day's material, compare the report with the actual files, check identifying information and confirm that unusual recordings are labeled. Include the report with the agreed audio delivery and preserve a copy with the production records. If a correction is made later, identify the revised version clearly so editorial is not working from conflicting logs. A small amount of accurate documentation can prevent a disproportionate amount of searching in post-production.
Advertisement