
Trailer audio is built from a few basic shapes: risers, hits, drones and swells. Learn to prompt each one and you can score a whole cut.
Every clip shows the exact prompt that produced it. The render script reads its prompts from the same file as this page. Copy one, change a word and generate your own.
cinematic trailer buildup, rising sub-bass synth drone, tense string section ostinato, sparse brass ensemble braam hits accenting the climb, orchestral hybrid, one final deep orchestral hit at the end
epic orchestral trailer theme, dramatic choir vocals, deep strings and brass, rising tension, cinematic
cinematic sub bass drop, deep pitch falling into a long sustained rumbling low frequency bed
metallic cinematic riser, layered scraping metal harmonics accelerating upward into a hard cut
long airy cinematic whoosh accelerating into a huge distorted impact with a dark decaying tail
orchestral string section swelling on a dissonant sustained note, bows tightening, large hall
taiko drums building from sparse hits into a fast driving pattern, huge room, epic and wide
tense ticking clock bed with a low pulsing drone underneath, steady and claustrophobic, seamless loop
slow heartbeat pulse under a dark evolving drone, cinematic tension bed, seamless loop
reversed cinematic riser, sound sucking backwards into a sharp silence, wide stereo, dramatic
epic trailer braam with a dark male choir layered over a distorted brass blast, enormous hall
title card impact, deep clean boom with a bright metallic shimmer and a slow eight second decay
These models respond to physical description. Name the material, the action and the space.
single cinematic braam hit, deep brass-like impact with sub-bass underneath, hard attack, short decay, no reverb tail
"Short decay, no reverb tail" keeps the hit from smearing into the next shot. Trailer hits are edited on the frame, and a long tail fights the cut.
cinematic tension riser, thin string-like texture climbing in pitch and volume over 2.5 seconds, no percussive hit at the end
"No percussive hit at the end" stops the model from returning a riser plus a braam when you only need the climb.
cinematic low drone riser, sustained sub-bass tone with slow pitch climb, dark and tense, 3 seconds, subtle grit on the top end
"Subtle grit on the top end" adds enough high-frequency content to keep a sub tone audible on small speakers without turning it into a lead sound.
reverse cymbal swell building into a sharp cutoff, bright metallic wash growing in volume over 1.5 seconds, ends abruptly with no tail
"Ends abruptly with no tail" makes it sound reversed. A real reverse swell has no natural decay; it stops.
trailer hit boom, single deep sub-bass punch with a short metallic clang layered on top, tight low end, dry
Naming two layers (sub-bass punch and metallic clang) combines a felt low end with an audible transient, which a boom needs on small monitors.
A cinematic sting is usually two events edited together: a build and a hit. Prompt them separately, a riser that only climbs and a hit that only lands. "A cinematic sting" comes back as the model's own fixed version of both joined together. Separate clips let you time the hit to the frame you are cutting on.
Sub-bass below roughly 60 Hz is felt more than heard, and on a laptop speaker or phone it disappears. When you want low-end weight, pair it with a word that puts something in the audible range too ("grit", "metallic clang", "brass-like") so the sound still works on small speakers.
Cinematic prompts often return a generic combo when you wanted one piece of it. If you want a riser with no hit at the end, or a swell with no tail, say so ("no percussive hit", "no reverb tail"). The model tends to bundle these events together, and a negation separates them.
Stable Audio can render a wash that sounds vaguely choral, but it has no vocal path: no voice sings real syllables. ACE-Step is built for that. Give it a short lyrics block and its choir sings it. Use it when a trailer moment needs an intelligible chant or hook; use Stable Audio for a generic "epic choir" pad.
The models run on your machine, which changes the cost, the privacy and what you can automate.
Weights are fetched once. After that, generation, the library and the API all work with the network off. Everything lives in one SQLite file and one folder of WAVs under ~/.soundbox, and nothing is uploaded.
Soundbox runs an MCP server in the same process, with tools for generating and listing sounds. Generated files come back as absolute paths, so an agent can copy them into a project.
Every model's terms are shown before you download it, and non-commercial weights need an explicit confirmation. Soundbox is MIT. The licence of the model that made a sound governs what you may do with it.
claude mcp add --transport http soundbox http://127.0.0.1:17494/mcpcurl -X POST http://127.0.0.1:17494/api/generate \
-H 'Content-Type: application/json' \
-d '{"model":"audiocpp-stable-audio-3-sfx","prompt":"8-bit coin pickup blip","duration_s":1}'