Nodes/ComfyUI_Eclipse/Image Resolution Pipe
ComfyUI Node

Image Resolution Pipe

Resolution presets that travel down the pipe instead of loose wires

By r-vage·Created 10 months ago·Updated a day ago· 31
Image Resolution Pipe
    • pipe
    resolution1024x1024 (1:1 XL/SD3/Flux/HiDream)
    width1024
    height1024
    batch_size1

    Image Resolution [Pipe] is the pipe-flavored twin of Image Resolution. Same preset dropdown, same width/height/batch inputs - but instead of three loose INT outputs, it emits a single pipe carrying width, height, and batch_size. The author's own description is the practical one: connect this to a Pipe Out node (like Pipe Out Smart Folder) to retrieve the dimensions.

    This is the Eclipse pipe ecosystem doing what the KB's plumbing doc calls "one wire instead of forty." The pack's whole philosophy is bundling related parameters into a Python dict that flows down one connection, then unwrapping them where you need them with a Pipe Out node. In a workflow that already runs context pipes and smart folders, a resolution pipe means your dimensions travel with the rest of the setup data instead of as three separate wires you have to route around the canvas.

    How you'd use it

    The typical shape: Image Resolution Pipe → (pipe) → Pipe Out Smart Folder → width/height/batch ints wherever the folder config needs them. The pipe carries the resolution alongside whatever else your smart-folder config needs, so the whole "what am I generating and where is it going" bundle stays together.

    The preset list is the same curated set as the plain node - SD1.5 native sizes up through 1024x1024 (1:1 XL/SD3/Flux/HiDream) and friends, plus Custom to unlock width/height. Batch size rides along too (1–64).

    The honest comparison

    If you don't use Eclipse's pipe/smart-folder machinery, skip this and take the plain Image Resolution - three ints are simpler than pipe-and-unwrap. If you do run pipes, this is the version that keeps resolution data in the same format as everything else, which means you can merge, override, or pass it through the pack's Concat/Pipe Out nodes. It's a consistency play, not a capability play. Neither node touches pixels; they're both settings sources.

    Installing

    ComfyUI_Eclipse, r-vage's all-in-one pack. Manager → search ComfyUI_Eclipse, or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/r-vage/ComfyUI_Eclipse
    

    Restart; under Eclipse → Settings. Standard deps; Eclipse targets current ComfyUI (frontend 1.51.2+) and its v4.0 rewrite removed legacy RvTools_v2 nodes (Migration Tool included).

    The one thing to remember: a pipe output only does something once you unwrap it with a Pipe Out node. Wire it to a generic preview and you'll just see a dict. Match it with Pipe Out Smart Folder (or whichever pipe-out node carries the fields you need) and the values land where you expect.

    Category🌒 Eclipse/ Settings

    Inputs (4)

    NameTypeDefaultDescription
    resolutionCOMBO1024x1024 (1:1 XL/SD3/Flux/HiDream)Select a preset resolution or 'Custom' to enter custom dimensions.
    widthINT102416–32768Custom width (used when 'Custom' is selected).
    heightINT102416–32768Custom height (used when 'Custom' is selected).
    batch_sizeINT11–64Number of images to generate at once.

    Outputs (1)

    NameTypeDescription
    pipePIPEOutput pipe containing width, height, and batch_size parameters.