Broadcast Leader Builder

What a broadcast leader is (and why it survived file-based delivery)

A broadcast leader — sometimes called a head leader or pre-roll — is the standardized run-up that precedes program content on a broadcast master: color bars and reference tone, a slate identifying the show, black separating each element, and a one-frame sync marker called the 2-pop, all timed backward from an exact program start timecode (typically 01:00:00:00 for US network delivery, 10:00:00:00 for UK DPP/AS-11). It dates from tape, where an engineer needed something to calibrate a machine to and confirm sync before the program itself rolled. File-based delivery removed the physical tape, but not the need: encoders, transcode farms and QC stations still need a calibration reference, a human-readable ID, and — because sync can still drift across a multi-generation encode chain — a frame-accurate way to prove picture and audio line up. So the leader survives, largely unchanged in structure, as a QC convention baked into nearly every network and platform delivery spec.

What each segment does

Bars & tone calibrate the playback chain before anyone looks at picture: SMPTE color bars (or EBU bars in the UK) give a video reference for levels and color, while 1 kHz reference tone — typically −20 dBFS on US masters, −18 dBFS on UK/EBU masters — gives an audio level reference so a QC operator or automated system can confirm the chain reads correctly before program starts.

The slate is the human-readable identification: production or show title, episode or segment number, total running time (TRT), audio channel configuration, timecode standard, and delivery version, so anyone who pulls up the file — weeks or years later — knows exactly what it is without opening a spec sheet.

Black is a deliberate settling buffer: it keeps bars, slate and program from bleeding into each other, and stops a viewer, or an automated ingest system, from being jolted by a hard cut straight from tone into program audio.

The 2-pop is a single frame of 1 kHz tone paired with a single white (or numbered) video frame, placed at exactly two seconds before program start. Its job is sync verification, not calibration: if the beep and the flash line up exactly on playback, picture and audio are in sync; if the pop's flash and beep have drifted apart by even a frame, something in the delivery chain shifted audio relative to video. That is exactly why file-based masters still carry one — a transcode, a frame-rate conversion, or a bad conform can introduce precisely the kind of drift the 2-pop is built to catch, and it catches it in a single glance rather than requiring a full A/V sync review.

Drop-frame vs non-drop: why the leader's timecodes shift with frame rate

At 29.97 fps, video runs at exactly 30000/1001 frames per second — about 0.1% slower than a true 30. Non-drop timecode (NDF) still labels 30 frames every counted second, so it drifts about 3.6 seconds behind the wall clock per hour. Drop-frame timecode (DF) fixes this by skipping frame labels 00 and 01 at the start of every minute except minutes divisible by ten — no video frames are removed, only their numbers.

Here is the leader's 2-pop worked through the arithmetic, at 29.97 DF, with program starting at 01:00:00;00:

• 01:00:00;00 converts to an absolute frame count of 107,892 — one hour of DF timecode is always 107,892 frames: 108,000 nominal frames minus 108 dropped labels (2 labels × the 54 non-exempt minutes in that hour).
• The 2-pop sits two seconds earlier, at 00:59:58;00, which converts to 107,832 frames.
• 107,892 − 107,832 = 60 frames exactly — precisely 2 seconds × 30 nominal frames, with no drop-frame adjustment landing in between.

That clean result isn't a coincidence to generalize from carelessly: it comes out to a full 60 frames here specifically because the boundary this 2-pop crosses lands on minute 60 (01:00), which is divisible by ten and therefore exempt from the drop rule. Land the same 2-second gap on a non-exempt minute rollover instead — say, a program starting at 00:01:00;02, the first label that exists in minute 01 — and the 2-pop's label is 00:00:58;00: the two labels skipped at the boundary (00:01:00;00 and 00:01:00;01) make the labeled gap between pop and program read 62 frames even though the real elapsed time is still exactly 2 seconds (60 frames). This tool always computes leader positions as absolute frame counts first and converts to labels last, specifically so it never falls into that trap.

US network vs UK DPP conventions

What goes on a slate

These are typical conventions, not universal law — always confirm the exact leader structure, tone levels and slate fields against the specific network or platform's own delivery spec before building a master. Use the timeline above to lay out any of the three presets, or switch to Custom to match a spec that doesn't fit the templates.

1. Choose a convention preset: US network, UK DPP/AS-11, or a theatrical and festival leader.

2. Enter your program start timecode and frame rate, and the timeline works backward from that point to place every segment.

3. Read the in and out timecode for each segment, and check any follow-on arithmetic in the Timecode Calculator.