1. Why early endings may occur
In some cases, the model may interpret the track as having reached a natural ending slightly earlier than the intended duration. This can happen due to:
- Internal structure detection (e.g. cadence, resolution points)
- Tempo or arrangement patterns that signal an “ending” to the model
This is a known behavior, and our team is actively working on improving end-of-track handling to reduce premature cutoffs.
2. Why extending may change the melody
When you extend a track after it has already “resolved,” the system treats the extension as a new continuation rather than a simple time fill. This can result in noticeable melodic or arrangement changes instead of a seamless tail.
3. Recommended workaround (current best practice)
To reduce the chance of early cutoffs, we recommend:
- Adding a brief intro or outro instruction in your prompt (e.g. a short instrumental tail or fade-out)
- Planning for a small buffer at the beginning or end of the song to give the model more structural space
This often helps the generation reach its full intended length more consistently.
4. About credits
We’re very sorry that this behavior has caused unnecessary credit usage. If you’ve lost credits due to repeated early endings or failed extensions, please contact our support team with:
- The affected project or music links
- A brief description of what happened
We’ll be happy to review your case and assist with appropriate credit compensation where applicable.