Timecode Synchronization Setup Guide for Crews

A camera card labeled A-Cam, a sound roll labeled Day 4, and a slate that is four seconds off might not stop lunch. They can absolutely stop post. This timecode synchronization setup guide covers the practical decisions that keep cameras, audio recorders, monitoring, and timecode-capable lighting working from the same clock - without building a system that is more complicated than the shoot.

Timecode is not glamorous gear. Nobody gathers around video village to admire it. But when it is planned correctly, assistant editors can sync a day’s footage quickly, sound can match takes with confidence, and the crew avoids the classic end-of-day question: which device is actually right?

Start With the Deliverable, Not the Box of Cables

A reliable timecode workflow begins before anyone jams a camera. Confirm the production frame rate, recording frame rate, delivery frame rate, and whether the job requires drop-frame or non-drop-frame timecode. Those details sound similar until they are not, and mixing them is a fast way to create clips that appear to drift or land on the wrong edit points.

For most narrative, commercial, and documentary work, production should designate one timecode standard for every device that records picture or sound. Write it on the camera report, sound report, and call sheet where appropriate. A common setup might be 23.976 fps non-drop-frame for a scripted project, or 29.97 drop-frame for broadcast-oriented work. Do not assume a camera’s project frame rate automatically means its timecode mode matches. Check both menus.

Also decide whether time-of-day code or record-run code serves the job. Time-of-day is generally the practical choice for multi-camera shoots because every clip carries a timestamp that corresponds to the day. Record-run can be useful for a tightly controlled single-camera workflow, but it becomes less friendly once multiple cameras, separate audio, pickups, and second units enter the picture.

Choose a Master Clock That Fits the Shoot

The master clock can be a dedicated timecode generator, a sound recorder with a stable internal clock, or a production-approved master source. On a small owner-operator job, a pair of compact wireless timecode boxes may be all that is needed. On a larger production, sound often manages the master clock and distributes jammed or continuously fed code across cameras and recorders.

A dedicated generator is usually the safest choice when you have multiple cameras, long takes, or a shoot that runs all day. Look for a unit with a stable temperature-compensated oscillator, clear status display, appropriate I/O, and the ability to set frame rate and time-of-day code precisely. Wireless monitoring and control can be useful, especially when cameras are mounted on gimbals, vehicles, or locations where accessing ports repeatedly is not realistic.

The trade-off is simple: wireless timecode saves handling time, but it does not remove the need to verify the device is receiving valid code. A hardwired jam is still a good habit at call, after a battery swap, and whenever a device has been powered down or changed modes. Wireless is helpful. Confirmation is better.

LTC, embedded timecode, and why connectors matter

Most field timecode workflows use LTC, or linear timecode. It is an audio-like signal carried through connectors such as BNC, LEMO, 3.5 mm locking mini-jack, or 5-pin interfaces depending on the equipment. The connector does not tell you everything about the signal, so check the camera or recorder manual and use the correct cable wiring.

A cable that physically fits can still be wrong. Some devices need a dedicated timecode input cable, while others use a combo sync or audio port with a menu setting that must be enabled. Keep cables labeled by connector type and purpose. The tiny black adapter at the bottom of a pouch is not the place to discover pinout differences while talent is ready.

Embedded timecode is different. SDI and HDMI feeds can carry timecode metadata, but whether a monitor, switcher, recorder, or wireless video system preserves it depends on that specific signal path. If post needs timecode from a video assist recording, test the whole chain before the shoot. Do not assume an SDI cable passing picture also guarantees usable metadata at the other end.

How to Jam a Basic Camera and Audio Package

Set the master generator first. Select the approved frame rate and drop-frame setting, set the source to time-of-day or the required production time, and confirm it is counting correctly. If the production uses a specific date and user bits convention, set that before distribution.

Next, set the audio recorder to external timecode and match its frame rate exactly to the master. Feed LTC from the master into the recorder’s timecode input, jam the recorder, then confirm the displayed value agrees with the master. If the recorder can remain locked to an external source during the day, that can add security on a cart-based setup. If it will run independently, confirm its internal generator is suitable for the planned runtime.

