For ComfyUI’s MiniMax H3 MiniMaxH3AddGuide, convert a target time in seconds with round(seconds × 24), then check that the guide’s anchor and length fit within the generated video. A negative frame_idx counts backward from the end; it does not mean a time before the clip. Make the boundary check for every guide, especially when changing the requested duration or using a multi-frame guide.
Convert seconds into frame indices
The H3 multiframe template uses 24 frames per second for frame_idx and calculates the index by rounding seconds multiplied by 24. This gives a practical coordinate conversion, not a way to alter the clip’s duration. For example, a target at 1.5 seconds maps to frame 36. A fractional result can round to the nearest integer, so record the resulting frame index rather than assuming the node accepts seconds.
In the workflow, find the Frame Index and Math Expression parts of a guide block and verify the value passed into MiniMaxH3AddGuide. If you manually set frame_idx, apply the same conversion yourself. Do not convert using the source clip’s nominal frame rate: the documented H3 guide coordinate is 24 fps.
Check the guide’s occupied range
The anchor alone does not establish whether the guide fits. The H3 documentation requires the frame index plus guide length to remain inside the generated duration. For a nonnegative anchor, use this arithmetic planning screen, with N as the output frame count:
start = frame_idxend = start + guide_length- The planned interval is
[start, end); compare it with[0, N).
For example, frame 60 with a 22-frame guide gives [60, 82), covering labels 60 through 81 under zero-based counting. This is a consistent half-open-interval calculation, not a guarantee of MiniMaxH3AddGuide acceptance: the cited documentation says the index plus guide length must stay inside the generated duration but does not specify all custom-length endpoint semantics. Treat a calculated out-of-range interval as a planning warning to investigate, and confirm the node’s behavior in the current workflow before deciding acceptance, especially at the boundary. Read the actual guide length and output frame count from the workflow; do not infer them from rounded display duration.
Negative frame_idx values count from the end of the video. The cited H3 guide does not specify how a negative anchor combines with a multi-frame guide length to determine its occupied interval, so verify that placement and length behavior in the current MiniMaxH3AddGuide workflow before assessing its range.
Use an ordered boundary check
- Read the output’s total frame count from the current workflow. For native H3 duration settings, confirm the configured
17k+5frame grid and use the resultingN; otherwise obtain the configured or generated frame count first. - Convert each requested anchor time with
round(seconds × 24)and write the resultingframe_idxbeside the guide. - Record each guide’s actual frame length. A still has a different length from a multi-frame batch; use the guide input’s frame count, not the source file’s duration label alone.
- For nonnegative anchors, calculate the planned half-open interval using one frame-count convention across the worksheet, and flag intervals outside
[0, N)for correction or workflow investigation. - Chain guides whose ranges have been checked into the H3 workflow. Recalculate the frame count and ranges whenever output duration or guide media changes.
Example worksheet: hypothetical 124-frame output
This is a hypothetical arithmetic worksheet, not a generated or inspected workflow. Assume N = 124 frames, consistent with the documented 17k+5 grid at k = 7; this does not assert that any particular workflow generates 124 frames. Guide lengths are frame counts, and the table uses the half-open planning interval [start, start + length). Its end is exclusive, so an end equal to N reaches the boundary without including frame N.
| Target time | Rounded index | Guide length | Planned exclusive end | Arithmetic screen against [0, 124) |
|---|---|---|---|---|
| 1.5 s | 36 | 22 | 58 | Inside: [36, 58) |
| 3.0 s | 72 | 22 | 94 | Inside: [72, 94) |
| 5.0 s | 120 | 5 | 125 | Outside: [120, 125); endpoint exceeds N |
| 4.0 s | 96 | 28 | 124 | Ends at N; interval is [96, 124) |
For this arithmetic convention, the 124-frame output has labels 0 through 123. The third row exceeds the output range, while the fourth ends exactly at the exclusive boundary. These calculations screen nonnegative anchors; confirm exact-boundary behavior in the current workflow before treating it as node acceptance.
When the check fails
If the planning interval extends beyond the output, test an earlier anchor, a shorter guide when supported by the input and workflow, or a longer generated duration, then recalculate. These are author-recommended adjustments, not documented guarantees about composition or motion. For a negative anchor, first verify its placement and multi-frame behavior in the current workflow; do not use it to bypass an unresolved positive-anchor range warning.
MiniMaxH3AddGuide is conditioning: the native workflow starts sampling from an empty latent. The documentation distinguishes it from video-to-video editing, and says denoise does not scale guide strength like V2V. A guide can anchor a composition at a frame; that is not a promise that every intervening frame will reproduce an input clip. For multi-frame guide inputs, the documented crop behavior also has a 17k+5 length grid, and inputs under five frames use only the first image. Those input rules are separate from the anchor-versus-output boundary check.
Common questions
Can I use the source video’s frame rate in the conversion?
Not for this template’s frame_idx conversion. The documented rule is round(seconds × 24). Reference-video frame-rate handling is a separate workflow detail; it does not change this guide-coordinate rule.
Why does the worksheet use a half-open interval?
It makes the frame-count arithmetic explicit: [start, end) includes end - start frame labels, and an end equal to N reaches but does not include the boundary. The rectangle-style right boundary x + width = W is likewise a valid half-open geometric example; pixel W - 1 is the last included coordinate. These are counting conventions, not claims about every custom node’s implementation. An anchor at N is outside the ordinary zero-based labels of an N-frame output.
How do I determine `N` before checking a guide?
Use the configured H3 duration and its documented 17k+5 frame grid, or read the actual output frame count from the workflow. Do not mark the check as passed while N is unknown.
Sources and next step
- ComfyUI MiniMax H3 Multiframe Reference Workflow
- ComfyUI MiniMax H3 Text-to-Video, Image-to-Video, and Reference-to-Video Workflows
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.