MiniMax H3 Easy Aspect Ratio

The most honest kind of node: one input, one output, one job

MiniMaxH3EasyAspectRatio is a utility you'll probably never reach for on its own - and then you'll build a two-pass workflow and suddenly it's the piece you were missing. It reads the resolved aspect ratio out of the main node's h3_context and hands it back as a human-readable ResolutionSelector label like 16:9 (Widescreen). That's the whole thing.

What it does

• Input: h3_context, straight from MiniMax H3 Easy.
• Output: aspect_ratio - a label, not a number. The full mapping is 1:1 (Square), 2:3 (Portrait Photo), 3:2 (Photo), 3:4 (Portrait Standard), 4:3 (Standard), 9:16 (Portrait Widescreen), 16:9 (Widescreen) and 21:9 (Ultrawide).

The important design detail is in what it does not do. It synchronizes only the ratio. Megapixels, multiples and exact width/height stay independent downstream. So you can render a 480P 16:9 first pass and a 1024P 16:9 second pass without ever touching the ratio twice - the second pass inherits the shape, sets its own pixel budget, and neither side fights the other.

That's exactly the job it does in the pack's included MiniMax_H3_Easy_Pass2.json: the aspect-ratio node sits between the main Easy node and the second pass's resolution selector, keeping the composition ratio locked while the pass-2 megapixel target floats free. If you've ever manually kept a widescreen ratio consistent across two resolution-changing samplers, you know the silent mismatch this prevents.

Install and use

Install with the rest of the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/nkxx188/ComfyUI-MiniMaxH3-Easy

or search "MiniMax H3 Easy" in ComfyUI Manager, then restart. Wire h3_context in, wire aspect_ratio to whatever resolution selector wants the label, done. There are no settings, no modes, no gotchas in normal use.

When to skip it

If your workflow renders one pass at one resolution, this node is pure noise - the ratio is already baked into the main node's canvas. It earns its place only when something downstream needs to know the ratio independently, which realistically means pass-2 refinement or any workflow that rescales between stages. Also note the output is a label string, not a numeric ratio: it's meant for nodes that accept that preset label, not for math. And if you feed it a context that was built with an unsupported ratio, it throws rather than guessing, which is the right failure mode for a synchronizer.