⏱️ VRGDG_TimecodeFromIndex

Every multi-scene video workflow eventually hits the same problem: you're working in frame indices - frame 0 through frame 2,400 - but your subtitles, your audio sync, and your edit decisions all live in seconds. VRGDG_TimecodeFromIndex is the two-input bridge that converts one to the other.

Its whole job is answering "what time is this frame?" and handing you a human-readable start_time string you can feed into anything that cares about timestamps. In VRGameDevGirl's music video pipeline, where chunks of frames get rendered per scene and then trimmed to an audio track, that conversion happens constantly - this node exists so you don't hand-roll the division on every scene.

How it works

One input, one output:

• index (integer, default 0) - the frame index you want the time for. Wire this to whatever frame counter your workflow is on, or set it by hand.
• start_time (string output) - the timecode for that frame, ready to paste or wire into a node that consumes timestamps.

That's the entire surface. No FPS input, no config to get wrong - the node does the conversion and hands you a formatted timecode string. It's the kind of utility that looks trivial on paper and saves you a dozen tiny mental arithmetic mistakes across a long workflow.

It pairs naturally with the pack's trimming nodes (VRGDG_TrimFinalClip, VRGDG_TrimImageBatch) and the SRT-synced variants, which all work in frames-per-scene terms. When you need to tell a consumer node "this scene starts at 12.5 seconds," you feed it this node's output instead of computing it in your head.

Installing it

Ships with the VRGameDevGirl Video Enhancement Nodes pack. ComfyUI Manager → search vrgamedev → install, then restart ComfyUI, or:

cd ComfyUI/custom_nodes
git clone https://github.com/vrgamegirl19/comfyui-vrgamedevgirl

No models, no pip packages needed for this one.

Common issues

You expected a start_time number and got a string. That's by design - the output is a formatted timecode text string, not a float. If a node downstream wants a numeric time, convert it there.

Not sure if it's 0-based or 1-based. The default index is 0, which is the ComfyUI convention for frame tensors. If your timestamps are off by exactly one frame's duration, that's the first thing to check.

It's a one-line utility wearing a node costume. When you're deep in a scene-by-scene video build, those are often the nodes you appreciate most.