LTX Upscaler Power

This is the pack's quietest node and also its most self-explanatory: it's a dropdown that outputs a value. One input, one output, both named upscaler_power, choices none, x1.5, and x2. If that sounds trivial, you're right - but it exists to solve a real workflow-hygiene problem once your LTX graph stops being a toy.

Here's the context. LTXResolutions, the pack's main LTX node, has its own upscaler_power dropdown, and it's a special kind of combo: it accepts a direct connection from another node. That means you don't have to set upscale power three times across three resolution nodes in the same graph - you wire all of them to one shared control and change it in one place. That shared control is what LTX Upscaler Power is. It's a value node, like a String or Int constant you can route anywhere.

How it works

It's a straight pass-through with a bit of forgiveness. You pick none, x1.5, or x2, and it emits that as a COMBO on the upscaler_power output. Under the hood the pack normalizes whatever it receives - so if something upstream hands it "1.5" or "2x" instead of the exact label, it still lands on the right choice, and anything unrecognized falls back to none rather than erroring. It'll also run happily through a generic/combo switch first, which is how you'd get one master dropdown controlling a whole scene.

The wiring pattern:

1. Add LTX Upscaler Power to your graph.
2. Set its upscaler_power to what you want.
3. Connect its output to the upscaler_power input on every LTXResolutions node you care about (you can route it through a combo switch in between).

One thing worth knowing: this node only sets the mode - it's the x2 decision, not the actual upscaling. The actual math lives in LTXResolutions, which reads the power, treats your selected preset as the final target, and outputs the smaller base resolution you should generate at before upscaling. So x2 on a Full HD preset returns 960×544, and you upscale 2× to land on 1920×1088. This node is the "why" of that choice made visible; LTXResolutions is the "how".

Installing

Identical to the rest of the pack - ComfyUI Manager (search "WanResolutions" / "Wan/MiniMax/LTX Resolutions"), or:

cd ComfyUI/custom_nodes
git clone https://github.com/boobkake22/ComfyUI-WanResolutions.git

Restart ComfyUI. No dependencies, no models, nothing to download.

Should you bother?

If you run one LTX workflow, honestly, just use the dropdown built into LTXResolutions and skip this node entirely. Where it earns its place is the moment you're running a multi-pass or multi-node LTX setup and you're tired of hunting for three identical dropdowns every time you want to swap between draft speed and final quality. One labeled control beats three buried ones. For a single-purpose pass-through, that's a legitimately good reason to exist.