Timecode on Set: What It Solves and What It Does Not

A time label is not the whole sync system

Timecode assigns a time reference that editorial can use to align pictures with separately recorded sound. It is useful for multiple cameras, long interviews and productions with many clips. For those numbers to mean the same thing across the system, camera, sound and post-production need to agree the workflow and responsibility for settings before filming begins.

Timecode is not automatically interchangeable with the clocks that govern audio sampling or with video frame synchronisation. Matching numbers on two displays do not by themselves guarantee that long recordings will never drift apart. The available synchronisation options depend on the equipment and its connections. Test the complete arrangement instead of treating a photograph of matching displays as proof that everything is correct.

Agree the reference and settings

Before the shoot, decide where the time reference comes from and who checks that each device receives it correctly. Confirm the project frame rate and the relevant timecode mode. Similar-looking values are not necessarily interchangeable. If camera settings change, sound and editorial need to know; otherwise the recorded material may be interpreted differently from what the crew intended.

Jam sync refers to setting a device’s timecode generator from a reference. How long that device maintains suitable accuracy, and what happens after a battery change or restart, must be checked in the documentation for the actual equipment. There is no single checking interval that suits every configuration and every environment. Establish a procedure around the system that will really be used.

Check a long take as well as the start

Run a test that resembles the planned recording. Short clips may appear correct even when a longer continuous take reveals a problem. Checking alignment at both the beginning and end of a longer test helps distinguish a fixed offset from progressive drift. Involve the person who will receive the material in post-production so that the test also covers the intended ingest process.

A slate remains a useful visual and audible reference. It supports verification and can help when metadata is missing or the planned system did not behave as expected. The slate must still be visible, audible and clearly identified. For documentary events that cannot be interrupted, agree an appropriate alternative identification and checking method in advance.

Record changes instead of assuming continuity

After a restart, equipment change or unexpected interruption, check synchronisation according to the agreed procedure. If an exception occurs, identify the affected clips and explain it in the sound report. Editorial needs to know what changed and from which point, rather than receiving only a vague warning that there was a timecode issue somewhere during the day.

When arranging production sound, provide the number of cameras, the expected duration of continuous takes and a post-production contact. Timecode can then become part of a tested workflow. Its value is better organisation and more efficient alignment, but it does not replace listening, a slate where appropriate or verification of the actual result in editorial. A modest system with clear responsibility is more useful than an elaborate arrangement that nobody has tested from recording through import.

Test material need not be visually interesting, but it needs a clearly recognisable shared event and enough duration to assess the system. Briefly record the result. If equipment changes later, the team can see which assumptions were tested and which need checking again. Assign responsibility to a specific person rather than vaguely to the crew as a whole.