
In Blender's Movie Clip Editor, a Timecode Index controls how frames are located in footage. It is not simply a smaller proxy. If camera footage seeks to inconsistent moments even when its nominal frame rate matches the scene, inspect the indexing route before repeatedly changing proxy resolution.
Separate decoding workload from frame addressing
The Blender 5.0 Movie Clip sidebar documents proxies as lower-resolution or quality copies and timecode indexing as a response to seeking problems in camera footage. This guide concerns that editor's controls, not an assumed identical Video Sequencer panel.
A hypothetical tracking task needs the same hand position every time the editor seeks to a marked point. A smoother preview is helpful, but smooth playback alone does not establish correct frame correspondence.
Inspect the documented indexing choices
In Footage > Proxy/Timecode, compare the available Timecode Index modes. None seeks from calculated timestamps. Record Run uses timestamps from the movie stream. Record Run No Gaps ignores incomplete or dropped frames and frame-rate changes as described in the manual.
Choose from the actual symptom and intended time relationship. Do not treat No Gaps as recovered missing imagery; ignoring gaps cannot reconstruct an unrecorded action.
Build the relevant index and verify events
Use Build Proxy/Timecode or Clip > Proxy > Rebuild Proxy and Timecode Indices for the documented build operation. Keep source media unchanged while investigating, and record the selected index mode separately from generated proxy sizes.
After building, seek repeatedly to several recognizable source events and compare their positions. Include a later event, because one correct opening frame does not establish correspondence throughout a recording. These are proposed checks, not a performed index rebuild.
Preserve the distinction in the handoff
If the chosen index changes the apparent treatment of gaps, inspect the relationship to sound and any existing tracking before continuing. Record what the reference timeline is meant to represent. An index with convenient sequential frames is not automatically the intended real-time interpretation.
The decoded-frame counting guide examines another aspect of source evidence; its counts do not select Blender's seeking policy. Retain the original and report an unresolved mismatch rather than promising that indexing repairs every damaged file.
Related tasks
- Can ffprobe’s frame rate tell me the actual frame count?
- Why Did Relinking a Missing Video Replace It with the Wrong Take?
Sources and scope
- Blender 5.0 Movie Clip Editor Sidebar: Proxy/Timecode: Proxy versus timecode functions, None/RecordRun/NoGaps semantics, Build/Rebuild routes and caveats.
Based on official Blender documentation read through search-index body results on October 23, 2026. Direct HTTP 200 retrieval and hands-on testing were not established; examples and acceptance checks are proposed guidance.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Mak Cézar / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.