ACE-Step 1.5 XL Free Music Generation in ComfyUI (04/12/26)

Use this guide to run ACE-Step 1.5 XL in ComfyUI with a practical setup path: choose the right model path for your VRAM, generate and refine lyrics with local LLM nodes, run first-pass songs, and then remix with conditioning/latent strategies for stronger final outputs.

Source Video

ACE-Step 1.5 XL = Free Music Generation in ComfyUI!

Channel: Nerdy Rodent
Published: 04/11/26
Length: 22m 33s

Watch on YouTube

1) What you will accomplish

Recommended path: Build one baseline song first, then test one remix strategy at a time. Avoid changing five controls at once.

2) Prerequisites

Hardware and runtime assumptions

Software and nodes

Before you start

3) Step-by-step setup and workflow

Step 1, build a clean workflow layout

  1. Create clear groups: Loader, Settings, Prompt/Lyrics, Generation, Remix, Monitoring.
  2. Add switch nodes at branch entrances so you can test quickly without rewiring.
  3. Place Adaptive Projected Guidance in the loader path and add a bypass switch for direct comparisons.
Practical reason: this keeps experimentation fast, reproducible, and less error-prone than manual reconnecting.

Step 2, set baseline generation settings

  1. Choose model branch: turbo, base, or SFT.
  2. Set song length and BPM to a realistic first-pass target.
  3. Set your initial CFG and step values conservatively, then raise in later runs only if needed.

Step 3, configure AI prompt and lyric generation (optional but powerful)

  1. Enable the LLM prompt switch and route topic/style inputs into your lyric/tag generator branch.
  2. If using Ollama + Gemma 4, verify performance settings first. In the video workflow, disabling flash-attention-related behavior improved responsiveness.
  3. Add a post-processor rule: cap tags and enforce output format (for example: max tag count and strict section structure).
Common issue: LLMs often ignore precise formatting requests. Add sanitizing nodes or regex cleanup before passing tags downstream.

Step 4, run a first-pass song and store baseline artifacts

  1. Generate baseline output with prompt branch enabled and remix branches off.
  2. Save key artifacts for comparison: output audio, seed, prompt text, tag list, key settings.
  3. Listen once for structure and once for mix/style character, take separate notes.

Step 5, run controlled remix experiments

  1. Create a second conditioning set with a new seed and slightly altered style/key instructions.
  2. Test approach A: reuse prior latent and apply updated conditioning in a resampler path.
  3. Test approach B: blend conditioning with a conditioning-average node, then render with unchanged core settings.
  4. Optionally inject latent-noise variants for more texture, then compare against plain latent reuse.

Step 6, select winning branch and harden for repeatability

  1. Pick one branch with best lyric intelligibility + style confidence.
  2. Lock seed ranges and preserve exact node groups as a reusable template.
  3. Save as versioned presets (for example: ace-xl-metal-v1, ace-xl-ambient-v1).

Suggested iteration matrix

PassWhat to ChangeWhat to Keep FixedWhat to Evaluate
BaselineNone (initial prompt + settings)Model, length, BPMOverall coherence, lyric fit
Remix ANew conditioning + latent reuseCFG, steps, lengthStyle evolution without structural collapse
Remix BConditioning average blendSeed strategy, durationSmoother transitions, less harsh drift
Remix CLatent-noise injectionPrompt core and modelTexture uniqueness vs artifact risk

4) Practical examples you can copy

Example A, lyric-first workflow

Example B, style-first workflow

Example C, short-version remix

5) Success checks

  • You can toggle Adaptive Projected Guidance on/off and hear a consistent quality difference in your comparisons.
  • You can generate one stable baseline plus at least two remix variants from the same starting run.
  • Your prompt/lyric branch produces usable output after sanitizing (not uncontrolled tag spam).
  • You can reproduce a preferred result family using saved presets and branch settings.

6) Troubleshooting

Problem: XL runs fail or stall

Problem: LLM branch is too slow

Problem: Lyrics are okay but style drifts

Problem: Too many variables changed per run

7) Sources