Orchestral music for a product reveal: build, hit, resolve brief

An orchestral product reveal needs three beats: tension, a hit on the reveal, and a short resolve. Google's music generation page, read on 2026-10-05, documents timestamps and lyrics-style section tags for Lyria 3.5, so you can write the cue as a timed outline. On Sume it runs through the Music Router at a fixed $0.125 per accepted generation.

A timed brief

Try this prompt: "Cinematic orchestral cue, instrumental. 0:00 to 0:10 low strings and a slow pulse build with rising tension. At 0:12 a full-orchestra hit with brass and timpani. 0:12 to 0:20 warm, hopeful resolve with strings and harp, ending on a held chord." The model is single-turn, so there is no editing pass: if the hit lands at 0:10, change the timestamp in the prompt and generate again.

Aligning the picture

Cut the reveal shot to start on the hit, then check the music length in a Timeline plan call (unbilled). Set soundtrack.fade_out_seconds up to 10 for a gentle ending; a fade longer than the output returns soundtrack_fade_exceeds_output. The render is $0.10 per output minute, so a 20-second reveal costs $0.10 on top of the music.

What to expect

Orchestral cues made by a model can blur section changes. If the hit is soft, say so in plain words: "sudden and loud". Google's pricing page lists Lyria 3.5 at $0.08 per song as of the same date, but the Sume price above is what an account is billed.