MiniMax H3 Motion Overload Analyze / 动作过载分析 (Advanced)

Fast motion is where H3 starts lying to you - warping limbs, smeared faces, frames that look like the model gave up mid-sentence. The pack's Motion Recovery system exists to catch that and fix it, and MiniMaxH3MotionOverloadAnalyzeT8Advanced is the first step: it looks at your pass-1 result and decides whether the motion is overloaded enough to be worth repairing.

Its defining trait is that it's read-only. It analyses the H3 latent and the decoded frames, but it never patches your MODEL and never touches sampling. That's a deliberate design choice - the author separates "measure the problem" from "spend compute fixing it," and it means you can run this node freely without worrying it's silently mutating your pipeline. On calm clips it abstains: should_repair comes back false, and the downstream Auto Gate bypasses the entire second-pass graph, which is the whole point of the chain - don't spend eight extra joint AV forwards on a clip that doesn't need them.

Inputs that matter

• av_latent and frames - the pass-1 latent and its decoded frames. Both, because the analysis fuses latent motion with pixel-level residual.
• mode - report_only (never expand, just tell you), auto_conservative_exp (default; expands only when all abstain gates pass), or manual_ranges (use manual_ranges exactly).
• manual_ranges - used only in manual_ranges mode; examples are 36-60:4 or 1.5s-2.4s:3 (frame/seconds ranges with an expansion count).
• overload_threshold (3.5), minimum_profile_contrast (2), minimum_residual_motion (0.01) - the sensitivity knobs. The residual gate is the important one: it runs a small global-translation search and requires real pixel change, so a quantile-only rule can't flag a static shot.
• max_hold (4), bridge_tokens (2), minimum_hot_frames (5) - how hot ranges get merged and how small a blip counts.
• fps - fixed at 24 for H3.

Outputs

motion_plan (type H3_T8_MOTION_RECOVERY_PLAN) - the signed plan that every later node in the chain consumes. should_repair - the boolean that drives the Auto Gate. heat_preview - a visual of where the motion overload is. expanded_frames - how many frames the analysis thinks need expanding. Plus report_json. This node is marked as an output node, so it can sit at the end of a diagnostic-only graph.

Install and where it fits

Pack install once: ComfyUI Manager → search MiniMax H3 Audio T8, or git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8 into ComfyUI/custom_nodes/, restart. No pip extras, no model downloads.

The full chain is: Analyze → (gate) → Retiming Prepare → Recovery Composer → Recover AV → Auto Gate. Run this node in report_only first on a clip you know is bad, read the heat preview and report_json, then let it auto-expand. The one honest caveat: the pack's own testing shows a true calm clip passes the abstain gate with hashes identical to pass-1, but motion analysis is a proxy, not proof - a clip can pass analysis and still have a subtle seam. Treat should_repair=false as "no obvious overload," not "certified perfect."