Vox Director

Vox 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, music and captions. Runs on one Atlas Cloud API key + 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:

1. 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.
2. 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)

• echo "${ATLASCLOUD_API_KEY:+set}" — if empty, tell the user to set it (get one at https://www.atlascloud.ai/console/api-keys) and stop.
• 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>/.

1. 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 headline must be a ≤3s hook; beat count per duration (30s→6–8, 60s→10–12); split each beat into 2 shots (wide+detail) with per-shot camera_move VARIED across adjacent beats (never repeat; static on the payoff) and rich element_motion (see step 4). Each beat: narration, title_cn/title_en, scene, bg, feel, hook. This draft is the one mandatory approval gate — show the user the beat map before generating. Examples in examples/.

2. 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) 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 "theme": python3 scripts/style_bakeoff.py out/<project> american-retro,swiss-modern,punk-zine,atomic-age Set the chosen name as "collage_style" in beats.json (keyframes.py reads it).

3. Keyframes (the collage look). python3 scripts/keyframes.py out/<project> Generates one collage poster per beat/shot with google/nano-banana-2/text-to-image, headline text baked in. Compose prompts with the 5-part structure in references/prompt-guide.md. Verify each poster looks like a real layered collage before animating — re-roll cheap ($0.08) here rather than paying to animate a weak image.

4. Motion. python3 scripts/clips.py out/<project> Animates each poster with google/gemini-omni-flash/image-to-video. Two independent axes (see references/beat-layer.md §3, tested on our stack): • camera_move — ONE move per shot. Safe/default: {static, push_in, pull_out, pan, tilt, parallax}. Bold/experimental {orbit, dolly_zoom, roll, whip} are available, not banned — they can warp the flat art, so pair with constraints: loose and re-roll. Any custom phrase also passes through. • element_motion — where the energy lives; AI writes it per beat to fit that scene (not a template). Make it RICH (several elements moving) — be bold. A hero element flying across the frame (paper bird/plane/coins) is a great occasional punch on a key beat, not every shot (a flyer in every frame reads as a formula). motion_style = amplitude calm | punchy | max (the theme sets a default). constraints = strict (default: defect guards on — flat-2D, one-way, no-morph; best for clean text-heavy explainers) or loose (let the model explore 3D/bold moves; re-roll the misses). Headline text is hard-protected only on shots that have a title (detail shots without a headline are free to go wild). For real people / brand logos, Omni & Seedance refuse — set "video_model": "kwaivgi/kling-video-o3-pro/image-to-video".

5. Voice + music. python3 scripts/audio.py out/<project> One consistent narrator via xai/tts-v1 (multilingual, voice_id) + instrumental BGM via minimax/music-2.6. (Do NOT use seed-audio for plain narration unless you pin a speaker — see gotchas.)

6. Assemble. python3 scripts/assemble.py out/<project> ffmpeg: normalize + concat all shots, lay the single narration ducked under the music, burn captions timed per beat, add the watermark. Output out/<project>/final.mp4.

7. Verify. You can't read an mp4 directly — extract frames to jpg and look: ffmpeg -ss <t> -i final.mp4 -vf "scale=640:-1,format=yuvj420p" -frames:v 1 f.jpg

Cadence — how long shots should be

A common mistake is one long shot per beat. On a 9:16 / social piece especially, a static 10s shot reads as dead air. Aim for a cut every ~4–6 seconds:

• Shots run 3–6s; never let a single shot exceed ~7s — beyond that the AI motion has nowhere to go and it feels static.
• A beat's narration is ~8–10s, so give each beat 2 shots (a wide establishing shot with the headline + a detail cut-in without it). The narration plays continuously across both; the visual cuts mid-sentence. This is the single biggest rhythm win.
• So a 60s film is typically **6 beats × 2 shots × ~5s = 12 shots**, not 6 × 10s.
• Reuse the wide keyframe as shot a; generate a tighter detail scene for shot b. keyframes.py skips any shot that already has a keyframe_url, so adding b shots and re-running only generates the new ones.

Add a shots array to each beat (see schema). Give each shot its own short scene and motion; set "title": true only on the wide shot so the headline shows once per beat.

beats.json schema

{
  "project": "my-film", "topic": "...", "language": "en",
  "aspect": "9:16",                       // 16:9 | 9:16 | 1:1 | 3:4
  "style": "collage",
  "provider": "atlas_cloud",              // media backend — default; pluggable (scripts/provider.py)
  "theme": "american-retro",              // THEME_PRESET (styles.THEME_PRESETS) — the LOOK layer
  "arc": "timeline",                      // narrative arc (beat-layer.md) — the STORY skeleton
  "video_model": "google/gemini-omni-flash/image-to-video",  // Kling for real people
  "motion_style": "punchy",               // amplitude: calm | punchy | max (theme sets a default)
  "constraints": "strict",                // strict = defect guards on | loose = let AI explore + re-roll
  "voice": {"voice_id": "leo", "language": "en", "speed": 1.0},
  "music": "epic cinematic orchestral, instrumental, no vocals",
  "mix": {"music": 0.6, "voice": 1.25},   // audio balance — optional; these are the defaults (BGM ducks under the VO)
  "watermark": "Made with Atlas Cloud",
  "beats": [
    {
      "id": 1, "title_cn": "", "title_en": "BEFORE MONEY",
      "bg": "earthy clay tan", "feel": "ancient, humble", "hook": "surprising_stat",
      "narration": "For most of history, there was no money...",
      "shots": [
        // shot_size: EST_WIDE|WIDE|MEDIUM|CLOSE|DETAIL ; camera_move: static|push_in|
        // pull_out|pan|tilt|parallax (flat-safe only) — VARY per adjacent beat, static for payoff
        {"id": "a", "dur": 5, "title": true,  "shot_size": "WIDE", "camera_move": "push_in",
         "scene": "...wide establishing collage...",
         "element_motion": "traders gesture, goat bobs, a paper bird flaps across the frame, coins scatter"},
        {"id": "b", "dur": 5, "title": false, "shot_size": "CLOSE", "camera_move": "parallax",
         "scene": "...close cut-in detail...",
         "element_motion": "the exchanged goods slide together, halftone pulses"}
      ]
    }
  ]
}

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.

Model selection (always verify IDs live)

Model IDs change — fetch the live list first: GET https://api.atlascloud.ai/api/v1/models (no auth; keep only display_console: true). Defaults that work today:

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 API call goes through a provider (scripts/provider.py); Atlas Cloud is the default and only backend today. Set "provider" in beats.json to route to a different backend once one is added — the stage scripts don't change. scripts/provider.py's run_jobs() also does the submit/poll with auto-resubmit on a stalled or failed job.

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, all on Atlas.
• Manual prompt-pack: if the user isn't on Atlas, 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.