MiniMax H3 · Native / Safe Windowed Delivery

If you're generating MiniMax H3 video and your shot plan isn't asking for a fancy finishing route, the R42 universal system still needs something to deliver the segments. IAMCCS_MiniMaxH3UniversalNativeWindowedR42 is that something - the plain, safe delivery branch: native resolution, windowed encode, no upscaling tricks. Display name: Native / Safe Windowed Delivery.

This is one of several R42 adapters that each wrap a proven earlier implementation so they can coexist in one graph. The class subclasses the author's IAMCCS_MiniMaxH3PixelRefineR38B, and the R42 layer adds exactly one behavior worth caring about: it verifies the shot plan actually selected a compatible route before it runs. For this node that means the off route (native, no upscale pass) or the h3_pixel_refine route. Choose any other route in the plan - RTX final, fast two-pass, LTX master - and this branch refuses with a clear "incompatible route" error instead of silently doing the wrong thing.

That route guard is what makes the universal graph safe to wire with every branch connected at once. The route controller in the plan (IAMCCS_MiniMaxH3UniversalRouteControlR42) decides which branch ComfyUI's lazy-input system actually requests, so the other branches are never evaluated. This node is the "default" branch - the one that runs when you're not asking for pixel refinement, RTX upscaling, the fast two-pass, or an LTX master. It takes the checkpointed native frames and audio, handles the windowed encode per segment, and chains through your render automatically.

Underneath, "windowed" is doing the memory management work. Long H3 clips are encoded in windows rather than held as one giant image batch, which is what keeps a multi-minute render from eating your RAM at the encode stage. Native resolution means what the native take decoded to - this branch deliberately doesn't try to make it bigger or sharper. If you want a quality pass, that's what the other routes exist for.

Inputs and outputs

The full delivery-sink set: model, video_vae, sampled_latent, conditioning, cine_linx, the checkpointed native_frames and native_audio, resolved_render_id and native_saved_report, current_segment/total_segments, context_trim_frames/join_trim_frames, and queue_next_segment (default true). Outputs: video_path and report.

You can see it reuses the same choreography as the other branches - same render-id strings, same segment counting, same trim bookkeeping - because the universal design point is that you should be able to swap routes without rewiring the graph.

The honest take

Reach for this when you want the framework's bookkeeping (checkpointing, segment auto-queue, AV-join handling, the metadata reports) but you're not chasing extra quality - quick tests, dailies, or final renders that are already good enough at native res. It's the low-drama option in the R42 menu. One reminder: because it inherits from the R38B pixel-refine lineage, its native path expects the R38B-era input contract - if a workflow built against an older IAMCCS version feeds it something else, expect the compatibility shims to do their thing rather than this node changing shape.

Install

Part of IAMCCS-nodes, installed once:

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes

or via ComfyUI Manager (search "IAMCCS"), then restart. You need the H3 stack - current ComfyUI (≥ 3.x) with native MiniMax H3 support, Python ≥ 3.12, PyTorch ≥ 2.8, H3 weights and video/audio VAEs - and you'll want the reference R42 workflow to see the whole graph wired. Remember the H3 licence: US, EU, UK and Korea are excluded from the community terms.