📝 CR Keyframe List

If you've ever animated anything with the old A1111 Deforum extension, you know the syntax: 0:(value), 30:(value2), 60:(value3) - frame number, colon, value in parens, comma-separated. CR Keyframe List is where you write and manage that kind of frame-indexed schedule inside ComfyUI, and it can speak two dialects: Deforum's own syntax, or Comfyroll's internal CR format used by its own scheduler nodes.

How it works and why it exists

Deforum - the animation extension that shipped for A1111 back in October 2022 - popularized frame:value keyframing years before ComfyUI had any native video-model support, and a lot of animators who cut their teeth on it carry that syntax around out of habit. It's a genuinely compact way to write "hold at X, ramp to Y by frame 60." CR Keyframe List gives you a box to type that schedule into and a dropdown to pick which format you're writing.

This isn't a scheduler itself - it doesn't apply anything to your model or your prompt. It's the authoring step. The string it outputs is meant to feed into whatever schedule-consuming node further down your graph expects that syntax; Comfyroll's own scheduler and prompt-encoding nodes elsewhere in the pack read exactly this kind of string.

Inputs and outputs that matter

• keyframe_list - a multiline text field (default placeholder text is literally "keyframes") where you type your frame:value pairs.
• keyframe_format - a two-way switch: Deforum or CR. Pick whichever syntax the node consuming this output actually expects.
• Output is keyframe_list (the string, passed through) plus show_help.

There's no value-type validation exposed here - it's a text field, so typos in your keyframe syntax won't be caught until something downstream tries to parse it.

How to install it

Same as every Comfyroll node: ComfyUI Manager → search "Comfyroll Studio" → install → restart. Or manually: cd ComfyUI/custom_nodes && git clone https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes.git, restart. No model downloads - it's a text-authoring node.

Common issues

The format mismatch is the one that'll bite you: if you write Deforum syntax but the downstream node's own format switch is set to CR (or vice versa), you won't get a clean error - you'll get a schedule that silently parses wrong or gets ignored entirely. Comfyroll's animation-schedule nodes (CR Load Scheduled Models, CR Load Scheduled LoRAs, and others in this section) each have their own schedule_format dropdown; keep that in sync with whatever you set here.

Beyond that, it's worth knowing this whole animation-scheduling corner of Comfyroll is from the pre-AnimateDiff era of ComfyUI - before motion modules and native video diffusion, per-frame parameter scheduling driven by a text string was how people got any motion-adjacent variation out of a still-image model. If you're doing anything with a real video model today (Wan, Hunyuan, LTX), you probably don't need this kind of manual frame scheduling; it's mainly relevant if you're maintaining or extending an older Comfyroll-based animation template.

And, as always: if the node's missing entirely, check your ComfyUI console on startup for an import error elsewhere in the pack - one broken section can hide nodes that have nothing to do with it.