Video Background Music v2 was tested with one unchanged input clip and four soundtrack directions. The point was not to find a universal winner. It was to check how far a short caption and a BPM value can move the musical character while the picture stays fixed.
What this Video Background Music v2 test checks
The same video appears before every result below. That matters: a changing source clip would make it hard to tell whether a different feeling came from the edit or the music. Each run used an instrumental caption, no reference-audio file, a background-music volume of 0.7, and the documented seed value of 42. The only intentional changes were the caption and BPM.
The model accepts a video URL or uploaded file, a free-text caption, optional reference audio, BPM, volume, and seed. A BPM of 0 lets the model choose tempo. A specific BPM is useful when the cut has an obvious pulse or an edit needs music near a planned tempo. The model page is here: Video Background Music v2 on Wiro.
Input clip used for all four outputs
This is the untouched source supplied to each run. The examples below are the existing hosted outputs from the same test set, so the page keeps the original media rather than substituting illustrative audio.
Four Video Background Music v2 directions
1. Ambient calm: leave tempo open
Caption: Ambient instrumental background music, soft pads, calm mood
BPM: 0
Reference audio: none
Volume: 0.7
Seed: 42
This output is the least prescriptive test. “Soft pads” and “calm mood” set the palette, while BPM 0 leaves pacing to the model. It is the sensible starting point for a quiet product shot, a reflective montage, or a clip that already contains speech and needs space around it. The tradeoff is control: it asks for atmosphere, not a beat that an editor can reliably cut against.
2. Lo-fi chillhop: relaxed pulse at 75 BPM
Caption: Lo-fi chillhop instrumental, warm vinyl texture, mellow beat
BPM: 75
Reference audio: none
Volume: 0.7
Seed: 42
This version adds a slow, stated tempo and genre markers that are much more concrete than “calm.” The warm-vinyl and mellow-beat wording is designed to pull the result toward a textured loop rather than a floating bed. Pick it for desk setups, tutorials, cafe scenes, or social clips that need movement without urgency. At 75 BPM, it is a poor fit for fast cuts, reveals, or a trailer-style escalation.
3. Upbeat indie pop: a clear edit-friendly pace
Caption: Upbeat indie pop instrumental, bright drums, catchy rhythm
BPM: 120
Reference audio: none
Volume: 0.7
Seed: 42
The 120 BPM instruction makes this the most explicit pacing test. Bright drums and a catchy rhythm aim for a forward-moving bed, not a faithful recreation of any song. That makes it the practical choice for launches, app demos, travel highlights, and cuts that land near a regular beat. It can also compete with spoken narration more than the ambient option. If dialogue is the point, lower the background-music volume before changing the prompt.
4. Cinematic trailer: tension without a vocal hook
Caption: Cinematic trailer underscore, strings and low percussion, tense
BPM: 100
Reference audio: none
Volume: 0.7
Seed: 42
Here the test changes both instrumentation and emotional intent. Strings, low percussion, and “tense” ask for pressure rather than a song-like groove. The 100 BPM setting sits between the lo-fi and indie-pop tests, so it can support a reveal without rushing through it. Choose this direction for a product teaser, a before-and-after, or an announcement with a buildup. Avoid it for light lifestyle footage unless the contrast is intentional; the prompt is doing exactly what it says.
Runtime and cost: what the documentation actually shows
The model documentation does not publish a fixed price per generated output or a guaranteed runtime. Its example task-detail response shows an elapsed time of 6 seconds, but that response is an API example and its sample output is not this music workflow. It should not be read as a promise for these four videos. The same documentation includes cost fields in a cancellation example, not a current rate card. For that reason, this test does not assign an invented per-output cost.
For a real production estimate, run the intended clip with its final caption and inspect the returned task detail. Duration, queue time, source-video length, and post-processing can all affect what a single run looks like. That is more useful than turning a documentation placeholder into a budget claim.
Which setup to pick
- Ambient, BPM 0: pick this when mood matters more than a cuttable beat.
- Lo-fi, 75 BPM: use it for calm, casual footage that still needs a steady pulse.
- Indie pop, 120 BPM: choose it for energetic edits, demos, and quick visual changes.
- Cinematic, 100 BPM: use it when the video needs tension, weight, or a reveal.
A useful prompt names the genre, the mood, and one or two musical details. BPM should solve a timing problem, not decorate the request. Leave it at 0 when the footage needs the model to choose a natural pace. Add reference audio only when a specific style direction matters more than a clean test of the caption.
Related Wiro video tests
For generated moving images before soundtrack work, see Grok Imagine Video: 5 Video Prompt Tests. For another video workflow built around preset movement, read Animated Logo: 4 Before/After Preset Videos. For a broader look at video generation with audio, see Veo 3 vs Sora 2 Pro: The New Era of AI Video Generation With Sound.
Try the model
Run Video Background Music v2 on Wiro with a short clip, one clear style description, and a BPM only when the edit needs one.
