MiniMax H3 Hybrid Pair Inspector / 混合模型配对检查 (Advanced)

MiniMax H3 is a 33B joint audio-video model, and the Hybrid line in this pack is how you get FL2VA-style first/last-frame control and Ref2VA reference behavior without paying for a full second model in VRAM. The price of that trick is that the two checkpoints you're pairing - a pruned FL2VA quality base and a pruned Ref2VA reference overlay - have to be exactly the versions the pack expects. The whole difference between "hybrid works" and "hybrid renders garbage and you can't say why" is usually a mismatched file. This node is the gatekeeper that checks before anything is built.

It's the strictest node in the Hybrid family for a reason: it won't let an artifact exist until it's verified the exact pair of checkpoints it's standing on. If you're new to this pack, treat the Pair Inspector as mandatory upstream of the Hybrid Model Loader, even though the loader technically doesn't require it.

How it works

You feed it two checkpoints: quality_base (the exact validated FL2VA-pruned ConvRot checkpoint) and reference_overlay (the exact validated Ref2VA-pruned ConvRot checkpoint). The node then verifies them - by default with a full SHA-256 hash - and only then emits a hybrid_plan that downstream nodes can build from.

The verification input has a sharp edge worth knowing: full_sha256 is the buildable plan, and header_only_exp is a diagnostic mode that always blocks artifact construction. If you switch to header-only to "save time," you get a readout but no artifact. That's deliberate - a truncated check is good enough to look, not good enough to build on.

The profile input (default blocks_25_49_video_audio_exp) picks which neutral experimental recipe the plan encodes. The tooltip is explicit and honest: none of these profiles is a proven quality winner, and the static modality rows affect target streams too. In other words, changing the profile changes the experiment, not the answer key.

The inputs that matter

• quality_base and reference_overlay - the two COMBO dropdowns are everything. Wrong file in either slot and the whole pipeline is quietly wrong.
• verification - full_sha256 default; leave it there.
• profile - leave at default unless you're deliberately A/B-testing recipes.
• positive (optional) - connect an existing H3 Conditioning and auto_match_reference_modalities_exp uses its real reference kinds to pick the minimal video/audio modality recipe. Only matters if you're on the auto-matching path.

Outputs

hybrid_plan (the H3_T8_HYBRID_PLAN you feed the loader), compatible (BOOLEAN), plus report and report_json strings. When compatible is false, read the report - it tells you which checkpoint failed verification or which profile constraint broke, not just that something is wrong.

Installing it

Part of the pack, so: ComfyUI Manager → "MiniMax H3 Audio T8", or:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8

restart. No extra pip deps, no auto-downloads - the two pruned checkpoints have to be in models/diffusion_models yourself.

Common issues

compatible=false on a pair you downloaded from the pack's own links. Re-download. The SHA-256 check is there because files get truncated or a mirror serves a different variant; the node is refusing to build an artifact it can't vouch for, and you don't actually want it to.

"Why is header_only not producing a plan?" Because it's diagnostic by design. Use full_sha256 when you want something you can actually sample with. And don't pad a SHA check off as optional - the pack's own notes treat a header-only pass as "probably fine to look at," never "safe to ship."