Then move to camera. In the camera menu, choose external timecode, select the matching frame rate, and confirm whether the camera is configured to jam-sync, continuously lock, or use its internal generator after jamming. Connect the correct cable, let the camera read the incoming signal, and verify the displayed code against the master. Record a short test clip and inspect the metadata in the intended post workflow if time permits.

For cameras with removable batteries, check whether timecode holds through a power change. Some cameras retain jammed code for hours; others lose it quickly without external power. The answer changes how often the AC team needs to re-jam. Build that step into battery changes instead of making it an emergency.

Add Wireless Timecode Without Creating New Failure Points

Wireless timecode boxes are especially useful for compact cinema cameras, DSLR and mirrorless bodies, car rigs, Steadicam, gimbal work, and any camera that moves away from the sound cart. Mount the unit where the display can be checked without disrupting the operator, secure the cable with strain relief, and avoid placing the antenna or unit where it will be crushed by a cage, battery plate, or rain cover.

Each receiver should be assigned to one device and labeled accordingly: A-Cam, B-Cam, sound, or video assist. That sounds basic, but identical boxes migrate between carts quickly. Labeling helps the crew know what was jammed and what still needs attention.

Before first shot, compare every display against the master. A difference of one frame may be a configuration problem, while a difference of several seconds usually means the unit was not jammed, was set to a different frame rate, or is displaying a different mode. Fix it immediately. Post can work around many things; mismatched timecode across a full shooting day is not a favor.

Do Not Confuse Timecode With Genlock

Timecode identifies when a frame was recorded. Genlock controls when cameras begin their scan or frame timing. They solve related but different problems.

For standard single-camera or two-camera work, matching timecode is usually sufficient for post synchronization. For multi-camera live work, virtual production, broadcast switching, high-speed integration, or certain LED volume and playback environments, cameras may also need genlock or tri-level sync. In those cases, a master sync generator, distribution amplifier, and properly terminated reference lines can matter as much as LTC.

The practical rule is to ask the DIT, video engineer, or post supervisor what the system needs. If the requirement is frame-accurate switching, timecode alone is not the answer. If the requirement is efficient editorial sync between camera and sound, genlock may add cost and complexity without providing a useful benefit.

Timecode and Lighting Control: Use It Where It Earns Its Place

Timecode can also drive cue-based lighting and effects workflows. DMX control systems, pixel-mapped fixtures, practical effects, playback, and certain specialty lighting ecosystems can follow a programmed timecode timeline. This is valuable when a lighting cue must repeat exactly across multiple takes, such as interactive car-process work, music performance playback, or a practical screen sequence.

The setup needs a defined master. If playback is the timing authority, lighting control may need to chase playback timecode. If the camera or a central show-control system is the master, configure the lighting console or interface to receive the same frame rate and start time. Test a full cue sequence, including stops, resets, and take restarts. A cue that looks perfect during a rehearsal but resets to the wrong timestamp at take one is a very expensive blinking light.

For straightforward interview, tabletop, or narrative coverage, timecode-controlled lighting is often unnecessary. Use it when repeatability is the point, not because the fixture has a port that can do it.

Run a Verification Routine at Call and After Lunch

A small verification routine prevents most timecode trouble. At crew call, compare the master to every camera, recorder, and wireless unit. Confirm frame rate, drop-frame status, source mode, and battery level. Record a brief camera-and-sound test, including a slate if the production uses one.

After lunch, after a major battery cycle, after moving to a second unit, and after any camera menu reset, check again. Keep a short log showing device, frame rate, jam time, and crew member who verified it. This is particularly helpful when the package includes rented cameras, specialty rigs, or multiple operators.

Carry the unglamorous support gear too: the correct timecode cables, adapters, spare generator batteries, fresh media for test clips, labels, and a way to secure small boxes to cages or carts. The generator is only one part of the system. The cable you forgot is usually the part that wins.

When timecode is treated as a quick department handshake rather than an afterthought, the camera team, sound team, and post team all get a better day. Set the standard, verify the path, and make every device prove it is on the same clock before the slate goes up.