ComfyUI Node: MiniMax H3 Plan Studio (Experimental)

MiniMax H3 Plan Studio (Experimental):

The MiniMaxH3ChainPlanStudio is an experimental node designed to facilitate the creation and management of complex scene plans within the MiniMax H3 framework. It serves as a central hub for constructing, validating, and executing scene plans, allowing you to seamlessly integrate various elements such as timing, source timelines, and references into a cohesive workflow. This node is particularly beneficial for AI artists looking to streamline their creative process by providing a structured environment to manage scene metadata and ensure compatibility across different components. By leveraging the capabilities of the MiniMaxH3ChainPlanStudio, you can efficiently organize and execute your artistic vision, ensuring that all elements are aligned and optimized for the desired output.

MiniMax H3 Plan Studio (Experimental) 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. The input is optional but, when provided, it overrides the internal plan_json of the visual editor for the current execution. This allows for flexibility in plan management, enabling you to use external sources for scene planning. The JSON input undergoes the same normalization and validation processes as the internal plan, ensuring consistency and accuracy. If left empty or disconnected, the internal plan_json remains unchanged.

chain_policy

The chain_policy parameter is used to connect the MiniMax H3 Generation Profile directly or pass it through an Advanced Policy or the Legacy 0.4 Policy Adapter. This parameter plays a crucial role in defining the transition, final soundtrack, source-audio reference, generated audio continuity, and automatic audio context within a single connection. By configuring this parameter, you can control the audio and transition elements of your scene plan, ensuring that they align with your creative objectives.

MiniMax H3 Plan Studio (Experimental) Output Parameters:

plan

The plan output provides a validated chain plan that can be connected to other nodes such as Loop Start or Manifest Load for recovery. This output is essential for ensuring that your scene plan is correctly structured and ready for execution within the MiniMax H3 framework.

summary

This output offers a human-readable summary of the scene count, delivered duration, and compatibility. It provides a quick overview of the plan's key metrics, allowing you to assess its scope and alignment with your project goals.

clip_count

The clip_count output indicates the number of scenes included in the plan. This information is useful for understanding the complexity and scale of your project, helping you manage resources and timelines effectively.

width

The width output specifies the validated generation width, which should be connected to the stock H3 conditioning node. This ensures that the visual dimensions of your scenes are consistent and optimized for the intended output.

height

Similar to the width output, the height output provides the validated generation height. Connecting this to the stock H3 conditioning node ensures that your scenes maintain the correct aspect ratio and visual quality.

video_blend_frames

This output represents the legacy plan-wide default blend length. It is important to note that this value cannot represent a per-scene override, as the plan does not have an active scene. Instead, you should connect the Current Shot state to the Loop Trim state for more precise control over blending.

MiniMax H3 Plan Studio (Experimental) Usage Tips:

• Utilize the plan_json_input to import scene plans from external sources, allowing for greater flexibility and integration with other tools or nodes.
• Configure the chain_policy to ensure that audio and transition elements are seamlessly integrated into your scene plan, enhancing the overall coherence and quality of your project.
• Regularly review the summary output to assess the scope and compatibility of your scene plan, making adjustments as needed to align with your creative objectives.

MiniMax H3 Plan Studio (Experimental) Common Errors and Solutions:

invalid_plan

• Explanation: This error occurs when the connected H3 Chain Plan is not validated or the saved JSON is malformed.
• Solution: Rebuild the Plan in Plan Studio to ensure that the JSON is correctly formatted and validated.

invalid_scene_selection

• Explanation: This error indicates an issue with the start clip or scene range selection within the current Plan.
• Solution: Choose a valid start clip and scene range, or clear the scene_range to validate the complete Plan.

invalid_source_input

• Explanation: This error arises when there is an issue with the connected Source Timeline or legacy source_audio input.
• Solution: Ensure that only one source route is connected, and relink or replace any malformed source media in the Project Asset Manager.

invalid_scene_metadata

• Explanation: This error suggests that the scene metadata was edited outside of Plan Studio, leading to inconsistencies.
• Solution: Open the reported scene in Plan Studio and correct its settings, or rebuild the Plan if necessary.

invalid_reference_input

• Explanation: This error occurs when there is an issue with the active reference registry, such as malformed tags or anchors.
• Solution: Correct or reconnect the reference registry, removing any malformed tags or anchors and adding them again through the Prompt Editor.