EmAySee Lora Loader From Input

Pick the LoRA in one node, apply it in another

EmAySee's LoRA nodes come in two flavors: ones that carry a LORA_OBJECT (a preloaded weights dict) and ones that carry a plain name. EmAySee_LoraLoaderFromInput is the consumer end: it takes a lora_filename input of type LORA, resolves it, and applies it to your model and clip with the usual strength_model/strength_clip pair.

That LORA type input is the key detail. It's not a dropdown and not a raw string - it's designed to receive the lora_filename output of the pack's EmAySee_LoraSelector node, which is the "control" half of the pair: you pick the LoRA and set its strengths there, this node does the actual patching here. You get a clean separation between "which LoRA" and "the sampling graph," which is a nice way to keep a busy graph readable when you're swapping adapters between runs.

How it works

Standard machinery underneath. It takes the filename, resolves it to a full path against your loras folder, and applies it via comfy.sd.load_lora. The fail-safe matches the pack's style: if the file can't be resolved it prints [EmAySee_LoraLoaderFromInput] Lora file not found: ... Skipping Lora application. and passes model and clip through unchanged. So a wrong name won't crash you - it'll quietly render without the LoRA.

Inputs

• model (MODEL), clip (CLIP) - what gets patched.
• lora_filename (LORA) - connect the lora_filename output of EmAySee_LoraSelector, or anything else emitting the LORA type.
• strength_model, strength_clip (FLOAT, −10 to 10, default 1.0).

Outputs: MODEL and CLIP.

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 extra dependencies.

Gotchas

The failure mode is the quiet one: a LORA-typed input that isn't connected to a selector will typically be a stale or empty value, and an unresolvable filename only logs a warning. If a LoRA "isn't working," check the console before you blame the sampler. Also keep the two-piece framing straight: this node does not have its own LoRA dropdown, so don't go looking for one - the dropdown lives on EmAySee_LoraSelector (or EmAySee_LoraNameSelector if you're using the object pipeline with LoraProcessor/LoraStacker20, though that pair uses LORA_OBJECT instead and isn't compatible with this node's LORA input). Matching the wrong selector type to this node's input is the most common wiring error.