📐 NL Resolution

Somewhere in every video workflow there's a width and a height, and it's never in just one place. There's the EmptyLatentImage, the VAE encode, the resize, maybe the aspect-ratio node - and if the shot changes, you get to go update all of them and hope you didn't miss one. NL Resolution is the NOLABEL/Workflow answer: set the resolution once in the top-bar NL Workflow panel, and this read-only node hands it back to the graph as two clean INTs - width and height.

It's the sibling of the pack's NL Frame Range and the rest of the Workflow family. The NL Workflow panel is workflow-level UI state (saved to ComfyUI/user/default/nl_workflow.json), not a graph node - you fill in your shot context there, and these helpers read the cached values so everything downstream stays in sync. Change the width in the panel, every node fed by NL Resolution follows.

What you get

• width - INT
• height - INT

No inputs, nothing to configure. Wire them into your EmptyLatentImage, into a latent scale or resize, into anything that takes dimensions. The win isn't that it saves you two numbers - it's that the resolution lives next to the rest of the shot metadata instead of buried inside a node, which makes the whole graph easier to read and to hand to someone else.

Install

Same pack, same dance. ComfyUI Manager → search "ComfyUI-NL_Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/NOLABEL-VFX/ComfyUI-NL_Nodes
# restart ComfyUI

No extra dependencies - it's a plain cached-value reader. The "NL Workflow" button shows up in your top bar after the restart.

The trap to watch

This node reads what you typed. It does not check whether your model is happy at that size, and that's where people get burned. Every video and image model has a native resolution - generating way above it gets you tiling, duplicated anatomy, stretched limbs; generating at a random in-between size gets you mediocre results. LTX Video's sweet spot moved around as the model updated (512×768 at launch, then 1216×704 at 30 fps from 0.9.6). So before you set a "shot resolution" of 1920×1080 in the panel, make sure it's a resolution your actual model likes, or you're just centralizing a mistake you'd have made anyway.

Also: if the panel's resolution was never set, you'll get defaults and the node will look inert. It mirrors context; it doesn't invent it.