ComfyUI Node: MiniMax H3 Plan (Modern)

MiniMax H3 Plan (Modern):

The MiniMaxH3ChainPlanModern node is designed to facilitate modern and organized production planning within the MiniMax H3 framework. It serves as an advanced tool for managing and executing complex scene-column editing tasks while maintaining the integrity of the established Plan output contract. This node is particularly beneficial for users who require a streamlined approach to continuity and audio intent, as these elements are now exclusively managed through the Generation Profile. By preserving the familiar scene-column editor, MiniMaxH3ChainPlanModern ensures that users can continue to work within a known environment while benefiting from enhanced capabilities. This node is ideal for those looking to modernize their workflows without losing access to traditional methods, as the original Plan remains available for legacy workflows.

MiniMax H3 Plan (Modern) Input Parameters:

plan_json

The plan_json parameter is a serialized backing document for the visual scene-column editor. It is used for importing, exporting, or advanced editing of the scene plan. This parameter allows you to define the structure and content of your visual scenes in a JSON format, which can be particularly useful for complex projects that require precise control over scene elements. The default value is a sample JSON, and it supports multiline input. It is important to use raw JSON for this parameter to ensure compatibility with the visual editor.

chain_policy

The chain_policy parameter specifies the required modern generation intent. It connects the MiniMax H3 Generation Profile, optionally through an Advanced Policy Override. This parameter is crucial for defining the continuity and audio behavior of the Plan node, although these aspects are not duplicated within the node itself. The chain_policy ensures that your project adheres to the desired generation profile, which can include transitions, final soundtracks, source-audio references, and generated audio continuity. This parameter does not have a default value and must be set according to the specific needs of your project.

run_name

The run_name parameter identifies the render history and its associated output/h3_chains folder. It serves as a unique identifier for the current execution of the node, allowing you to track and manage different runs effectively. The default value for this parameter is "h3_chain," but it can be customized to suit your project's naming conventions. This parameter is essential for organizing and synchronizing project assets, ensuring that each run is properly documented and accessible for future reference.

MiniMax H3 Plan (Modern) Output Parameters:

The context does not provide specific output parameters for the MiniMaxH3ChainPlanModern node. However, typically, such nodes would output a processed plan or a set of execution results based on the input parameters and the node's internal logic. These outputs would be used to further refine or execute the visual scenes defined in the plan_json.

MiniMax H3 Plan (Modern) Usage Tips:

• Ensure that your plan_json is correctly formatted and validated before execution to avoid errors during processing.
• Utilize the chain_policy parameter to align your project with the desired generation profile, especially if your project involves complex audio and continuity requirements.
• Customize the run_name to keep track of different project iterations and maintain an organized workflow.

MiniMax H3 Plan (Modern) Common Errors and Solutions:

H3 chain plan changed during recursive execution.

• Explanation: This error occurs when there is a mismatch between the base_plan_hash of the prepared plan and the plan_hash of the current plan during recursive execution.
• Solution: Ensure that the plan has not been altered during execution. Verify that all input parameters are consistent and that no external changes have been made to the plan during processing.