Music Generation
Models that produce music from a description — good enough for background, and sitting on an unresolved argument about whose work it learned from.
When not to use it
- When the music is the point. Structure and intent are missing, and that's what songs are made of.
- When provenance matters and the training data is undisclosed. For any commercial media use, "we don't know what it learned from" is a risk you're accepting on someone's behalf.
- When you need a specific composition. Prompts control style, not form. If you know what you want musically, a musician is faster.
- For long-form. Coherence degrades with length and there's no configuration that fixes it.
Reach for something else instead
- Licensed stock libraries — clear provenance, unremarkable music. Currently the safe option.
- A composer — for anything where structure or intent matters.
- Models trained on licensed or owned catalogues — the provenance answer, at some quality cost.
- Symbolic generation (MIDI) — gives you notes you can edit rather than audio you can't.
Sources & further reading
- Dhariwal et al. (2020), Jukebox: A Generative Model for Music — raw audio with vocals; the ambition and the compute cost.
- Agostinelli et al. (2023), MusicLM: Generating Music From Text — semantic-then-acoustic token hierarchy; the shape most current systems use.
- Copet et al. (2023), Simple and Controllable Music Generation — MusicGen; single-stage token modelling and practical conditioning.
Primary sources, listed so you can check the claims on this page rather than take them on trust.
Where people go wrong
- Judging the technology on a thirty-second sample and assuming it holds for three minutes. It doesn't.
- Using undisclosed-training-data models in commercial work and treating the legal question as someone else's.
- Prompting for composition. Adjectives control texture; they can't specify form.
- Assuming output is automatically clear of the training data. Memorisation happens and detection is poor.