MiniMax H3 Context Loop Plan:
The MiniMaxH3ChainPlan node is designed to parse and validate a frame-exact MiniMax H3 shot plan, which is essential for generating coherent and seamless video sequences. This node is particularly beneficial for AI artists who aim to create complex video projects with precise control over scene transitions, audio continuity, and visual consistency. By leveraging this node, you can ensure that your video projects maintain a high level of quality and coherence, as it computes valid lengths, overlaps, audio windows, seeds, and checkpoint compatibility hashes. The node's primary goal is to facilitate the creation of intricate video sequences by providing a robust framework for managing and executing detailed shot plans.
MiniMax H3 Context Loop Plan Input Parameters:
plan_json_input
This parameter accepts a complete scene-plan JSON, which can be supplied by another node, such as an LLM story director or a reusable STRING source. It allows you to override the visual editor's internal plan_json for the current execution, ensuring that the node uses the most up-to-date and relevant plan. The input must be a non-empty connected value to take effect; otherwise, the internal plan_json remains unchanged. This flexibility allows for dynamic adjustments and refinements to your video project.
chain_policy
The chain_policy parameter connects the MiniMax H3 Generation Profile directly or through an Advanced Policy or Legacy 0.4 Policy Adapter. It combines various elements such as transition, final soundtrack, source-audio reference, generated audio continuity, and automatic audio context into a single connection. This parameter is crucial for defining the generation intent and ensuring that the video project adheres to the desired stylistic and technical guidelines.
run_name
This STRING parameter identifies the render history and its associated output/h3_chains folder. It serves as a unique identifier for your project, allowing for easy organization and retrieval of project assets. The default value is "h3_chain," but it can be customized to suit your project's specific needs.
MiniMax H3 Context Loop Plan Output Parameters:
plan
The plan output is a validated chain plan that can be connected to Loop Start and, for recovery, Manifest Load. It represents the core structure of your video project, ensuring that all elements are correctly aligned and executed according to the specified plan.
summary
This output provides a human-readable summary of the scene count, delivered duration, and compatibility. It offers a quick overview of the project's scope and ensures that all components are compatible and aligned with the intended output.
clip_count
The clip_count output indicates the number of scenes in the plan. This information is crucial for understanding the project's complexity and ensuring that all scenes are accounted for in the final output.
width
The width output represents the validated generation width, which should be connected to the stock H3 conditioning node. It ensures that the video output adheres to the specified dimensions, maintaining visual consistency across all scenes.
height
Similar to the width output, the height output provides the validated generation height, which should also be connected to the stock H3 conditioning node. It ensures that the video output maintains the desired aspect ratio and visual quality.
video_blend_frames
This output specifies the legacy plan-wide default blend length. It cannot represent a per-scene override because the plan has no active scene. Instead, it should be connected to the Current Shot state to Loop Trim state, ensuring smooth transitions between scenes.
MiniMax H3 Context Loop Plan Usage Tips:
- Ensure that your
plan_json_inputis correctly formatted and connected to take advantage of dynamic scene planning and execution. - Utilize the
chain_policyparameter to define clear generation intents and maintain stylistic consistency across your video project. - Customize the
run_nameto keep your project assets organized and easily accessible.
MiniMax H3 Context Loop Plan Common Errors and Solutions:
H3 Chain Plan JSON is invalid
- Explanation: This error occurs when the provided JSON for the plan is not correctly formatted or contains syntax errors.
- Solution: Double-check the JSON structure for any syntax errors or missing elements. Ensure that it is a valid JSON object or a list of shots.
H3 Chain Plan requires a non-empty 'shots' list
- Explanation: The plan must include a list of shots to be valid. An empty or missing 'shots' list will trigger this error.
- Solution: Ensure that your plan JSON includes a populated 'shots' list with the necessary scene details.
H3 Chain Plan supports at most MAX_SHOTS shots
- Explanation: The plan exceeds the maximum number of supported shots, which can lead to performance issues or execution errors.
- Solution: Reduce the number of shots in your plan to stay within the supported limit, ensuring smooth execution and performance.