Suno retires older models: keeping a brand jingle reproducible

If a brand jingle was made on an older Suno model, plan on never regenerating it. TechCrunch reports that Suno's new v6 models replace the old ones and that older models are to be retired. Even on a model that stays available, generative music is not repeatable: Google's Lyria guide says outputs vary across identical calls. The only reliable copy of a jingle is the file you saved, together with the record of how it was made.

What is known about model lifetimes

Two facts, from two sources, point the same way.

What to store with a jingle

Treat the generated file as the master and keep these next to it.

• The delivered audio file itself, in lossless form where the tool offers it. Google's guide lists WAV alongside MP3 for Lyria.
• The exact prompt, including any section tags or timestamps.
• The model id that ran, and the date.
• The job or generation id, and the plan or terms in force the day you generated it, which matters if rights depend on a paid tier.
• Any stems or edits made later, labelled as derived from the master.

How this looks in Sume

Sume's Music Router returns completed audio as a hosted artifact on Sume media URLs, and the job records request.routed_model, the engine that ran, such as lyria-3.5. You can pin that id instead of using sume/music-auto when you want the engine to stay fixed across calls. Pinning chooses the engine; it does not make the output repeatable, so the stored artifact is still the master.

Download the artifact into your own asset store soon after the job completes. The docs describe hosted artifacts but do not set a retention promise, so I would not rely on a link as an archive. Sume does not ship Suno; this checklist applies to any music tool.

If you need a jingle to evolve

When the brief changes, such as a new length or a different mood, write a new prompt from the saved one and generate again, accepting that it is a new piece. For continuity, keep the prompt's tempo, key and instruments the same and name the same arc. Sume's music docs advise keeping continuity when you want one consistent score, and an optional still can go in as image_url. Listen to every result; a similar brief gives a related track, not the same one.