On 20 February 2026 at 14:21 Asia/Shanghai, zombiepiratebacon described a late-song failure that shows up after a draft is already working.

“The final chorus dips out. The music strips back, all that momentum is gone, your final chorus plays as if it is reflective rather than anthemic.”

The earlier verse–chorus passes had already worked, and the bridge was fine. The last hook was supposed to be the peak. Instead it arrived quieter and thinner, more like a wind-down than a last chorus. The useful part is the shape of the mistake: the song already has a hook worth keeping, and the continuation treats that hook like an outro. This checklist is for stopping that drop when you extend a finished draft.

Decide whether you actually want the song to recede

A quieter last chorus is a problem only when you wanted a peak. Some songs should thin out: a receding outro, a last line almost alone, a fade. If that is the ending you want, say so clearly and stop here. The failure to fix is different. What disappeared is weight: the snare softens, a doubled vocal becomes a single close vocal, a guitar figure turns into single notes. The join can be smooth and still feel like a comedown.

Write that in one sentence before you spend another run: “I want the last chorus as full as the second chorus, then a short stop — not a reflective strip-back.” If you cannot name what should stay as loud as the earlier hook, you do not yet have a test you can listen for.

Save the source, then pick a complete-phrase boundary

Do not extend the first almost-good file you click. Open the library, check the title, and play the take you actually want to keep — related versions can look almost identical. In EasyMusic.AI, open the completed song’s … menu and choose Extend. The operation opens a timeline. Material before the boundary is kept; what follows is recreated from your continuation instructions. Save the source first so you can compare later. An extension should not overwrite the take you already like.

Move the boundary while you listen, and preview the kept and recreated regions. Place it on a complete musical phrase, not on the last available second. If the last two bars of the bridge have already started to thin — a held vocal, a fill that dies away, a soft button ending — and you start from there, listen to whether the continuation comes in with that same drop. If it does, put the boundary earlier, on a phrase that still has the drum weight you want the last hook to match.

When aligned lyrics exist, moving the boundary first fills the continuation field with the words after that point. Once you edit those words, later moves keep your draft. If there is no usable timing, do not treat the waveform as a lyric map — a visible wave does not mean synchronized lyrics exist. Use the manual time control to set the boundary, check that position against playback, and write the continuation lyrics yourself in the continuation field.

Ask for a last hook, not an outro

Include only what should be sung after the boundary. If the field still contains a receding outro, a fade, or a last whispered line, you are asking the model to start winding down.

Keep the hook lyric close to the chorus that already works. Short, repeatable lines travel better than a new paragraph of commentary. A [Final Chorus] tag is a signpost, not a lift by itself. Add one or two audible cues beside the label:

[Final Chorus — full band, stacked vocal, same drum weight as the earlier chorus, no fade]
Leave the porch light on
Leave the porch light on
I still know the way back home
Leave the porch light on

That block is hypothetical — rewrite your own hook. The instruction is the point: fullest arrangement, same chorus words, no strip-back. Keep the style consistent unless you really want a transition. “More energy” is too vague to check; name something you can hear: same snare weight, doubled vocal, the guitar figure between lines, no breakdown, no fade. If you also want a short ending, you can include it in the same continuation — the field can describe a final chorus or an outro. If the hook then starts winding down early, a later, shorter ending pass is an optional experiment, not a required second paid extend. You can also ask for the last hook alone first, then decide whether you still need an ending.

Generate once, then listen at the join

Extension needs eligible paid access and enough balance. Read the charge shown for the options you picked, then submit once. Do not send a second request because the file has not appeared yet.

The current flow can assemble the continuation into a complete song automatically. Listen to that completed result before you hunt for a separate join button. Some older or partial results still offer Get Full Song; use it only when that control is shown, and only as a way to assemble a new version.

Listen three ways: the phrase before the boundary, so you remember the weight you wanted to keep; across the join, for cut-off syllables, repeated words, a hole in the vocal, or a jump in loudness; and the whole last chorus without pausing, compared with an earlier chorus from the same source.

A usable result is not “the new file is louder.” It is that the last hook still feels like the same song, the parts you named are still there, and the join does not advertise itself. If loudness drops suddenly at the boundary, move the boundary before you rewrite the lyric.

If the energy still drops, change one thing

If the join is awkward, move the boundary to another complete phrase before you rewrite all of the instructions. Try the bar where the last full-band hit still exists, or the downbeat before the hook lyric returns.

If the join is clean and only the arrangement recedes, use Smart refine rather than another vague “make it bigger” extend. Smart refine is a new generation from a completed source; the original stays saved. The instruction field accepts up to 500 characters, it requires paid access, and the current cost is 20 credits — check the button before you submit. Name one audible change: “In the final chorus, keep the same drum weight as the earlier chorus and make the hook build rather than thin out. Keep the lyric.” Listen to the new version and to the sections you did not ask to change. Voice, timing, or melody can still shift even when you ask for preservation. If the result has wandered away from the song you wanted to keep, start again from the original rather than stacking demands on a drifted take.

If only a line of wording is wrong and the energy is fine, use timed lyric editing, not another arrangement pass. A DAW edit is a fair last step when you like the performance and only need a level to stay put, but it is not the first lever. Check the boundary and the continuation text first, especially if the text is already asking for an outro.

What you should expect, and what this will not do

After a careful extend you should have the original take, the new complete song, and a clear listen at the join. Sometimes the last hook holds. Sometimes one Smart refine request is enough to test a single arrangement change. Sometimes the generator still writes a reflective last chorus; a label cannot forbid that outcome. There is no energy lock, no guaranteed identical vocal, and no promised loudness match with the earlier hook. “Full band” is a direction you can check, not a control that forces a mix.

These operations are paid — review the displayed charge. A free account can be a place to start making songs; it does not make extend or refine free. Commercial use requires a plan that explicitly includes commercial licensing; check pricing. The documented extend path is at https://docs.easymusic.ai/tutorials/extend-and-complete-song/.

If two honest attempts — one boundary move, one specific refine — still give you a soft last chorus, the draft may want a shorter last-chorus lyric, or a short contrast phrase before the hook returns. That is a structure choice, not proof that you should throw away the verses you already like. Keep the source until you have downloaded the version you are willing to live with, and name the files so you can tell “full last hook, take B” from the quieter first continuation.

Disclosure: written by the EasyMusic.AI team, with AI assistance.