ComfyUI Node: MiniMax H3 Shot (Plan v2)

MiniMax H3 Shot (Plan v2):

The MiniMaxH3PlanV2Shot node is designed to facilitate the creation and management of complex shot plans within the MiniMax H3 framework. This node is particularly beneficial for users who need to organize multiple shots in a coherent sequence, ensuring that each shot is properly timed and aligned with the overall project duration. By leveraging this node, you can automate the process of validating shot sequences, managing transitions, and ensuring that the timing of each shot is contiguous and logical. The node is capable of overriding manual shot fields with its calculated durations, providing a streamlined workflow for video production and animation projects. It is especially useful when working with chained references, as it can integrate seamlessly with other nodes to maintain a consistent timing context across different shots.

MiniMax H3 Shot (Plan v2) Input Parameters:

ot_plan

The ot_plan parameter is recommended for use with multiple shots, where it connects the final MiniMax H3 Shot node. It writes real [Shot N] markers, validates contiguous float ranges, and uses the last end_time as the target duration, overriding the manual shot field. This parameter ensures that the shot sequence is coherent and properly timed, especially when a timing_context is connected, as it takes priority over manual settings.

timing_context

The timing_context parameter is recommended for use with chained references, where it connects to the MiniMax H3 Target Timing.timing_context. It overrides duration_seconds and carries any connected Shot plan, allowing for a seamless integration of timing across different shots. This parameter ensures that the upstream h3_length can safely feed video visual references and native H3 without creating a graph cycle, maintaining a consistent timing context throughout the project.

MiniMax H3 Shot (Plan v2) Output Parameters:

context

The context output provides a detailed timing context for the shot plan, including the number of shots in the connected chain and the source of the timing information. It offers insights into the requested duration, native duration, and effective duration, helping you understand how the shot plan aligns with the overall project timeline.

h3_length

The h3_length output indicates the native duration of the shot plan in frames, calculated at the H3's native frame rate. This output is crucial for ensuring that the shot plan fits within the desired project duration and helps in adjusting the timing of individual shots to achieve the desired effect.

report

The report output provides a comprehensive summary of the timing source, requested duration, and effective duration of the shot plan. It serves as a valuable tool for reviewing the shot plan's alignment with the project goals and making necessary adjustments to optimize the timing and sequence of shots.

MiniMax H3 Shot (Plan v2) Usage Tips:

• Connect the ot_plan parameter to the final MiniMax H3 Shot node to automate the validation and timing of multiple shots, ensuring a coherent sequence.
• Use the timing_context parameter to integrate timing across different shots, maintaining a consistent context and avoiding graph cycles.

MiniMax H3 Shot (Plan v2) Common Errors and Solutions:

ValueError: shot_handle must come from a Plan v2 Shot node.

• Explanation: This error occurs when the shot_handle is not derived from a valid Plan v2 Shot node.
• Solution: Ensure that the shot_handle is correctly connected to a Plan v2 Shot node and that it contains valid shot identity data.

ValueError: shot_handle contains invalid Shot identity data.

• Explanation: This error indicates that the shot_handle does not have the correct shot number or cut timestamp.
• Solution: Verify that the shot_handle includes accurate shot number and cut timestamp information, and that it matches the connected h3_plan timeline.

ValueError: H3 Image Reference needs exactly one IMAGE in [1, height, width, channels] form.

• Explanation: This error arises when the image reference does not conform to the expected shape.
• Solution: Ensure that the image reference is in the correct format, with exactly one image in the [1, height, width, channels] form.