To read a Resolve position in seconds, first identify its display: timecode, total frames or Fusion frames. Timecode already includes seconds; its last pair counts frames. Decimal seconds require conversion or, for audio work, a seconds-based display in Audacity.

This guide covers locating a point in an edit and expressing its position as elapsed seconds. The Resolve instructions follow Blackmagic Design’s DaVinci Resolve 21.1 Reference Manual, including its Fairlight and Fusion chapters. The separate Fairlight training guide cited below covers Resolve 20.

Which display are you trying to change?

Resolve has several timing displays with different controls. Before changing a setting, identify whether you are reading the main edit, an animation editor or a Fusion composition. The following decision aid brings together the documented options; it is not a single application-wide setting.

Where you are working Supported approach What you get
Main Edit timeline Right-click its timecode display to choose the timing representation Timecode, frames, subframes or audio sample information
Keyframe Editor or Curve Editor Choose Display Time Ruler in Seconds in that editor’s option menu Timeline-based HH:MM:SS:FF
Fusion composition Change the time display through Fusion settings Frames, SMPTE timecode or feet and frames
Fairlight timeline Read its playhead timecode and range fields Timeline position and range timing
Audio in Audacity Choose a seconds format for the appropriate readout Whole seconds or seconds with milliseconds

These distinctions follow the Resolve 21.1 Reference Manual, particularly pages 854, 1258–1263, 1302 and 3750–3751, and Audacity’s playhead-position documentation.

The important boundary is that Blackmagic’s documented Display Time Ruler in Seconds command belongs to the keyframe and curve editors. Its output still includes frames. The cited sections do not establish a global decimal-seconds mode for the main Resolve timeline, so use the specific path that matches your task.

How do you read seconds in Resolve timecode?

Standard timecode uses HH:MM:SS:FF: hours, minutes, seconds and frames. For example, 00:00:08:12 identifies eight seconds plus twelve frames. The final 12 is not twelve hundredths of a second. Apple documents the same hours, minutes, seconds and frames interpretation in its guide to navigating with timecode.

For an illustrative timeline running at exactly 60 frames per second, twelve frames last 12 ÷ 60 = 0.2 seconds. The position 00:00:08:12 therefore corresponds to 8.2 seconds when the timeline starts at zero. At another frame rate, the same displayed frame field represents a different fraction of a second.

Exact timeline frame rate Illustrative timecode Position from a zero start
24 fps 00:00:08:12 8.500 seconds
25 fps 00:00:08:12 8.480 seconds
30 fps 00:00:08:12 8.400 seconds
60 fps 00:00:08:12 8.200 seconds

These are calculated examples for exact integer frame rates. They show why reading the last pair as a decimal produces the wrong answer. For a rough whole-second reading, read the seconds field; for an exact position, retain the frames and the timeline frame rate.

Restore a useful display on the main Edit timeline

On the Edit page, right-click the timeline’s numeric timecode display. Choose the timecode representation when you want hours, minutes, seconds and frames instead of a total frame count. Blackmagic documents this context menu as the place to select timecode, frames, subframes or audio sample information on page 854 of the Resolve 21.1 Reference Manual.

If you only need larger digits, choose Workspace > Timecode Window, then give the timeline focus. The floating window follows the viewer or timeline that currently has focus and can be resized. It improves readability while retaining timecode, as described on page 32 of the reference manual.

How do you convert a timeline position to elapsed seconds?

First establish where elapsed time begins. A position is an address; elapsed time is the distance from a chosen starting address. If the timeline begins at 01:00:00:00, a playhead position beginning with 01 does not mean an hour of your edit has played.

To check the start, move to the beginning of the timeline and read its timecode. Blackmagic’s Resolve 20 Fairlight guide documents Home for this action, or fn-Left Arrow on Mac keyboards without a Home key. It documents End and fn-Right Arrow for the timeline end. See the navigation instructions in The Fairlight Audio Guide to DaVinci Resolve 20.

For an exact integer frame rate with ordinary non-drop-frame timecode, convert both addresses using seconds = hours × 3600 + minutes × 60 + seconds field + frames ÷ fps. Subtract the start value from the playhead value. This calculation assumes both addresses use the same frame rate and do not cross a timecode wrap.

