Stable Manifold Anchor Resize

Stable Manifold Anchor Resize (class StableManifoldAnchorResize) is a backward-compatibility alias. In the pack's nodes.py, it maps to the exact same node class as SMC Affine Anchor Resize - one entry point, two names. If you've loaded a workflow that references StableManifoldAnchorResize, this is what you're actually getting, and you don't need to re-lay anything.

Why does the duplicate exist? The pack's history: the earlier "Stable Manifold" node names shipped first, then the pack was reorganized under the SMC prefix and the old class names were kept as aliases so saved workflows wouldn't break. The pack author's own comment in the source calls them "backward-compat aliases from the earlier pack." It's a small thing, but ComfyUI's node registry treats each class name as its own entry - so in your node search you'll see both names and might reasonably assume they're different nodes. They aren't.

Same inputs, same outputs

Identical to SMC Affine Anchor Resize:

• image, target_megapixels (0.01–32, default 1.0), multiple_of (1–256, default 16), upscale_mode (bilinear/bicubic).
• Outputs: anchor_image, width, height, megapixels.

Use it to build the low-res anchor for the affine drift-estimation path - feed the output into SMC Affine Estimate Drift or SMC Affine Compand. Full behavior is covered in that node's article; nothing differs except the class name.

Install & gotchas

Same pack, trivial install:

cd ComfyUI/custom_nodes
git clone https://github.com/xmarre/ComfyUI-StableManifoldCompander

or ComfyUI Manager (search "Stable Manifold Compander"). No extra dependencies. The practical question people actually hit: "which one do I use?" Answer - whichever name is already in your workflow. If you're building fresh, prefer the SMC-prefixed name since that's the current convention and the one new examples will use. If a shared workflow loads StableManifoldAnchorResize, leave it alone; it works and will keep working. The pack is tiny and early, so there's no guarantee every alias survives a future refactor, but keeping old names alive is exactly what a compatibility alias is for.