EmAySee Lora Name Selector

The control panel half of the string-based LoRA pipeline

EmAySee_LoraSelector is a widget-only node: no inputs, just three controls - a LoRA dropdown and two strength sliders - and three matching outputs. It's the "decide here" end of EmAySee's string pipeline, designed to feed EmAySee_LoraLoaderFromInput, which does the actual patching. You pick the adapter and set its strength_model/strength_clip in one tidy spot, and the loader downstream applies it.

The LORA-typed lora_filename output is the thing to understand. It's the same type ComfyUI's own LoraLoader uses for its dropdown internally, so LoraLoaderFromInput accepts it directly - that's the intended pairing. The two float outputs just echo the strength widgets so you can see them as data, and nothing stops you from routing them into a print node or a batch grid.

Inputs (widgets) and outputs

There are no wire-in inputs; all three controls render as widgets on the node:

• lora_name (LORA, default "NONE") - the dropdown of your loras folder.
• strength_model, strength_clip (FLOAT, −10 to 10, default 1.0).

Outputs:

• lora_filename (LORA) - the selected file, for LoraLoaderFromInput.
• strength_model (FLOAT), strength_clip (FLOAT) - echoed strengths.

Install

From ComfyUI_EmAySee_CustomNodes:

cd ComfyUI/custom_nodes
git clone https://github.com/EmAySee/ComfyUI_EmAySee_CustomNodes
# restart ComfyUI

Or via ComfyUI Manager → "ComfyUI_EmAySee_CustomNodes". No dependencies.

Gotchas

The trap here is mixing it up with the object pipeline. If you wire this node's lora_filename into a LORA_OBJECT-based consumer like LoraProcessor or LoraStacker20, the types won't match - those want the pre-loaded weights from EmAySee_LoraNameSelector, not a LORA name. Keep the pairing straight: LoraSelector ↔ LoraLoaderFromInput for the string pipeline, LoraNameSelector ↔ LoraProcessor/LoraStacker20 for the object pipeline. Also, since there are no inputs, this node can't be driven by graph data - it's a manual-selection control surface, which is exactly what it's for. One lighter note: the default name is "NONE" (all caps, unlike the "None" used elsewhere in the pack), so if you see a workflow skip a LoRA after this node, check the exact default casing.