For example, suppose a synthetic graphics edit runs at exactly 25 fps, begins at 01:00:00:00, and has its playhead at 01:02:08:12. The difference is two minutes, eight seconds and twelve frames: 120 + 8 + 12 ÷ 25 = 128.48 seconds. That is the elapsed position to record in a seconds-based timing note.

If your readout is a total frame count, divide the number of elapsed frames by the exact frame rate. An illustrative count of 462 elapsed frames at exactly 60 fps is 462 ÷ 60 = 7.7 seconds. Establish that the count is measured from your intended start before using it.

Keep fractional frame rates and drop-frame timecode separate

Do not apply the simple timecode-field formula unchanged to 23.976, 29.97 or 59.94 fps material. Timecode numbering and elapsed clock time require additional care at fractional rates. Apple explains that 29.97 fps video uses nominal 30-frame timecode numbering, and that drop-frame timecode skips designated numbers to compensate; it does not remove video frames. See Apple’s timecode technical note.

For those timelines, use an actual elapsed frame count divided by the exact playback rate, with the correct starting frame accounted for. Keep the original timecode alongside the seconds value when communicating an exact edit point. Rounding a fractional frame rate to 30 or 60 can introduce accumulating error.

How do you show seconds while adjusting keyframes?

If the numbers you want to replace are in an animation editor, use its own ruler setting. In the Keyframe Editor or Curve Editor, open the editor’s option menu and select Display Time Ruler in Seconds. Blackmagic defines this as timeline-based HH:MM:SS:FF, while Display Time Ruler in Frames shows frames since the timeline start. These options are documented on pages 1258–1263 of the Resolve 21.1 Reference Manual.

For example, when timing a simple title animation, this setting lets you compare keyframes with the timeline’s timecode addresses. Continue interpreting the final field as frames. Selecting the command does not produce a decimal readout such as 8.200 seconds or establish that the main timeline ruler has changed.

The feature also appears in the DaVinci Resolve 20 New Features Guide. That version boundary matters when following these instructions in an older installation.

How do you change Fusion’s frame-based time display on Mac?

Fusion has a separate time display setting. Its documented choices are frames, SMPTE timecode, and feet and frames. To replace frame counting with timecode, follow the procedure in the Fusion chapter, page 1302, of the Resolve 21.1 Reference Manual:

  1. In Resolve, choose Fusion > Fusion Settings. In standalone Fusion Studio on Mac, choose Fusion Studio > Preferences.
  2. Open the Defaults panel and choose a Timecode option.
  3. Open Frame Format and choose the appropriate frame rate. Enable has fields if the project is interlaced.
  4. Click Save.

Use the appropriate frame rate for the composition when configuring that display. The documented result is SMPTE timecode, which retains a frame field. This is a Fusion setting; it does not establish a seconds-only display for the Edit or Fairlight timeline.

What if you need decimal seconds for audio?

Fairlight’s main timing controls show the playhead’s timecode, range start, range end and range duration. Its ruler displays program timecode. These are useful for locating audio against the edit, but the cited controls do not document a decimal-seconds replacement. See pages 3750–3751 of the Resolve 21.1 Reference Manual.

For a separate audio measurement task, Audacity documents both seconds and seconds + milliseconds formats for its playhead readout. Its current manual also describes independent formats for selection timing and duration. Choose the seconds format for the quantity you need to read, rather than assuming one display setting changes every ruler and counter. See Playhead position and Bottom toolbar.

If your installed Audacity interface uses the older Selection Toolbar, its documented procedure is explicit: click the triangle beside a time box, or right-click a digit, and select seconds + milliseconds. Choose Start and Length of selection when you need a start position and duration. This interface differs from the newer bottom-toolbar layout; follow the Selection Toolbar documentation only when it matches your installation.

In the newer interface, you can also right-click the timeline ruler and choose Minutes & seconds. Audacity documents this as clock-time ruler labeling, with fractional seconds appearing as you zoom in. The numeric readout’s format remains a separate choice. See Minutes & Seconds.

For any separate audio measurement, define the same starting point used in Resolve. If the audio file begins partway through the edit, its local seconds require that timeline offset before they identify the same position.

For everyday Resolve editing, start with timecode and read its seconds field correctly. Convert only when you need a total elapsed value, accounting for the timeline start and frame rate. Use the keyframe or Fusion settings within their documented scope, and choose Audacity’s seconds readouts when the task is specifically audio measurement.

Sources