Nodes/Comfyroll Studio/πŸ› οΈ CR Current Frame
ComfyUI Node Runs on cloud

πŸ› οΈ CR Current Frame

A frame-index passthrough for animation loops

By Suzie1Β·Created 3 years agoΒ·Updated 2 years agoΒ· 1,296
πŸ› οΈ CR Current Frame
    • index
    β—„index1β–Ί
    β—„print_to_consoleβ–Ύβ–Ί

    This is a tiny utility node with one job: hold the current frame number and pass it downstream as an integer. In Comfyroll's frame-by-frame animation workflows, lots of nodes need to know "which frame are we rendering right now?" - the schedulers, the cycle nodes, the interpolators. Current Frame is the single, obvious place to set that value so everything reads from one source.

    It's from Comfyroll Studio (Suzie1 / RockOfFire), in the Animation β†’ Utils group. Think of it as the frame counter for a manual animation loop - you set it, and it feeds the number wherever a frame index is expected.

    How it works

    There's not much to it, which is the point. You set index - the current frame number, ranging from βˆ’10000 to 10000 - and the node outputs that exact integer. The optional print_to_console toggle (Yes / No) echoes the frame number to the ComfyUI console when it runs, which is handy for confirming your loop is advancing the way you think.

    The wide negative range exists because frame math sometimes needs offsets and lead-in frames; most of the time you'll just be feeding it 0, 1, 2, and up.

    The inputs that matter

    • index (βˆ’10000 to 10000, default 1) - the current frame number. This is the whole node.
    • print_to_console (Yes / No) - log the frame number as it runs, for sanity-checking the loop.

    Output is a single index (INT). Unlike most Comfyroll nodes, there's no show_help output here - it's just the number. Wire it into any node that takes a frame index: the cycle nodes' current_frame, a scheduler, or an interpolator.

    Where you'd actually reach for it

    In Comfyroll's older animation style, you render one frame per queue run and advance the frame number each time. Current Frame is the knob you bump between runs, and because it's a single source, every downstream node that depends on the frame stays in sync. It saves you from typing the same frame number into three different nodes and getting them out of step.

    Straight talk: this belongs to Comfyroll's manual frame-by-frame approach, which is older than today's AnimateDiff and video-model pipelines. If you're on a modern batch-animation workflow, you probably won't touch it. It's for people running the Comfyroll cycle/scheduler nodes, where a shared frame index is exactly what you need.

    How to install it

    • ComfyUI Manager: search Comfyroll Studio, install, restart.
    • Manual: cd ComfyUI/custom_nodes && git clone https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes.git, then restart.

    No downloads - it outputs a number.

    Common issues

    If the node's missing from your menu, that's almost always the whole pack failing to load. On newer ComfyUI builds Comfyroll can throw during startup - a submodule fails to import and the console fills with NameError: name 'CR_...' is not defined, taking every CR node with it. Scroll to the first error (the real cause) and update the pack via Manager.

    Node-specifically there's essentially nothing to break - it hands out an integer. The only real "issue" is expecting it to advance on its own. It won't; it's a value holder, not a counter with memory. In the manual workflow you set the index each run (or drive it from an upstream incrementer). If your animation isn't progressing, that's the thing to check.

    Category🧩 Comfyroll Studio/πŸŽ₯ Animation/πŸ› οΈ Utils

    Inputs (2)

    NameTypeDefaultDescription
    indexINT1-10000–10000β€”
    print_to_consoleCOMBO2 options: Yes, No

    Outputs (1)

    NameTypeDescription
    indexINTβ€”