Same Lyria 3.5 prompt, different song: why, and no seed on Sume

Google says Lyria results vary between calls. Sume's music API has no seed. How to keep the take you like and generate a few to choose from.

3 min readSume
All posts

The same Lyria 3.5 prompt can give a different song every time, and Sume's music docs list no seed to fix it. Google's music-generation guide, read 2026-10-01, says results vary between calls and that generation is single-turn, with no multi-turn editing.

What should I do instead?

Treat each call as a take. Generate two or three with different Idempotency-Keys, listen, and keep the artifact you like. Each costs a fixed $0.125, and the saved file on media.sume.com is your master.

Taking several Lyria 3.5 takes on Sume, from the Music 1.0 and Music Router docs, read 2026-10-01.
ItemValue
SeedNone listed
Cost per take$0.125 fixed
Edit callNone; change the prompt and generate again
Retry with the same Idempotency-KeyReturns the same job
New Idempotency-KeyA new take

Can I tweak a track?

Not in place. There is no edit call; change the prompt and generate again. To trim or join, use Timeline audio.

What about retries?

An Idempotency-Key makes a retry return the same job rather than a new song. A new key is a new take.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume