JZL - 🎵 MiniMax Music3 歌词编辑
It's a text box with buttons — and that's exactly what Music3 lyrics need
- lyrics
The name oversells it. JZL - 🎵 MiniMax Music3 歌词编辑 doesn't write lyrics, doesn't call an API, doesn't need a key, and doesn't touch a model. It's a plain text box with a row of shortcut buttons, and once you've hand-fed MiniMax Music3 a song structure you'll understand why that's the whole point.
MiniMax Music3 is picky about lyrics the way a composer is picky about a lead sheet: it expects the official section tags - [Intro], [Verse], [Chorus], [Bridge], [Outro] - and it treats the structure as instructions, not decoration. Typing those brackets by hand is where songs go wrong, because it's exactly the kind of fiddly, repetitive thing you'll typo at 1 a.m. This node exists to make the bracket part impossible to get wrong.
How it works
Pure pass-through with a nicer editor. You type (or paste) lyrics into the lyrics_text field, and the node hands the exact same string back out through lyrics. The front-end adds the value: a tag picker on the node with 21 official MiniMax tags, including the obvious [Intro]/[Verse]/[Pre-Chorus]/[Chorus]/[Post-Chorus]/[Bridge]/[Instrumental]/[Solo]/[Outro], plus the Music3-specific ones like [Hook], [Breakdown], [Breakdown to drums-Chorus], [All in Chorus], and [Final Chorus]. Click a tag and it's inserted at your cursor with a newline after it, so you're always building one-tag-per-line and never retyping.
There's exactly one input (lyrics_text, multiline) and one output (lyrics, a plain STRING). Wire that output into the official MiniMax Music3 Text Encode node's lyrics input and you're done - that's the whole workflow.
Installing it
It ships inside the JZL MiniMax pack, so you're installing the pack, not the node:
- ComfyUI Manager → Install Custom Nodes → search
JZLorComfyUI-JZL-MiniMax-H3. - Or manually:
cd ComfyUI/custom_nodes && git clone https://github.com/wjluoxiao/ComfyUI-JZL-MiniMax-H3and restart.
The pack wants a fairly new ComfyUI - it uses the V3 io.Schema API for its reference-encoding nodes, which means you need a version that ships comfy_api.latest and the official MiniMax H3 nodes. This particular node is featherweight though: no model downloads, no llama runtime, nothing in requirements.txt applies to it.
Where people get burned
Not much to burn here, honestly. The one trap is thinking it does more than it does: if your Music3 output ignores the structure you wrote, the problem is upstream - check that you actually used the official tag spellings (which the buttons guarantee) and that the lyrics output is the one wired into Text Encode. And a heads-up for English speakers: the whole JZL pack is Chinese-first, so the node's label and buttons lean Chinese with the English tag names alongside. The buttons themselves are English, which is what matters.
For a node whose entire job is "don't let me typo a bracket," it's quietly great. Grab it when you're building a Music3 song workflow and you'll stop thinking about it by the second song.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| lyrics_text | STRING | 歌词文本。点击下方按钮可在光标处插入官方段落标签:[Intro]/[Verse]/[Pre-Chorus]/[Chorus]/[Post-Chorus]/[Bridge]/[Instrumental]/[Solo]/[Outro] 等 |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| lyrics | STRING | — |