HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ace-step
ACE-Step-1.5
Python2026–2026
ace-step / ACE-Step-1.5

ACE-Step-1.5

The most powerful local music generation model that outperforms almost all commercial alternatives, supporting Mac, AMD, Intel, and CUDA devices.

5Distinct people
8Mentions
0Explicit recommenders
14.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The most powerful local music generation model that outperforms almost all commercial alternatives, supporting Mac, AMD, Intel, and CUDA devices.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month8 dated mentions

Observed mentions: 2026-02-03 17:20:21 UTC to 2026-10-14 07:40:01 UTC.

02462026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 7 mentions; 3 submissions, 4 commentsFeb 20262026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 20262026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC734
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC000
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC000
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC000
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC000
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC000
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC000
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC110

What Hacker News says

8 sources
I’ve been experimenting with ACE-Step 1.5 lately and wanted to share a short summary of what actually helped me get more controllable and musical results, based on the official tutorial + hands-on testing. The biggest realization: ACE-Step works best when you treat prompts as [structured inputs], not a single sentence (same as other LLMs) 1. Separate “Tags” from “Lyrics” Instead of writing one long prompt, think in two layers: Tags = global control Use comma-separated keywords to define: - genre / vibe (funk, pop, disco) - tempo (112 bpm, up-tempo) - instruments (slap bass, drum machine) - vocal type (male vocals, clean, rhythmic) - era / production feel (80s style, punchy, dry mix) Being specific here matters a lot more than being poetic. 2. Use structured lyrics Lyrics aren’t just text — section labels help a ton: [intro] [verse] [chor
Read the rest
us] [bridge] [outro] Even very simple lines work better when the structure is clear. It pushes the model toward “song form” instead of a continuous loop. 3. Think rhythm, not prose Short phrases, repetition, and percussive wording generate more stable results than long sentences. Treat vocals like part of the groove. 4. Iterate with small changes If something feels off: - tweak tags first (tempo / mood / instruments) - then adjust one lyric section No need to rewrite everything each run. 5. LoRA + prompt synergy LoRAs help with style, but prompts still control: - structure - groove - energy Over-strong LoRA weights can easily push outputs into parody. Overall, ACE-Step feels less like “text-to-music” and more like music-conditioned generation. Once you start thinking in tags + structure, results get much more predictable. Curious how others here are prompting ACE-Step — especially for groove-based music. resource:https://github.com/ace-step/ACE-Step-1.5
In Ace-Step 1.5 prompt tips: how I get more controllable music output
Hi HN! We released ACE-Step 1.5, an open-sourced AI music model. Key traits of ACE-Step 1.5: Quality: beats Suno on common eval scores Speed: full song under 2s on A100 Local: ~4GB VRAM, under 10s on RTX 3090 LoRA: train your own style with a few songs License: MIT, free for commercial use Data: fully authorized plus synthetic GitHub: https://github.com/ace-step/ACE-Step-1.5 Weights/Training code/LoRA code/Paper are all open. Closed-source commercial models dominate AI music today, tying creators to a single app and model. If access disappears, or the model changes, your creative power can vanish overnight. ACE-Step 1.5 breaks that lock-in with a competitive open-source alternative: run locally, own it, fine-tune with your songs, and reduce privacy/data-leak risk.
In SHOW HN:AceStep1.5an on-device music model that beats Suno on common eval metric

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.