MiniMax H3 Attach Motion to Shot (Plan v2):
The MiniMaxH3PlanV2ShotMotionReference node is designed to enhance the animation workflow by integrating motion references into a shot plan. This node allows you to attach specific motion sequences to a shot, ensuring that the motion is accurately represented and synchronized with the visual elements of the shot. By leveraging this node, you can create more dynamic and realistic animations, as it facilitates the precise alignment of motion with the intended visual narrative. The node is particularly beneficial for projects that require detailed motion planning and execution, as it provides a structured approach to incorporating motion references into the animation timeline.
MiniMax H3 Attach Motion to Shot (Plan v2) Input Parameters:
h3_plan
This parameter represents the validated plan that includes the timeline and phases for the animation project. It is crucial for ensuring that the motion reference is integrated into the correct phase of the project, maintaining the continuity and coherence of the animation sequence.
shot_handle
The shot_handle is a reference to the specific shot within the plan that will receive the motion. It ensures that the motion is applied to the correct shot, allowing for precise control over which part of the animation the motion affects.
video_frames
This parameter consists of a batch of image frames, typically ranging from 2 to 15 seconds in duration. These frames provide the visual content that will be synchronized with the motion reference, ensuring that the motion is accurately depicted within the shot.
target_subject
The target_subject is a string that identifies the subject performing the motion within the shot. It is essential for ensuring that the motion is applied to the correct visual element, allowing for accurate representation of the intended action.
reference_name
This parameter is a string that names the motion reference being attached. It helps in organizing and identifying different motion references within the project, facilitating easier management and retrieval of motion data.
description
The description provides a textual explanation of the motion being referenced. It serves as a documentation tool, offering insights into the nature and purpose of the motion, which can be useful for collaborators and future reference.
source_fps
This parameter specifies the frames per second (FPS) of the source video from which the motion reference is derived. It is crucial for ensuring that the motion is accurately synchronized with the visual content, maintaining the intended timing and pacing of the animation.
MiniMax H3 Attach Motion to Shot (Plan v2) Output Parameters:
shot_handle
The shot_handle is returned to confirm the successful attachment of the motion reference to the specified shot. It serves as a verification tool, ensuring that the motion has been correctly integrated into the shot plan.
video
This output parameter provides the processed video frames that now include the motion reference. It allows you to preview and verify the integration of motion within the shot, ensuring that the animation meets the desired visual and motion criteria.
preview
The preview offers a visual representation of the shot with the attached motion reference. It is an essential tool for reviewing the animation, allowing you to make adjustments and ensure that the motion aligns with the creative vision.
MiniMax H3 Attach Motion to Shot (Plan v2) Usage Tips:
- Ensure that the
target_subjectis correctly defined and matches an upstream subject to avoid errors during motion attachment. - Use the
descriptionparameter to document the motion reference clearly, aiding in project management and future revisions.
MiniMax H3 Attach Motion to Shot (Plan v2) Common Errors and Solutions:
Motion target '<target_subject>' is not an upstream Subject.
- Explanation: This error occurs when the specified
target_subjectdoes not match any defined subjects in the upstream plan. - Solution: Verify that the
target_subjectis correctly spelled and matches an existing subject in the project plan.
Invalid video frame batch size.
- Explanation: This error indicates that the
video_framesparameter does not contain the required number of frames (2–15 seconds). - Solution: Ensure that the
video_framesbatch is within the specified duration range to meet the node's requirements.
