All stories
EXPLAINER
MUSIC TECHNOLOGY
How AI music generation works
From text to sound: the technology behind a new way to create.
2 min read
7 sections
Plain-language explainer
01
Your description
Mood · instruments · style
02
Model generation
Patterns represented as data
03
Audio output
A track you can listen to
A text-to-music system takes a written description and produces audio guided by it. A phrase such as “gentle piano with a slow, reflective mood” gives the model a direction. But how does that direction become sound?
01
The prompt guides the generation
Researchers call this conditioning: supplying information that shapes a model’s output. Google’s MusicLM research demonstrates music generation guided by text descriptions. Some systems can also accept a melody as guidance.
The text is not a musical score with every note specified. It describes qualities the model should aim for. Think of a prompt as creative direction rather than a complete arrangement.
02
Music can be represented as audio tokens
MusicGen provides one documented example of this process. It uses an audio tokenizer called EnCodec to represent sound as sequences of compact codes. These codes are often called audio tokens; they are not written words or individual musical notes.
A transformer model generates token sequences conditioned on the description. The audio codec decodes those representations into a waveform you can hear.
This is a simplified explanation of MusicGen, rather than a description of every music generator.
03
Different models take different routes
MusicGen uses a single-stage transformer architecture. MusicLM describes a hierarchical approach with multiple stages. Both show how text can guide music, but their internal designs differ.
These research models are examples, not claims about Sondu’s underlying provider. Sondu’s interface lets you submit a description, lyrics, or an instrumental direction. The interface alone does not reveal the generation model’s architecture.
04
Why the same description can produce different music
MusicGen’s documentation exposes sampling controls such as temperature and top-k. Sampling chooses among possible outputs, so a description does not necessarily determine one fixed track. Whether a product exposes those controls depends on its implementation.
This helps explain why another attempt may sound different. For practical comparison, keep your description stable and change one detail at a time. Listen for the difference instead of expecting an identical arrangement.
05
Technical terms do not guarantee exact results
MusicGen’s model card notes limitations with vocals and fine-grained control. These are limitations of that model, not a universal statement about Sondu. They illustrate why it matters to evaluate the audio a system actually produces.
In your own listening checks, assess rhythm, vocal clarity, transitions, and the ending. A technically detailed prompt is still a request. The generated track is what tells you whether the result meets your goal.
06
Using this understanding in Sondu
Use Quick to describe a sound, or Custom to start with lyrics or an instrumental direction. Keep the key musical details clear. Then listen, review, and refine the result.
Follow the step-by-step Sondu guide
07
Research sources
This explainer draws on publicly documented research examples. It does not identify Sondu’s model, training data, or internal generation pipeline.
MusicGen documentation
Meta AudioCraft
MusicGen model card
Meta AudioCraft
MusicLM: Generating Music From Text
Google Research
YOUR TURN
Hear how a description becomes sound
Policy
Blog
Delete account
© 2026 Sondu AI
abenales.tech
RESTORING SONDU