Beyond NTSC and PAL.

“NTSC to PAL” is still useful shorthand in a post-production conversation. It is not a complete specification for an HD or UHD master. The legacy television names often stand in for two rate families: 25/50 and 29.97/59.94. Resolution, scan type, frame rate and timecode counting are separate decisions.

Start with the actual media and the delivery specification. A UHD file can be 23.976, 24, 25, 29.97, 50 or 59.94 fps. “4K” alone does not tell you how fast its frames play, and a container’s reported rounded rate is not always its exact timebase.

Common rates in a digital workflow
Display nameExact rate used hereTiming family
23.976 / 23.9824000 / 1001Fractional 24
2424 / 1Integer cinema
25 / 5025 / 1 or 50 / 150 Hz workflows
29.9730000 / 1001Fractional 30
59.9460000 / 1001Fractional 60
30 / 6030 / 1 or 60 / 1Integer rates; distinct from 29.97/59.94

Use the fractions for timing calculations. In this guide, 29.97 and 59.94 are conventional labels for those rational rates, not literal decimal values truncated to two places.

Frames, fields and labels.

Check what the number in a format name actually measures. In 1080i59.94, 59.94 commonly describes fields per second: the frame rate is approximately 29.97. In 1080p59.94, there are approximately 59.94 complete progressive frames per second. The same distinction applies to 1080i50 versus 1080p50.

Avid’s documentation makes this explicit for 1080i/59.94 and 1080i/50. Do not select a 60-count timecode format merely because an interlaced file’s name includes 59.94. Check the media properties and the receiving system. Avid’s format reference.

Preserve frames, or preserve duration?

A calculation needs a policy. If you keep every original frame and change the playback rate, the clip runs for a different amount of time. This is a conform. If the programme must keep its original duration at a new rate, the media conversion must change how pictures are sampled or generated.

Preserve frames:
new duration = source frame count ÷ destination fps

Preserve duration:
target frame count = elapsed seconds × destination fps

The second result may not be a whole number. A delivery workflow must then resolve the frame boundary and processing method. Rounding a number is not a substitute for evaluating motion, cadence and audio synchronization.

Final Cut Pro offers rate-conform choices for mixed-rate media; Adobe also distinguishes interpreting a clip at another rate from its original interpretation. Those are media operations with visible results. A timecode calculation can help plan them, but does not perform them. Apple’s conform reference · Adobe’s interpretation reference.

Same frames. Different timing.

Take a 1,440-frame shot. At 24 fps it runs for 60 seconds. Conform those same frames to 25 fps and it runs for 57.600 seconds. At 24000/1001, it runs for 60.060 seconds.

Explore a frame-preserving conform.

Change the rates to compare physical playback durations. This example keeps every source frame and does not process a media file.

60.000 sOriginal playback duration
57.600 sConformed playback duration

Playback speed: 104.1667% of source speed. Frame count stays at 1,440.

For a 25 → 29.97 delivery that must preserve a 60-second duration, 60 × 30000/1001 ≈ 1798.202 destination frames. A real deliverable has whole frames; its exact end boundary and conversion method need to be agreed in the media workflow.

A useful delivery checklist.

  1. Identify the source’s exact rate, scan type and any embedded pulldown.
  2. Confirm the destination’s exact rate and required DF/NDF counting mode.
  3. Decide whether source frames or elapsed programme duration must stay fixed.
  4. Choose the conform or standards-conversion method in the media tool, then check motion and cadence.
  5. Verify the first frame, last frame, total frame count and audio sync against the delivery specification.

For UHD, include the expected raster and whether the recipient accepts the original rate. Delivery platforms may have different requirements for film, television and music video assets. Follow the actual destination’s specification rather than applying one platform’s rule to every master. Apple’s asset guide is one platform-specific example.

Where Timecode Pro fits.

Use Timecode Pro to work through timecode arithmetic and inspect values in your selected formats. Keep a frame-count display alongside a timecode display when comparing a conform.

Its format comparisons follow the selected presets. They are not a universal “preserve duration” media conversion. The physical-time equations above explain workflow mathematics; they should not be read as a promise that every app display or format conversion uses elapsed-time seconds.

For broadcast counting, continue with drop-frame versus non-drop-frame. For fractional cinema rates and pulldown, read from film to digital delivery.

Technical references

The numerical examples use exact rational rates and are rounded only for display. They describe timing, not an NLE’s interpolation quality.