📋 CR Simple Schedule

This is where Comfyroll's animation keyframe system actually starts. A SCHEDULE in this pack is text: lines pairing a frame number with a value, the same Deforum-era idea of "this parameter changes at this frame" - except Comfyroll generalized it well past prompts. CR Simple Schedule is the node that authors one of these - pick what kind of thing you're scheduling, write your frame/value lines, and it outputs a typed SCHEDULE the rest of the animation nodes can consume.

How it works

You write your keyframes into the schedule text box, following the pattern the default text hints at: frame_number, item_alias, [attr_value1, attr_value2]. What schedule_type you pick tells the rest of the system how to interpret those values - eleven options: Value, Text, Prompt, Prompt Weight, Model, LoRA, ControlNet, Style, Upscale, Camera, Job. A Value schedule reads its entries as plain numbers, a Prompt schedule reads them as text to inject at that frame, a LoRA schedule expects model/weight references, and so on - the type is what makes the same underlying line format mean something different depending on what you're actually animating. schedule_alias gives this particular schedule a name so a downstream merging node (like CR Central Schedule) can pull it out by reference when you're combining several. schedule_format picks the output convention - CR for Comfyroll's own, or Deforum if whatever's consuming it downstream expects that syntax instead.

The inputs and outputs that matter

• schedule - your frame/value keyframe lines. This is the actual content you're authoring.
• schedule_type - what kind of thing is being scheduled. Get this wrong and the value at each frame gets misread by whatever consumes it.
• schedule_alias - a name for this schedule, useful once you're merging multiple.
• schedule_format - CR or Deforum output syntax.

Output: SCHEDULE, wired into a downstream animation-consuming node or into CR Central Schedule for combining with others, plus the standard show_help link.

How to install it

Comfyroll Studio (Suzie1 and RockOfFire). The animation nodes only make sense as part of a larger keyframed workflow, typically alongside AnimateDiff or a frame-by-frame render setup - no models required by this node specifically.

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

Common issues & troubleshooting

Downstream node reads your schedule wrong or reads it as empty. This is almost always a schedule_type mismatch - tagging a prompt schedule as Value, say. The type is how the parser decides what shape to expect in each line; a wrong tag means it's looking for the wrong thing and silently fails to extract anything useful.

Not sure what to actually write in the schedule box. The default placeholder text is the format hint: frame number, an alias for that entry, then the values in brackets. Start from a single line, confirm it reads correctly downstream, then add more frames rather than writing a long schedule blind.

You have several schedules and need them combined. This node only authors one schedule at a time. For merging several - a Prompt schedule plus a Camera schedule plus a LoRA schedule, say - feed them all into CR Central Schedule, which takes up to three at once and folds them together.

Comfyroll nodes missing entirely. If nothing from the pack loads, check your startup log for Comfyroll Studio: Failed to load Graphics nodes and a trailing NameError: name 'CR_HalftoneGrid' is not defined - a symptom of an earlier import error, commonly a Pillow version conflict from another custom node. Force-reinstall Pillow (pip install --upgrade --force-reinstall pillow) or reinstall cleanly, then restart.