MiniMax H3 ClipProj Compatibility Audit / 小编码器投影审计 (Advanced/T8)

MiniMax H3's default CLIP path is a 32B Qwen3-VL, which is a big chunk of VRAM just to encode a prompt. A popular memory diet is swapping in a smaller encoder via an external projection - the ComfyUI-ClipProj ecosystem lets you use a 4B or 8B Qwen3-VL with a learned projection matrix instead. It's a great idea and a great way to spend an afternoon debugging dimension mismatches. MiniMaxH3ClipProjCompatibilityAuditT8Advanced is the node that checks whether your ClipProj setup will actually work - without loading the encoder or the projection matrix at all.

That last part is the whole point. The audit reads the projection file's header (dimensions, declaration, load mode), checks the separately installed ClipProj plugin's version, and compares it against what your connected CLIP and reference usage require. It never loads tensors, never runs the encoder, never touches your 32B default path. It's a dry-run compatibility report you run before committing the VRAM.

What it checks

• plugin_version - whether your installed ComfyUI-ClipProj is new enough (the pack validates against 0.1.13+).
• projection_input_dim / projection_output_dim - the matrix's dimensions from its header, matched against what the 4B/8B encoder and H3 expect.
• Qwen3-VL declaration - the encoder family/architecture/quantization you claim to be using, checked for consistency.
• load_mode (stock_pageable default) - how the projection would load.
• reference boundary - has_reference_images / has_reference_videos flags: ClipProj's visual-reference path is a separate contract, so a setup that works for plain T2VA may not cover Ref2VA.

Inputs you set: clip (passed through unchanged), encoder_family (auto), projection_path (absolute path or a filename under models/clip_projections), and the two has_reference_* booleans. Outputs include compatible (BOOLEAN), decision (STRING), and report_json. The clip output passes through byte-for-byte, so the node can sit in the CLIP path without altering anything while it audits.

Why this exists

The README documents real runs where a fixed 8B ClipProj bridge passed strict decoding but left only ~62MiB of headroom - technically done, terrifyingly tight. This audit is the pack's answer to "is my projector even compatible, before I find out at 3am via an OOM?" It also refuses to be a substitute for a real test: reading a header tells you compatibility, not whether 4B/8B quality equals 32B (the pack explicitly says it doesn't establish that).

Install

The pack install is standard, but this node has an external prerequisite - it audits ComfyUI-ClipProj, which you must install separately:

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

Restart ComfyUI, then install ComfyUI-ClipProj 0.1.13+ via Manager if you haven't. The node itself needs no extra pip packages and no model downloads - it reads headers, not weights.