📋 CR Bit Schedule

This is a niche but clever little node in Comfyroll's animation section. You give it a binary string - something like 10110 - and it builds a keyframe SCHEDULE where each bit toggles a value on or off at successive points in the timeline. It's a compact way to write a rhythmic on/off pattern: a strobing effect, a LoRA that flickers in and out, a ControlNet that pulses across frames.

It's from Comfyroll Studio (Suzie1 / RockOfFire), part of the pack's 2023–2024 keyframe-scheduling system - the Deforum-style setup where parameters change at specific frames. Like the rest of that section, it only makes sense inside an animated workflow.

How it works

Each character in the binary_string is a bit: 1 is "on", 0 is "off". The node reads them in order and emits a schedule with a keyframe per bit. The interval controls how many frames each bit occupies (how long each on/off state holds), and loops repeats the whole pattern that many times - so a short binary string can drive a long, repeating rhythm without you writing it all out. The output is a schedule string you feed into the scheduler nodes that actually apply it (or into CR Central Schedule to combine with others).

The inputs that matter

• binary_string - your on/off pattern, e.g. 1010 for alternating. Multiline, so you can lay out longer patterns.
• interval (default 1) - frames per bit. Interval 1 flips every frame; interval 8 holds each bit for eight frames, giving a slower pulse.
• loops (default 1) - how many times to repeat the pattern. Set the string once, loop it across the whole animation.

Outputs: the SCHEDULE (a string), and show_text so you can preview the generated schedule as text - worth wiring to a preview node so you can see what pattern you actually built.

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. It only earns its keep as part of a keyframed animation pipeline.

Common issues

The two dials interact in a way that trips people up: interval sets how long each bit holds, and loops sets how many times the whole string repeats, so your total scheduled length is roughly string length × interval × loops. If the pattern feels too fast or too slow, you're almost always adjusting the wrong one - interval changes the speed of the flicker, loops changes how many times it happens.

Keep show_text connected while you dial it in; the generated schedule is just text, and seeing it is the fastest way to confirm the on/off pattern matches what you meant. And since this is the older animation part of the pack, don't be surprised if it needs the other Comfyroll schedule nodes around it to do anything - on its own it just produces a schedule string, nothing visible. If the node's missing entirely, that's the Comfyroll pack failing to load, a pack-level issue rather than this node.