Replace a disputed music track across 20 ads with Timeline

If a music track in 20 finished ads becomes a problem, you re-render each ad with a new bed. On Sume, Timeline takes an optional soundtrack field with a url, gain_db, loop, fade_out_seconds and duck_db, so the change is the soundtrack URL and a new render. Timeline's render costs $0.10 per output minute, rounded up, and its plan step is unbilled; twenty 15-second ads are about 20 renders at $0.10, or $2.00 before the cost of any new music.

This is a recovery plan, not a legal opinion. TechCrunch reported on 2026-09-09 that suits against Suno continue even as it moved to licensed training data, which is a reminder that a track's source matters when you buy ad music.

What do I need on hand to do this?

You need the original timeline documents that built each ad, or enough to recreate them: the audio spine, the ordered video slots, and the output size. Sume Timeline accepts only media.sume.com URLs for sources, imported with POST /v1/media-imports, and the import requires an Idempotency-Key. If you only kept the final MP4s, you would first need to import and re-edit them; keep the timeline JSON next time.

What if the track was baked into the video?

Then a soundtrack field cannot remove it. Timeline's output audio is the spine plus the optional bed, as the docs describe, so a clip whose own audio carries music needs to be regenerated or its audio replaced before assembly. Check one render by ear before you do all 20.

How do I match length and loudness?

Music 1.0 has no duration parameter, so length comes from the track and you set loop or fade_out_seconds in the timeline. If the ad has a voiceover spine, set duck_db so the bed drops under speech. Start gentle and listen; there is no single right value.

What should I keep for next time?

Keep each ad's timeline document, the soundtrack source file and where it came from, and the job id of each render. A short ledger lets you swap a track in an afternoon instead of rebuilding ads.