Timecode

The TC chip in the top banner opens the timecode sheet: Rec-Run / Free-Run count-up, drop-frame, HDMI output and a one-tap reset to 00:00:00:00 — everything needed to sync multi-cam shoots.

Every Multi View window carries a TIMECODE badge bottom-left (video mode only): the running TC, REF on the first connected window, ✓ when a window is within one frame of it, ▲/▼ Nf when it runs ahead/behind (amber up to 3 frames, red beyond). It counts in red while that body records. The badge replaces the timecode that used to trail the name chip.

TIMECODE JAM (Multi View bar, TC JAM chip next to Discon) syncs every connected body in one tap. The sheet lists each camera with its live timecode and, after a jam, its offset against the first camera in frames (green ≤ 1, amber ≤ 3, red beyond). Pick REC RUN (counts only while recording — the jam aligns the start value) or FREE RUN (counts continuously — true multi-cam sync), a START (phone clock, zero, or a manual HH:MM:SS:FF) and drop-frame (offered only at 29.97 / 59.94 fps). JAM switches Record timecode ON, writes the count-up method and drop-frame, measures each camera's round-trip and fires the same origin to all of them so it lands at the same instant (~1 s lead, per-camera latency compensated). Cameras that are recording are skipped — Nikon locks the timecode menu during REC — and a camera that refuses the write is reported without stopping the others. Expect ±1–2 frames over Wi-Fi; the offset column is your verification. NDF / DF = non-drop-frame / drop-frame counting: at 29.97 and 59.94 fps a drop-frame timecode skips two frame numbers every minute (except every tenth) so the count stays on the wall clock; at integer rates the toggle is disabled and NDF is the only option. Demo cameras have no PTP session and are reported as "nothing to jam"; a camera that refuses the value shows the reason in words (e.g. "Invalid property value") and the native log records the exact encoding attempts for that body.