From film to digital delivery

Start with what was actually captured.

“Film to video” can mean a physical scan, an inherited telecine master, or a modern digital-camera production shot at a cinema rate. Those sources need different treatment. Begin with the acquisition rate, the scan or recording rate, and the source’s frame identity.

A 24 fps camera original, a 23.976 progressive file and a 29.97 interlaced telecine can contain related pictures without sharing the same timebase or cadence. Before changing anything, establish whether pulldown is present, whether the source has already been conformed, and which identifiers must survive the handoff.

The 24 / 23.976 / 25 decision.

When a conform preserves every source frame, playback duration changes with the destination rate. For the same 86,400 frames, the physical timing is:

At 25 fps, the running time is 57 minutes 36 seconds. The speed increases by approximately 4.1667%, while the duration decreases by 4%. Those percentages use different denominators; they are not interchangeable.

Moving from 24000/1001 to 25 fps is a different conform: its speed factor is approximately 104.2708%. Using a generic “4%” instruction without the exact source rate can create a timing error.

Adobe’s interpretation guidance describes a conform as changing the reference playback rate, rather than rewriting the source file. The timing above is calculated from the rational rates; it does not describe motion-interpolation quality. Adobe’s footage-interpretation reference.

Pulldown is a cadence.

For a conventional 23.976 → 29.97 interlaced telecine, a 2:3 field cadence distributes four progressive source pictures across five interlaced video frames. That is a representation change; it is not the same operation as playing every source frame at a new rate.

If a source already contains pulldown, identify the cadence before removing it. Inverse telecine can recover the underlying progressive picture sequence when the source and cadence support it. Deinterlacing an arbitrary video source is not automatically inverse telecine. Adobe’s fields and pulldown reference.

A modern progressive delivery may accept the original 23.976 or 24 fps source and need no telecine at all. Do not add a historical broadcast cadence just because a destination is described informally as “NTSC.” Check the delivery’s rate, scan and cadence requirements.

Scans, frames and footage.

For scanned film or an image sequence, a frame count is only useful when its origin is known. Record the first image identifier and the sequence’s numbering convention. An image named shot_1001 is not necessarily frame 1,001 from the head of the original camera roll.

If you calculate an inclusive sequence length, a range from frame 1001 to frame 1240 contains 1240 − 1001 + 1 = 240 images. The offset between those two frame positions is 239 frames. Specify which quantity you mean in a turnover.

Physical footage adds gauge and perforation assumptions. For a 35 mm four-perforation format with 16 frames per foot, 90 feet contains 1,440 frames. At 24 fps that is 60 seconds; at 24000/1001 it is 60.060 seconds. A different gauge or perf arrangement changes the footage-to-frame relationship.

Adobe’s time-conversion reference exposes frames-per-foot as an explicit parameter. That is the useful principle for a digital turnover too: carry the assumption, rather than treating “feet” as a universal frame count. Adobe’s time and footage conversion reference.

Picture timing and audio timing travel together.

A frame-preserving conform changes the duration of the picture. Audio must be handled deliberately to retain sync. Whether pitch is allowed to change, or is corrected during a stretch, is a separate sound decision. Avoid treating a changed metadata rate as a complete picture-and-sound deliverable.

Adobe notes that footage interpretation can alter picture duration without correspondingly changing a separate audio track. Verify sync after the actual operation in the tool that performs it. Adobe’s conform and audio note.

1. Write down source acquisition rate, current file rate and destination rate.
2. Identify whether the job preserves source frames or programme duration.
3. Record any pulldown, conform or audio pull already applied.
4. Retain image-sequence origins, film identifiers and reference timecode.
5. Check the actual master’s frame count, first/last frames, audio sync and delivery metadata.

Delivery rules are platform-specific. Apple’s asset guide, for example, distinguishes film-sourced progressive assets and inverse-telecine material, with different requirements by delivery category. Use the receiving service’s current specification for the job. Apple Video and Audio Asset Guide.

Turn the assumptions into a calculation.

In Timecode Pro, choose the relevant film gauge, footage unit and rate, then keep a frame-count and video-timecode comparison visible. Use history to preserve the working behind a result you need to pass on.

The app’s format presets define its conversion behaviour. In particular, a format comparison is not a media conform or a universal guarantee of preserved clock duration. Treat the equations here as physical playback mathematics, and verify the app display appropriate to your chosen workflow.

Continue with frame-rate conversion in HD and UHD for mixed-rate delivery decisions, or drop-frame versus non-drop-frame for the counting convention.