| name | vox-video-director |
| description | Turn ONE topic into a finished Vox-style paper-collage explainer / ad video, end to end with Aliyun Bailian CLI + local ffmpeg — script, collage keyframes, motion, voice-over, music, captions, all automated. Use this whenever the user wants a "Vox style" video, a paper/torn-paper collage animation, a "motion collage", a narrated explainer or short ad built from AI-generated collage posters, a scrapbook-style tribute, or wants to turn a topic / product / person into a punchy narrated collage video — even if they don't say the word "Vox". Also use when reproducing Stav Zilber / rom1trs / Higgsfield-style collage ad workflows. Three input modalities: a topic (B-roll), a talking-head video (A-roll mode), or a single photo of a person/product anchored into the collage (C-roll mode). Triggers: "vox video", "collage video", "motion collage", "paper collage explainer", "make a collage ad", "turn this topic into a collage video", "turn my photo/this product shot into a collage video".
|
Vox Video Director
Turn a one-line topic into a finished Vox-style paper-collage video: a bold, punchy,
narrated explainer/ad where each beat is a torn-paper collage poster that comes alive, with
voice-over, optional music and captions. Runs through authenticated Bailian CLI (bl) + local ffmpeg.
The look is the modern editorial paper-collage popularized by Vox explainers and creators
like Stav Zilber / rom1trs: hand-cut paper cut-outs, torn edges, tape, halftone dots,
newspaper clippings, bold flat color per beat, big cut-out headlines.
The core idea (read this first)
The Vox collage look and the collage motion are two different steps:
- The look is born in the IMAGE step. Each beat is a finished collage poster made by a
text-to-image model. All the collage DNA (torn paper, cut-outs, halftone, bold color,
headline text) lives in that image. If the image isn't a rich collage, nothing downstream
will save it.
- The motion is added after. By default an AI video model animates the whole poster (the
"living poster" path — simple, automated). For dramatic piece-by-piece assembly you cut
the poster into parts and drive them with the local keyframe engine (advanced path).
Everything hinges on the prompts. Before writing any image or video prompt, read
references/prompt-guide.md — it has the exact prompt structures that make the difference
between "a real Vox collage" and "a moving PowerPoint".
Prerequisites (check, don't skip)
bl --version — requires Bailian CLI 1.14.3 or newer.
bl auth status — if unauthenticated, run bl auth login --api-key <key> and stop until login succeeds.
command -v ffmpeg ffprobe — required for assembly (brew install ffmpeg on macOS).
python3 -c "import PIL" — Pillow, for captions/watermark overlays.
Standard workflow (topic → film)
This is the default, most-automated path. Every stage is one script, all driven by a single
beats.json per project under out/<project>/.
-
Topic → beat map. First read references/beat-layer.md (the story layer) and pick a
narrative arc that fits the topic (timeline for history, pas/bab for ads,
how_it_works for explainers, man_in_hole for transformations, …). Then write
out/<project>/beats.json following that arc. Beat 1 must hook within 3s. Default to
one beat = one generated video segment = one shot. Size every segment from its narration,
not a fixed template: target 5–10s, use python3 scripts/timing.py out/<project> --estimated, and split any narration that estimates above 10s. A 60s film is usually 7–10
content-sized beats, not six fixed 10s blocks or twelve fixed 5s shots. Vary camera_move
across adjacent beats (never repeat; use static on the payoff) and write rich
element_motion. Each beat needs narration, title_cn/title_en, scene, bg, feel,
hook, and one shots item whose dur may be omitted. This draft with estimated durations
is the first mandatory approval gate. Use examples/content-timing.beats.json as the
default schema example.
-
Pick the visual style (hybrid — do this BEFORE keyframes). Do not reuse one house style
for every topic. Read references/prompt-guide.md (§5 theme presets); pick 3–4 theme presets
(styles.THEME_PRESETS: american-retro, swiss-modern, punk-zine,
soviet-constructivist, wpa-propaganda, 70s-groovy, chinese-ink, atomic-age,
newsprint-editorial) that fit
the topic's era/culture/tone — or compose a custom theme by mixing the prompt-guide dimensions
(medium/era/palette/type/finish) when none fit. Match the topic, not the language (an
English film on Chinese history should look Chinese). A theme bundles the whole LOOK layer
(idiom+palette+type+finish+mood+motion). Run a bake-off and let the user pick by eye — AI
proposes, the library is the quality floor, the human decides. Set the pick as :
Set the chosen name as in beats.json (keyframes.py reads it).
Cadence — content decides duration
- Default to one narration beat and one generated clip per segment. Keep each segment in the
model-safe 5–10s range.
- Estimate before generation from text length; after TTS, treat measured
narration_dur as
authoritative and round up to the next 0.5s with a ~0.45s edit tail.
- Video APIs receive the next whole second (for example 6.5s → request 7s); assembly trims the
returned clip to the exact edit duration, so narration is never cut.
- Short text still gets 5s so the idea can land. Long text gets up to 10s. If narration plus
tail exceeds 10s, split it at a sentence or clause boundary; never speed-read or silently
stretch a clip past the model limit.
- A 60s film usually lands at 7–10 segments of mixed lengths. Avoid identical durations across
the whole film unless the source genuinely has equal-length beats.
- Use multiple shots inside one beat only as an explicit editorial choice. Legacy multi-shot
projects remain supported, but new content-driven projects should split the narration into
separate beats so each generated clip still has its own 5–10s content unit.
A-roll mode (talking-head → collage)
The standard workflow above is B-roll: a topic becomes AI-generated collage posters
that get animated. A-roll is the reverse case — the user already has a real recorded
talking-head video (a presenter speaking to camera) and wants it itself turned into the
collage look, keeping their actual performance (face, lip movement, gestures) intact. There
is no poster to generate; the "keyframe" is the presenter's own footage. Use A-roll when the
user gives you a video file of themselves/a presenter talking, not a topic to write from
scratch.
-
Transcribe + auto-segment. python3 scripts/asr_beats.py <project_dir> <source.mp4>
Runs bl speech recognize (fun-asr) on the source audio and cuts it into beats at sentence-ending
punctuation or natural pause gaps (never exceeding ~9.5s, under Omni/Kling video-edit's
10s per-call cap). Writes beats.json with each beat's start/end/text — this is
the same mandatory approval gate as the B-roll beat map: review it, set "theme" (run
style_bakeoff.py the same way — the presenter's segment works fine as the bake-off
source), and optionally fill in a content_beats string per beat (a sticker/stamp idea
to layer in) before generating anything.
-
Generate. python3 scripts/aroll_clips.py <project_dir> [only_ids]
Cuts each beat's time range out of the source, uploads it, and re-styles it with a
photographic paper-cutout sticker treatment on the presenter — her real likeness,
lip movement, eye-line and gestures follow the source frame-for-frame; only the
silhouette edge and the world around her are paper-collage. Default model is
happyhorse-1.0-video-edit through bl video edit (set via
video_model/video_model_fallback in beats.json). Never ask the model to redraw or halftone-texture the face itself —
that gets rejected regardless of how the prompt is worded (tried both a strong and a
softened phrasing; both failed). Uses the same aspect-routing confirm gate as clips.py.
-
Assemble. python3 scripts/aroll_assemble.py <project_dir>
Muxes each generated clip with the original beat segment's own audio (never whatever
audio the video model produced) so lip-sync is guaranteed regardless of which model
handled that beat, normalizes every beat to one canvas, and concats into final.mp4.
C-roll mode (one photo → collage)
The third input modality — "cutout roll". A-roll re-styles a talking-head VIDEO; B-roll
generates everything from a topic; C-roll takes a single still PHOTO (a selfie, an
avatar card, a product shot) and anchors it inside the collage world: the subject is cut
out as a PHOTOGRAPHIC sticker — never redrawn — and per-beat posters are generated around
it with an image-EDIT model, then animated through the normal clip stage. Use C-roll when
the user gives you one photo and a topic: a personal explainer fronted by their own face,
or a collage ad built around a real product shot (validated on both, 2026-07-17).
-
Beat map. Same as B-roll (references/beat-layer.md, same approval gate), plus the
C-roll fields in beats.json: "mode": "croll", "anchor_photo", "croll_subject"
(portrait | product), and subject_wardrobe (portrait — lock the outfit or the
paper-doll body drifts) or subject_desc (product). Set "title": false on shots —
C-roll posters carry no headline; text belongs to captions. If there is no separate
script, transcribe/derive narration first and let the audio's ASR timestamps define the
beats (audio-first, like A-roll — not text-first like B-roll).
-
Anchored keyframes. python3 scripts/croll_keyframes.py <project_dir>
Uploads the photo once and generates one anchored poster per shot via
qwen-image-3.0 through bl image edit. Portraits get a
photographic face + illustrated paper-doll body; products get a pixel-faithful sticker
with label typography intact. Prompt rules that are baked in (all three cost a re-run to
learn): poses/expressions go to the BODY only — asking for a wink redraws the face;
halftone must be scoped to the background or it bleeds onto skin; portrait clothing must
be locked explicitly. The script also writes anchor_freeze into beats.json.
-
Voice timing + animate + assemble. Standard audio.py → clips.py → assemble.py.
clips.py injects the anchor_freeze guard into every motion prompt — without it the
video stage can re-letter a product label (observed: "PARFUM" → "PAREUM") or re-time a
face. For narration in the subject's own voice, set voice.clone_ref (see Voice + music
above); derive stamp/snap-zoom timing from the narration's ASR word timestamps
(asr_beats.py works on any audio, not just A-roll footage).
beats.json schema
{
"project": "my-film", "topic": "...", "language": "en",
"aspect": "9:16",
"style": "collage",
"provider": "bailian_cli",
"theme": "american-retro",
"arc": "timeline",
"video_model": "happyhorse-1.1-i2v",
"image_model": "qwen-image-3.0",
"image_resolution": "1k",
"video_resolution": "720p"
theme+arc set the two big layers; element_motion per shot is the energy (make it rich — see
below). motion/collage_style/era are still read for back-compat.
Bailian model selection
Use bl model list when you need to verify or override an ID. Defaults for this edition:
| Job | Model | Note |
|---|
| Keyframe / collage poster | qwen-image-3.0 | called through bl image generate |
| Anchored image edit | qwen-image-3.0 | called through bl image edit |
| Animate / image-to-video | happyhorse-1.1-i2v | called through bl video generate |
| Talking-head restyle | happyhorse-1.0-video-edit | called through bl video edit |
| Narration | cosyvoice-v3-flash | called through bl speech synthesize |
| ASR | fun-asr | called through bl speech recognize |
| Music | local file | set bgm_path; optional |
See references/models-and-gotchas.md for the full model-choice reasoning and every
API / ffmpeg gotcha (auth header, curl downloads, no-libass captions, content blocks, etc.).
Read it before debugging any failure — most failures are already documented there.
Backends are pluggable. Every generation call goes through scripts/provider.py.
bailian_cli is the default and starts parallel bl child processes without exposing an API key
to the project. atlas_cloud remains as an explicit compatibility backend. Failed CLI jobs may
retry; running CLI jobs are never duplicated on a stall because that could create duplicate charges.
Advanced: element-level motion collage
The standard path animates the whole poster (great, automated, "living poster"). For the
dramatic pieces-fly-in-and-assemble motion collage (à la cr7v2), or to animate real
people with full control and zero content filters, cut each poster into independent
elements and drive them with the local keyframe engine (no video model needed).
Read references/local-engine.md. In short: extract_elements.py (crop + background-removal
- residue/erase cleanup) →
motion.py (Layer + keyframes, fly_in/slap/drop/pop_settle
easings, procedural confetti/starburst, camera zoom+shake+whip, frame render). Pieces fly
back to their original positions on a blurred-placeholder backdrop, so the assembled
frame reconstructs the original poster.
Editions
- Auto edition (this skill): topic in, film out, through Bailian CLI.
- Manual prompt-pack: if the user cannot run Bailian CLI, just produce the beat map + the per-beat
image prompts + the per-clip motion prompts + the narration script for them to paste into
any generator. The creative engine (the prompts) is identical.