JK Inspire Scheduler Adapter

This is a type adapter, and the giveaway is right there in its own schema: it takes a scheduler input from ComfyUI's standard 9-option scheduler list (normal, karras, exponential, sgm_uniform, simple, ddim_uniform, beta, linear_quadratic, kl_optimal), and it outputs a scheduler typed against a wider list that adds a few extra entries on top - including things like AYS (Align Your Steps) variants and a GITS scheduler. Those extra names are specific to ComfyUI-Inspire-Pack, which isn't part of core ComfyUI and defines its own, larger scheduler enum for its own sampling nodes.

The problem this solves: ComfyUI checks that a node's output type matches what the receiving input expects, including the exact list of allowed values for a dropdown-typed (COMBO) socket. If you're building your scheduler choice dynamically - say, from a string switch, a text widget, or any node that outputs a plain scheduler name as a string rather than the exact enum type Inspire Pack's nodes want - that connection can get rejected as a type mismatch even though the value itself is perfectly valid. This node exists purely to retype a standard scheduler choice so an Inspire Pack node will accept it.

The inputs and outputs that matter

One input, one output, both named scheduler. The input is the plain, standard 9-choice scheduler dropdown you'd see on any normal KSampler. The output carries the same value forward but typed against the expanded list Inspire Pack expects. There's nothing to configure beyond picking the scheduler you actually want to use.

When you'd reach for this

Only relevant if you're mixing this pack's nodes (or a plain scheduler selection) into a graph that also uses Inspire Pack nodes downstream. If you're not running Inspire Pack, this node has no reason to exist in your workflow - just wire your scheduler choice directly. Its natural neighbor is EasyHRFix and EasyHRFix_Context, the two nodes in this pack that explicitly depend on Inspire Pack for their noise-injection machinery - if you're using either of those and also want to route a scheduler choice from elsewhere into an Inspire Pack node, this is the glue.

Installing it

Part of kostenickj/jk-comfyui-helpers - already on comfy.icu, or cd ComfyUI/custom_nodes && git clone https://github.com/kostenickj/jk-comfyui-helpers.git and restart if self-hosting. This node's own logic needs nothing extra, but it's only useful if you also have ComfyUI-Inspire-Pack installed - a real, actively-referenced pack in the wider community, not something obscure on its own, even though this particular adapter node is a small, low-visibility piece of a small, low-visibility pack.

Common issues

• Still get a type-mismatch error. Double-check you're connecting this node's output - not the original scheduler input - into the Inspire Pack node. It only helps downstream of itself.
• Inspire Pack node still rejects the value. Confirm you actually have a current version of Inspire Pack installed; if its scheduler enum has changed since this adapter was written, the two lists could drift out of sync.
• Unsure whether you even need this. If your scheduler choice is coming straight from a stock ComfyUI dropdown widget directly into an Inspire Pack node's input, you likely don't - this is specifically for cases where the value is passed through as a differently-typed connection rather than set directly on the widget.