Braam and trailer hit sound effects you generate yourself

The braam is the most recognisable sound in modern film marketing: a distorted brass blast over an enormous sub, placed on a cut and decaying for several seconds. Good ones are hard to buy, because the library versions have already been used by everyone else. A generated braam is yours alone, and you can render a version with a longer tail when the edit changes.

Listen: 10 samples from the trailer hits & braams collection

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.

  • Classic braam

    via audiocpp-stable-audio-3-sfx

    enormous distorted brass braam, low blaring horn blast with a huge sub underneath and a long decaying tail

  • Double braam

    via audiocpp-stable-audio-3-sfx

    two braam hits in succession, distorted brass blasts a beat apart with overlapping sub tails, enormous space

  • Build into braam

    via audiocpp-stable-audio-3-sfx

    tension building for three seconds then landing on a massive distorted brass braam with a long tail

  • Sub drop

    via audiocpp-stable-audio-3-sfx

    pure cinematic sub bass drop with no midrange, deep pitch falling and sustaining, felt more than heard

  • Metallic hit

    via audiocpp-stable-audio-3-sfx

    trailer impact with a bright metallic transient over a deep distorted boom, long shimmering decay

  • Choir braam

    via audiocpp-stable-audio-3-sfx

    hybrid trailer hit blending a dark male choir with distorted brass and a sub drop, cathedral scale

  • Boom hit

    via audiocpp-stable-audio-3-sfx

    huge percussive trailer boom, gated drum-like impact with a compressed room and a fast tight decay

  • Reverse into hit

    via audiocpp-stable-audio-3-sfx

    reversed swell sucking backwards for two seconds then landing on a massive distorted trailer impact

  • Short stinger

    via audiocpp-stable-audio-3-sfx

    short sharp trailer stinger, aggressive distorted stab with almost no tail, dry and violent

  • Final hit

    via audiocpp-stable-audio-3-sfx

    final trailer hit, enormous impact with a twelve second decaying tail settling into a low drone

Prompts that work

These models respond to physical description. Name the material, the action and the space.

  • The braam itself

    enormous distorted brass braam, low blaring horn blast with a huge sub underneath and a long decaying tail

    Name all three components (brass, sub, tail). A braam missing any one of them becomes a different sound.

  • Hit without brass

    huge percussive trailer boom, gated drum-like impact with a compressed room and a fast tight decay

    "Gated" and "compressed room" describe the production treatment, and these models respond well to that vocabulary.

  • Weight only

    pure cinematic sub bass drop with no midrange, deep pitch falling and sustaining, felt more than heard

    "No midrange" keeps the sub out of the way of everything else, so you can stack it under an existing hit.

  • Landing the ending

    final trailer hit, enormous impact with a twelve second decaying tail settling into a low drone

    The last hit of a trailer is defined by its tail. A tail that long needs a render length to match, or it gets cut off.

Making trailer hits & braams sounds that fit

A braam has three layers

Brass gives the identity, the sub gives the physical weight, and the tail gives the scale. Without brass you get a generic boom; without the sub, a horn; without the tail, something that sounds small however loud it is. You can prompt all three together, or generate them separately and stack them, which is useful when you want the brass from one take and the weight from another.

Give the tail enough time

As with bells, the decay tells the audience how big the space is, and trailer hits are built to sound like they happen somewhere the size of a canyon. So give the render enough seconds. A braam with a six-second tail rendered into a three-second clip loses its scale, and adding reverb afterwards does not convincingly restore it.

Leave silence around hits

Trailer hits land through contrast: near-silence before, and space for the tail to decay into afterwards. That is an edit decision, but it changes what you should generate: a hit with a clean start and a long uninterrupted decay, without padding of atmosphere. Ask for a dry start and a long tail, and leave the silence to the timeline.

Why generate locally

The models run on your machine, which changes the cost, the privacy and what you can automate.

Offline after download

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.

Your agent can use it

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.

Licences stated up front

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.

Connect a coding agent
claude mcp add --transport http soundbox http://127.0.0.1:17494/mcp
Generate over HTTP
curl -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}'

Frequently asked questions

Why do my trailer hits sound small?
Usually the tail. Big hits sound big because of the three to twelve seconds after the transient, and the two most common mistakes are rendering too short a clip and prompting only the impact. Ask for the decay, set the render length to contain it, and add a sub layer if the hit has no low end. Those three fixes cover most of the difference between a trailer hit and a drum sample.
Can I use these sounds in a commercial video or game?
It depends on the model that made them. Soundbox shows each model's licence before you download its weights. The clips on this page were rendered with Stable Audio 3.0 Small SFX, which uses the Stability AI Community License: commercial use is free below USD $1M annual revenue, and above that Stability requires an enterprise licence. Soundbox itself is MIT, but the audio is governed by the licence of the model that made it. Read that licence before you ship; this summary is not legal advice.
Does this work offline?
Yes, once the weights are on disk. Generation, the library and the HTTP API all run locally against one SQLite file and one folder of WAVs under ~/.soundbox. There is no account and no API key, and nothing is uploaded. The only step that uses the network is the initial model download.
What hardware does it need?
The clips here were rendered on a consumer NVIDIA GPU at roughly ten seconds of wall time per clip, through audio.cpp's quantised GGUF runtime, which needs little VRAM. CPU-only generation is supported, but expect minutes per clip instead of seconds: fine for a handful of sounds, slow for a whole library.
Can an agent generate these for me?
Yes. While the app is open, Soundbox runs an MCP server at http://127.0.0.1:17494/mcp with tools for generating, listing and mixing sounds. Every generated file comes back as an absolute path, so a coding agent can render the sound a scene needs and put it straight into the project. The several hundred clips across these pages were made this way.