Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > ComfyUI-MiniMax-H3-Guide > MiniMax H3 Target Timing (Legacy)

ComfyUI Node: MiniMax H3 Target Timing (Legacy)

Class Name

MiniMaxH3TargetTiming

Category
MiniMax H3/Prompting
Author
ethanfel (Account age: 3377days)
Extension
ComfyUI-MiniMax-H3-Guide
Latest Updated
2026-08-12
Github Stars
0.16K

How to Install ComfyUI-MiniMax-H3-Guide

Install this extension via the ComfyUI Manager by searching for ComfyUI-MiniMax-H3-Guide
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter ComfyUI-MiniMax-H3-Guide in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

MiniMax H3 Target Timing (Legacy) Description

Manages video timing constraints within MiniMax H3 framework, setting target duration for precise video sequences.

MiniMax H3 Target Timing (Legacy):

The MiniMaxH3TargetTiming node is designed to manage and resolve the timing for video sequences in the MiniMax H3 framework, ensuring that the duration of video content adheres to specific constraints. This node is crucial for setting the target duration of a video, which can be derived from a shot plan or specified manually. It ensures that the video duration is within the acceptable range of 4 to 15 seconds, which is essential for maintaining the integrity of the H3 framework's timing requirements. By resolving the target timing once, it prevents the formation of graph cycles during upstream media preparation, thus streamlining the video production process. This node is particularly beneficial for users who need to create precise video sequences with specific timing requirements, as it provides a structured approach to managing video duration and shot planning.

MiniMax H3 Target Timing (Legacy) Input Parameters:

duration_seconds

This parameter specifies the desired duration of the video in seconds. It is used when no shot plan is provided or when manual timing is preferred. The duration must be a finite value between 4.0 and 15.0 seconds. If the duration is outside this range, the node will raise an error, ensuring that the video conforms to the H3 framework's timing constraints.

shot_plan

The shot_plan parameter allows you to input a predefined sequence of shots that dictate the timing of the video. When a shot plan is connected, it takes precedence over the manual duration setting. The shot plan must ensure that the final shot's end time is at least 4.0 seconds to meet the minimum duration requirement. This parameter is essential for users who want to create complex video sequences with multiple shots.

manual_shot_plan

This parameter is a string that allows you to manually define a sequence of shots if no connected shot plan is available. It provides flexibility for users who prefer to specify shot timings directly. The manual shot plan must also adhere to the 4.0 to 15.0 seconds duration constraint, and it is only used when no connected shots are present.

MiniMax H3 Target Timing (Legacy) Output Parameters:

timing_context

The timing_context output is a dictionary that contains the resolved timing information for the video. It includes details such as the source of the timing (shot plan or manual), the requested duration, the calculated H3 length in frames, and the effective duration in seconds. This output is crucial for downstream processes that require precise timing information, ensuring that the video sequence aligns with the H3 framework's requirements.

h3_length

This output represents the number of frames calculated for the video based on the resolved timing. It is an integer value that reflects the native frame count required to achieve the specified duration. The h3_length is essential for ensuring that the video sequence is correctly aligned with the H3 framework's frame grid, providing consistency across different video processing tasks.

report

The report output is a string that provides a summary of the timing resolution process. It includes information about the timing source, the requested and effective durations, and the native frame count. This output is useful for users who need a quick overview of the timing configuration and any adjustments made during the resolution process.

MiniMax H3 Target Timing (Legacy) Usage Tips:

  • Ensure that the duration_seconds parameter is set within the 4.0 to 15.0 seconds range to avoid errors and ensure compliance with the H3 framework's requirements.
  • When using a shot plan, verify that the final shot's end time meets the minimum duration requirement to prevent errors related to insufficient video length.
  • Utilize the report output to quickly verify the timing configuration and make any necessary adjustments to the shot plan or manual timing settings.

MiniMax H3 Target Timing (Legacy) Common Errors and Solutions:

"The shot plan ends before H3's 4-second minimum. Extend the final shot so its end_time is at least 4.000 seconds."

  • Explanation: This error occurs when the final shot in the shot plan has an end time that is less than 4.0 seconds, which is below the minimum duration requirement.
  • Solution: Adjust the shot plan to ensure that the final shot's end time is at least 4.0 seconds.

"MiniMax H3 target duration must be a finite value from 4 to 15 seconds."

  • Explanation: This error indicates that the specified duration is either not finite or falls outside the acceptable range of 4 to 15 seconds.
  • Solution: Set the duration_seconds parameter to a finite value within the 4.0 to 15.0 seconds range.

"Target Timing contains an unsupported timing source."

  • Explanation: This error occurs when the timing_context contains a source that is not recognized by the node.
  • Solution: Ensure that the timing_context is derived from a valid MiniMax H3 Target Timing node and that the source is either "duration" or "shot_plan".

MiniMax H3 Target Timing (Legacy) Related Nodes

Go back to the extension to check out more related nodes.
ComfyUI-MiniMax-H3-Guide
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.