YuE2 LoRA:
YuE2LoRA, displayed as “YuE2 LoRA” in ComfyUI, prepares LoRA adapters for YuE2 music-generation workflows, including Generate Song, Plan, Plan Batch, and Render Plan. A LoRA is a compact set of adjustments that changes how a model behaves without replacing the entire model. This node lets you combine adapters and adjust their influence separately for YuE2’s two halves: AR, which writes the score and sings the performance, and NAR, which turns that performance into sound. It recognizes YuE2 adapters stored in both ComfyUI’s LoRA layout and m-a-p’s layout, helping avoid the silent non-application that can occur when m-a-p files are used with ComfyUI’s standard LoRA loader. Its file browser filters out unrelated adapters and provides information about recognized files, including their affected model halves, rank, trigger words, and compatibility problems when available. The node prepares adapter selections rather than generating audio itself; downstream YuE2 processing applies the adjustments. In normal operation, adapters are folded into model weights once per stage, preserving generation speed after that preparation. With low_vram, adapters are held alongside packed layers instead, with a documented token-speed cost of approximately 10%.
YuE2 LoRA Input Parameters:
loras
loras is a required STRING that stores this node’s adapter selections as a JSON list. Its default is "[]", meaning no local adapters are selected. Although the underlying parameter is a single-line text widget, the extension’s browser interface presents it as editable rows, with one adapter file and separate AR and NAR strengths per row. These strengths let you control the adapter’s influence on the performance-producing and sound-producing halves independently. The interface also displays information about what each file changes and any available trigger word. Use the row controls rather than manually composing JSON whenever possible, because malformed saved data can prevent the node from executing. The declared string input has no numeric minimum, maximum, or fixed list of options; available file choices come from recognized YuE2 .safetensors files in ComfyUI’s configured LoRA folders. The surrounding source defines a strength limit of 10.0 in either direction, but the supplied node class does not specify per-row strength defaults or the complete JSON schema.
lora
lora is an optional YUE2_LORA connection that accepts adapter selections from another YuE2 LoRA node. Use it to chain nodes when you want to organize adapters into separate groups while applying them together. The incoming selections are placed before this node’s own selections in the combined list; they are not replaced by the local rows. If you leave this input disconnected, the node uses only its own selections. If the local list is empty, incoming selections still pass through. This is a connection carrying structured adapter data, not a numeric or text setting, so no minimum, maximum, selectable options, or explicit widget default is declared. Without a connection, the implementation treats it as no incoming adapters.
YuE2 LoRA Output Parameters:
lora
lora is the node’s single YUE2_LORA output. It contains the combined adapter selections from the optional incoming connection and this node’s local rows, ready for a compatible YuE2 generation or planning node. Each prepared adapter entry carries identifying information, including its name, file, SHA-256 fingerprint, and AR and NAR strengths. The fingerprint identifies the selected file’s contents, helping preserve the adapter identity when settings travel into cached plans and song memory for later editing. This output is configuration data, not generated audio or an already-modified model: the actual adapter application occurs during downstream processing. With no incoming adapters and no local selections, it contains an empty list.
YuE2 LoRA Usage Tips:
- Put YuE2
.safetensorsadapters in ComfyUI’s configured LoRA folders. Subfolders are supported, and selections use relative names with forward slashes for portability between operating systems. - Use this node for YuE2 adapters rather than assuming ComfyUI’s standard LoRA loader supports every file layout. The supplied documentation specifically notes support for m-a-p files that the standard loader can leave unapplied without reporting it.
- Read each row’s compatibility information before generating. Check which model halves the adapter changes, whether it lists a trigger word, and whether it reports a reason it cannot be applied.
- Start with one adapter and make small strength adjustments while comparing results. Change AR and NAR separately to better understand which part of the result is affected; the usefulness of either control depends on which halves the adapter actually contains.
- Follow an adapter’s own instructions for trigger words when available. The node displays trigger information, but the supplied code does not establish that it automatically adds those words to your generation settings.
- Chain multiple YuE2 LoRA nodes through
lorawhen you want to keep adapter groups organized. The selections are combined, so review both upstream nodes and local rows when checking which adapters will be used. - Leave the local rows empty to pass through an upstream adapter collection without adding anything. With no upstream connection either, the node produces an empty adapter collection.
- Account for the performance trade-off when using
low_vramelsewhere in your YuE2 workflow. Normal operation folds adapters into weights once per stage; the low-VRAM path instead carries an approximately 10% token-speed penalty.
YuE2 LoRA Common Errors and Solutions:
Invalid adapter-row data — descriptive error category
- Explanation: The local selections must be readable as the expected JSON row structure. The node catches
ValueErrorduring selection processing and reports the associated message; the supplied excerpt does not include the exact validation messages. - Solution: Edit selections through the row interface rather than manually changing the stored string. If a manually edited workflow fails, reset the local list to
[]and add your adapters again.
Selected adapter file not found — descriptive error category
- Explanation: An adapter named in the saved rows cannot be located, for example because it was moved, renamed, deleted, or is unavailable on the current machine. The node catches
FileNotFoundErrorand reports its message. - Solution: Restore the file to a configured ComfyUI LoRA folder or select its current location through the node’s browser. When transferring workflows, preserve the adapter’s relative subfolder and filename.
Recognized YuE2 adapter cannot be folded — descriptive compatibility warning
- Explanation: A file can contain tensors that match YuE2 while also containing unsupported parts. The catalogue intentionally lists recognized but unusable adapters with a reason, including cases involving parts that do not map to the model or adapters that bring additional modules of their own.
- Solution: Read the reason shown for the file and use a compatible adapter version. Renaming the file will not fix an unsupported internal structure.
listing the LoRA files failed
- Explanation: This text appears in the server log when the adapter-listing route encounters an unexpected exception. The route returns an empty list and an error indication to the interface; the exact browser-facing message is not included in the supplied source.
- Solution: Check the ComfyUI console for the accompanying exception. Confirm that configured LoRA folders are accessible and files are readable. If the error identifies a particular file, temporarily remove it from the scanned folder and retry.
An adapter does not appear in the list — descriptive symptom
- Explanation: The catalogue only lists
.safetensorsfiles whose tensor names and shapes identify them as YuE2 adapters. Ordinary image LoRAs are intentionally excluded, and files outside configured LoRA folders are not discovered. - Solution: Confirm that the file is intended for YuE2, uses the supported file extension, and is stored in a configured LoRA folder. Do not assume that an adapter is compatible simply because another ComfyUI loader can display it.
An adapter has little or no apparent effect — descriptive symptom
- Explanation: Influence depends on the selected strengths, the model halves the file actually modifies, and any adapter-specific usage requirements. Adjusting a half that the adapter does not target will not add changes to that half.
- Solution: Review the file’s affected-half information and trigger-word guidance, verify the selected strengths, and confirm that the
loraoutput is connected to the intended YuE2 node. Test the adapter alone before combining it with others.
