Timecode Sync
Timecode sync is the practice of running all recording devices on a shared, frame-accurate clock.
What this is about
On a multi-camera or dual-system shoot, each device has its own internal clock, and internal clocks drift. Jamming — feeding a reference signal into a device — sets them to the same time; small sync boxes on each camera keep them there. Without this, a two-camera interview slowly slides out of sync over the day, and post pays the price in manual alignment. The rule of thumb: jam at call, re-jam after breaks, and never trust a device that was powered off.
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:
- Jam at call, re-jam after every break — power cycles reset some clocks
- Sync boxes on each camera beat one-time jamming for long days
- Audible claps remain a worthwhile backup even with timecode everywhere
With TillyGen
For multi-camera days, TillyGen's schedule can carry a sync-check reminder at call and after lunch, right where the crew reads its day.
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 I still need a clap if everything runs timecode?
It is cheap insurance. If a box fails or a device was not re-jammed, the clap gives post a visible and audible sync point to fall back on.
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.