📋 CR Central Schedule

This one lives in Comfyroll's animation corner, which is a whole keyframe-scheduling system for driving parameters across frames - the Deforum-style idea where a value, prompt, LoRA, or camera move changes at specific frame numbers as the animation plays. Central Schedule is a hub node: it takes up to three separate schedules, tags each with a type and a name, and merges them into one combined SCHEDULE that the rest of the animation nodes read from.

Fair warning up front: this is the older, more advanced end of Comfyroll (Suzie1 / RockOfFire). The scheduling nodes date from the pack's 2023–2024 animation push and assume you're building a keyframed pipeline. If you just want a still image, you're in the wrong section of the pack.

How it works

A schedule in Comfyroll is text: lines that pair a frame number with a value. Different things get scheduled differently - a prompt schedule reads as text, a value schedule as numbers, a LoRA schedule as model references. This node lets you bring in three of those at once, label each with a schedule_type (so the system knows how to interpret it) and a schedule_alias (a name to reference it by), and fold them together - optionally onto an existing incoming schedule - into a single central schedule.

The schedule_format toggle chooses the output convention: CR for Comfyroll's own format, or Deforum if you're feeding a Deforum-style consumer.

The inputs that matter

• schedule_1 / schedule_2 / schedule_3 - the three schedule strings to combine (multiline).
• schedule_type1/2/3 - what each one is: Value, Text, Prompt, Prompt Weight, Model, LoRA, ControlNet, Style, Upscale, Camera, or Job. This tells the system how to parse that schedule - get it wrong and the values won't be read correctly.
• schedule_alias1/2/3 - a name for each schedule so downstream nodes can pull the right one by reference.
• schedule_format - CR or Deforum.
• schedule (optional) - an existing SCHEDULE to merge these onto, for building up in stages.

Outputs: the combined SCHEDULE, and show_text, which dumps the merged schedule as text - genuinely useful here, wire it to a text preview so you can actually see what got combined.

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 models - but the animation nodes only make sense as part of a larger keyframed workflow (typically with AnimateDiff or a frame-by-frame setup).

Common issues

The most common mistake is a type mismatch: tagging a schedule as Value when it's actually a Prompt, or vice versa. The schedule_type is how the parser knows what it's looking at, so a wrong tag produces a schedule that silently reads empty or wrong. Set the type to match the content.

Keep that show_text output connected to a preview while you build - the whole animation subsystem is text-schedules feeding text-schedules, and it's very easy to lose track of what's actually in the merged result. Seeing the combined text is how you debug it. And because this is the older, less-trafficked part of the pack, it's also the part most likely to be rough on a bleeding-edge ComfyUI; if the animation nodes misbehave, that's the pack's age showing rather than your graph being wrong.