Nodes/saya-comfy-couple-plus/Saya Resolution Scale Calculator · Existing + Added Ratios
ComfyUI Node

Saya Resolution Scale Calculator · Existing + Added Ratios

The same resolution calculator, under its old name

By alphaziod·Created 3 months ago·Updated about 15 hours ago· 3
Saya Resolution Scale Calculator · Existing + Added Ratios
  • image
  • width_int
  • height_int
  • width_float
  • height_float
resolution_presetLandscape 16:9 · 1344x768
no_scalefalse
scale_from_imagefalse
aspect_preset_when_not_image16:9 - Landscape
swap_aspect_when_not_imagefalse
custom_aspect_width16
custom_aspect_height9
modeWAN/LTX (Div32)
custom_divisor8

Here's a ComfyUI quirk that confuses people, and it's worth one clean paragraph: SayaResolutionScaleCalculator13Ratios and SayaResolutionScaleCalculator are the same node. Look at the pack's source and you'll see both class names point at one implementation - the registry literally maps SayaResolutionScaleCalculator13Ratios to the SayaResolutionScaleCalculator class. The "13Ratios" id is a leftover from an earlier build of the calculator (before it grew the fixed preset ladder), kept registered so that workflows saved under the old node id still load today instead of showing up as a missing node.

Which means every input, output, and behavior description of the main calculator applies here verbatim. Same 29 exact presets in the dropdown (Landscape 16:9 · 1344x768 and friends), same clean AI-friendly dims, same no_scale pass-through toggle, same swap_aspect_when_not_image flip, and the same four outputs - width_int, height_int, width_float, height_float - so the ints feed an Empty Latent and the floats feed float-hungry scaling math. It even carries the identical display name in the node menu: "Saya Resolution Scale Calculator · Existing + Added Ratios." If you add a fresh one from the menu today, you'll get this same node; the 13Ratios distinction only survives in old saved graphs and on this page.

So the practical question isn't "which one do I use," it's "why did an old workflow of mine reference this name." Answer: because it was saved when the calculator's class went by that id, and the author kept the alias in place rather than breaking every graph that used it. That's genuinely good behavior for a work-in-progress pack - you don't have to hunt through old files and re-wire anything when you update. If ComfyUI ever does complain that the node is missing after an update, the standard fix applies: fully restart ComfyUI so the fresh registry is read, and if a node still shows stale sockets, delete it and drop a new one in.

Like every node in this pack, install via ComfyUI Manager (search saya-comfy-couple-plus) or clone into custom_nodes:

cd ComfyUI/custom_nodes
git clone https://github.com/alphaziod/saya-comfy-couple-plus

then restart. Only numpy/Pillow are extra dependencies; no models download.

If you landed here wondering whether the 13-ratio version does something the newer one doesn't: it doesn't anymore. Read the full walkthrough on the main calculator's page for how the presets and toggles behave. This page exists because ComfyUI's node index treats every class id as its own node - the underlying code hasn't been two different things for a while.

CategorySaya/Scaling

Inputs (10)

NameTypeDefaultDescription
resolution_presetCOMBOLandscape 16:9 · 1344x76829 options: Landscape 16:9 · 768x432, Landscape 16:9 · 896x512, Landscape 16:9 · 1024x576, Landscape 16:9 · 1152x648, Landscape 16:9 · 1280x720, Landscape 16:9 · 1344x768, +23
no_scaleBOOLEANfalse
scale_from_imageBOOLEANfalse
aspect_preset_when_not_imageCOMBO16:9 - Landscape14 options: 1:1 - Square, 4:5 - Portrait, 3:4 - Portrait, 7:9 - Portrait, 2:3 - Portrait, 9:16 - Portrait, +8
swap_aspect_when_not_imageBOOLEANfalse
custom_aspect_widthINT161–9999
custom_aspect_heightINT91–9999
modeCOMBOWAN/LTX (Div32)3 options: WAN/LTX (Div32), FLUX/SDXL (Div8), Custom Divisor
custom_divisorINT81–512
imageoptIMAGE

Outputs (4)

NameTypeDescription
width_intINT
height_intINT
width_floatFLOAT
height_floatFLOAT