📋 CR Load Schedule From File

Instead of typing a keyframe schedule into a multiline text box every time - and re-typing or copy-pasting it between workflows - this node reads it straight from a .txt or .csv file on disk. It's the file-based alternative to authoring a schedule inline, useful once your schedule gets long or you want to reuse the same one across several workflows without hand-copying it each time.

How it works

Point it at a file with input_file_path and file_name, and tell it whether that file is txt or csv via file_extension. It reads the file's contents and outputs them as a SCHEDULE object - the same type that CR Load Scheduled Models and CR Load Scheduled LoRAs expect on their optional schedule input - plus a show_text output so you can see exactly what got loaded without opening the file separately, handy for confirming the parse matches what you expect.

This node doesn't validate the content of your schedule against a particular format - CR versus Deforum syntax is a choice that happens downstream, in whichever scheduler node's schedule_format dropdown you point this output at. This node's job stops at "read the file, hand back a SCHEDULE."

Inputs and outputs that matter

• input_file_path - folder path to where your schedule file lives.
• file_name - the file itself.
• file_extension - txt or csv.
• Outputs: SCHEDULE (feeds the scheduler nodes) and show_text (a readable dump of what was loaded).

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, restart. No models involved - this is a plain file reader, so the only thing you need to get right is the path.

Common issues

Path problems are the most likely failure: input_file_path and file_name are separate fields rather than one combined path, so double-check you haven't accidentally duplicated a folder name across both, or left a trailing-slash mismatch. Relative paths behave differently depending on where ComfyUI was launched from - an absolute path is the safer bet if you're not sure.

Mismatches between the .txt/.csv selection and the actual file content will produce a schedule that parses wrong rather than a clean error, so use show_text to check the loaded content looks like what you expect before wiring it further downstream. And as with every node in this pack, if it's missing from the search menu entirely, that points to Comfyroll's shared node-registration file failing somewhere else - check your ComfyUI console for an import error before assuming this specific node is the problem.