Generate full-length songs with Google Lyria 3.5: verses, choruses and bridges in 44.1 kHz stereo, from a prompt or reference images.
Audio prompts work best when they define mood, pacing, structure, and finish. The more clearly you describe the role of the sound, the cleaner the result tends to be.
Best results start with genre, mood, structure, and arrangement.
Google Lyria 3.5
Generate full-length songs with Google Lyria 3.5: verses, choruses and bridges in 44.1 kHz stereo, from a prompt or reference images.
Use production language, not just genre labels.
Tell the model how the energy should move over time.
For speech, define delivery style, tone, and pacing.
For music, define arrangement and emotional arc early.
A strong audio prompt describes role, pacing, tone, and finish so the output feels produced rather than generic.
Describe the genre, emotional arc, instrumentation, and structure instead of relying on broad tags alone.
Define how the piece should progress so the output feels intentional instead of flat or repetitive.
Use stronger prompts and cleaner references once the direction is already working.
Google Lyria 3.5 is strongest when the brief is clear about function: what the sound should do, how it should move, and what it should feel like.
Use structure language early so the output lands closer to production-ready on the first passes.
For voice work, specify delivery and character. For music, specify arrangement and emotional progression.
Decide whether the output is carrying narrative, mood, rhythm, or all three.
Describe the build, energy, and transitions so the result has movement instead of flattening out.
Once the direction is right, refine and separate instead of regenerating blindly.
Pair voice generation with cloning when continuity across campaigns or characters matters.
Use generated music or speech as the finishing layer once the visual cut is already working.
