TIM SCHROEDER
Work / Infinity Video Pipeline
Automated video pipeline

Infinity Video Pipeline

One command turns a plain-English location brief into a finished vertical real-estate video: script, AI narration, animated satellite map, B-roll, captions and a Remotion render.

Private pipeline · on hold since Jun 2026Mar–Jun 2026
Vertical video frame: a satellite map of North America under the title 'Welcome to Windermere', with the caption 'If you're tired of Chicago' and the word 'tired' highlighted in goldGenerated example frame

The problem

A short local video for relocation buyers needs research, a script, a voiceover, maps, footage, captions and an edit. Done by hand, that is several tools and hours per video.

Who it's for

A real-estate team that wants hyper-local Shorts and Reels for buyers moving to the Windermere, Winter Garden and Orlando area.

Where AI is used

Claude turns the brief into facts, map coordinates, a statistic, a spoken script and upload metadata. ElevenLabs reads the script aloud and returns the timing of every word, which drives the captions.

Built with

  • Remotion 4
  • React 19
  • Claude Opus 4.7
  • ElevenLabs
  • MapLibre + Mapbox tiles
  • Pexels
  • Node.js
01 · The problem

A 45-second video is a dozen jobs

Short vertical videos are how many buyers first see a neighborhood. Each one still needs a researched script, a voice, a map that shows where the place is, some footage, captions and a final edit.

Doing that by hand for every neighborhood means the same steps in five or six different tools, every time.

  • Research and scripting start from a blank page for each neighborhood.
  • Map animations are slow to make by hand and hard to keep consistent.
  • Captions have to be timed to the voice word by word.
  • Changing the script means re-timing the whole edit.

Why custom software

Template video tools fill text into a fixed layout. They do not research a place, place it on a real satellite map, or re-time the picture to a new voiceover. Here the video is code, so every part follows from one data file.

02 · The solution

From a brief to an MP4 in one command

You type a brief such as 'a Short about Windermere for families moving from Chicago'. The pipeline writes the topic file, fetches footage, records the voice, renders the video and saves the upload metadata.

AI

Brief to script and data

Claude Opus 4.7 returns one structured topic file: the neighborhood, map coordinates, a headline statistic, a point of interest, the spoken script and YouTube metadata. An optional pause lets a person edit the script before any voice is paid for.

AI

AI voice with word timings

ElevenLabs reads the script and returns when each word is spoken. Those timings become TikTok-style captions that highlight the current word.

Animated satellite map

A map camera flies from the whole country to Florida, to Orlando and down to the neighborhood, tilts like a drone, draws a route to the point of interest and pulses the pins.

Five beats that follow the voice

Each video has five beats: establishing shot, neighborhood, statistic card, point of interest and call to action. The length comes from the voiceover, so a longer script re-times the whole video by itself.

B-roll, sound and branding

Vertical clips from Pexels play behind the statistic card. Sound effects land on beat changes, a music bed is ducked under the voice when one exists, and the call to action carries a QR code.

Ready-to-upload outputs

Each run saves a 1080×1920 MP4, a thumbnail still from the statistic card, and a metadata file with title, description and tags.

03 · My role

What I did. What the AI did.

I set the product, the audience and the services. Claude Code, an AI coding agent, wrote the code in both repos.

Tim · human judgement

I owned

  • Chose the niche: hyper-local relocation videos for buyers moving to the Windermere, Winter Garden and Orlando area.
  • Picked the services and hold the accounts: Claude for research and script, ElevenLabs for voice, Mapbox for map tiles and Pexels for footage.
  • Wrote the brief behind the first full video: Windermere, the Butler Chain of Lakes, and families moving from Chicago.
  • Set a standing rule in the project instructions that the agent warns before any step that costs API money.
  • Kept the Remotion renderer in its own repo, apart from the earlier Python pipeline, so its heavy dependencies stay isolated.
  • Had the earlier pipeline tightened to fact-only script prompts and a second research verification pass.
Claude Code · AI implementation

AI did

  • Wrote all of the code: the React composition, the map flyover, the Node pipeline scripts and the earlier Python stages. Six of the seven commits are co-authored by Claude; the seventh is Remotion's starter template.
  • Worked around a map-style problem so Mapbox satellite imagery loads in the open-source MapLibre renderer.
  • Turned ElevenLabs word timings into karaoke captions, and wrote a backfill script that captions older voiceovers with speech-to-text.
  • Rendered single test frames of the map at key moments to check the camera path before full renders.
  • Wrote the 38 committed test files in the earlier Python pipeline.

I decide what the video should say and which services it may spend money on. The agent writes and checks the code, and I judge the rendered video.

04 · How I built it with AI

From idea to production.

The work ran in two attempts. A larger Python pipeline came first in March and April 2026. A smaller, Remotion-based pipeline followed in May and June and produced the first full video.

  1. Mar 2026 · First pipeline

    Python stage pipeline and dashboard

    The Infinity-Video repo started with a staged pipeline for longer community videos from drone footage, with gates that stop a run before paid API calls, and a Next.js dashboard.

    Infinity-Video commit 4549758 (27 Mar 2026), 251 files
  2. Apr 2026 · Fact discipline

    Fact-only prompts and a second research check

    Script prompts were limited to researched facts, and community research got a second verification pass before scripting.

    Infinity-Video commits c98a504, 23cdccb (14 Apr 2026)
  3. May 2026 · New renderer

    A fresh Remotion project and the first map frames

    A new Remotion project was created for vertical Shorts. The first satellite map test frames were rendered the same day.

    commit 193518e (21 May 2026) · out/test-satellite.png
  4. Jun 2026 · Brief to MP4

    The full Shorts pipeline

    One commit added the whole chain: Claude research, ElevenLabs voice and word timings, captions, sound effects, the cinematic map camera, the statistic and call-to-action cards, B-roll and the brand design tokens.

    commit 57d6277 (10 Jun 2026)
  5. Jun 2026 · First video

    Windermere, start to finish

    The pipeline produced its first full video: a 49-second, 1080×1920 relocation Short about Windermere, with two B-roll clips, a thumbnail and metadata.

    out/windermere-butler-chain.mp4 (10 Jun 2026)
  6. Jul 2026 · On hold

    Documented, then on hold

    Both repos got a project memory wiki describing the stack and decisions. There have been no commits since June.

    memory/project-brief.md (1 Jul 2026) · git log, 2 Nov 2026
05 · Technologies

What it runs on, and why.

Every item here is in the project's code or configuration. I chose and connected them; AI coding agents wrote the code that uses them.

AI services

Claude Opus 4.7
Turns the brief into one structured topic file: facts, coordinates, statistic, script and metadata
ElevenLabs text-to-speech
Reads the script aloud and returns the timing of every word
ElevenLabs Music and Scribe
Optional music bed, and speech-to-text to caption older voiceovers

Video

Remotion 4.0.464 and React 19
The video is a React component rendered frame by frame to MP4
@remotion/captions
Word-by-word karaoke captions from the voice timings
Mediabunny
Reads the voiceover length, which sets the video length
Google Fonts (Archivo, Inter)
Brand typography from one design-token file

Maps and media

MapLibre GL with Mapbox satellite tiles
The animated map camera and pins
Turf
Map math for the route line to the point of interest
Pexels API
Vertical stock clips matched to the statistic beat
Sound effects
Four short CC0 effects keyed to beat changes

Pipeline

Node.js scripts
One driver script runs every step in order
TypeScript and ESLint
Type checks and lint for the composition
06 · System architecture

How the pieces fit.

A single Node script sends the brief to Claude, gathers voice and footage, saves one topic file, and hands that file to Remotion to render the video.

Infinity Video Pipeline architectureA single Node script sends the brief to Claude, gathers voice and footage, saves one topic file, and hands that file to Remotion to render the video.briefresearch + scriptscriptsearch phrasesavespropsaudio + timingsmap tilesrendersBriefOne commandPipeline drivergenerateTopic.mjsClaudeOpus 4.7ElevenLabsVoice + word timingsPexelsVertical B-rollTopic fileJSON + scriptRemotion renderReact · 1080×1920Mapbox tilesSatellite imageryOutputsMP4 · thumbnail · metadata
InterfaceApp / serverAI serviceData / storageExternal serviceScheduled job
Technical detail for engineers
  • Claude returns one JSON topic config. The script is saved to a separate text file so a person can edit it before the paid voiceover step.
  • The composition length is read from the voiceover file at render time. Beat lengths are fractions of that total, so the picture re-times to any script.
  • The map is MapLibre GL with an inline style that points at Mapbox's raster satellite tiles. Each frame waits for the map to finish drawing before Remotion captures it.
  • Renders use the ANGLE OpenGL backend and one worker, the setting the project uses for WebGL maps.
  • Optional steps skip cleanly: without a Pexels key the map stays full-screen, and without music permission the video renders with no music bed.
  • The map token is injected from the environment at render time and never written into a topic file.
07 · Challenges

Problems worth telling you about.

Real incidents from the project's history, each with how it was found, fixed and checked.

CHALLENGE 01

Satellite imagery that would not load

The map needed real satellite imagery, but Mapbox's ready-made map styles point to their resources with a mapbox:// address. The open-source MapLibre renderer cannot resolve that address.

VERIFIEDTest frames of the satellite map were rendered on 21 May 2026. The full Windermere video renders the map from the first frame to the last.
Why it was hard, what I decided, how AI helped
Why it was hard
Nothing about the style looks wrong. It loads from Mapbox, then quietly refers to tiles, fonts and icons the renderer has no way to fetch.
My approach
I wanted a continuous satellite flyover from the whole country down to the street, under every beat of the video, using an open-source renderer.
How AI helped
Claude Code replaced the Mapbox style with a small inline style that requests Mapbox's satellite tiles directly over HTTPS, and added sky and fog settings for the tilted camera.
The decision
Keep the open-source renderer and take only the imagery from Mapbox, instead of switching map libraries.
Evidence
src/MapFlyover.tsx (buildSatelliteStyle) · out/test-satellite.png · commit 57d6277
CHALLENGE 02

A live map inside a frame-by-frame renderer

Remotion makes a video by capturing one frame at a time. A web map draws its tiles in its own time, so a frame could be captured before the map has finished drawing.

VERIFIEDSingle frames were rendered at the end of beat 2, during beat 4 and at the zip-code step to check the camera path. The 49-second video then rendered in full.
Why it was hard, what I decided, how AI helped
Why it was hard
The camera moves on every frame, across zoom levels from the whole country to one street, and the map runs on WebGL inside a headless browser.
My approach
I judged the work by the rendered frames, not by the code, so the map had to be right in every frame of the video.
How AI helped
Claude Code set the camera position, zoom, tilt and heading from the frame number, held each frame until the map reported it was idle, turned off map fades and interaction, and set the renderer to ANGLE with one worker.
The decision
Trade render speed for correctness: one worker and a wait on every frame.
Evidence
src/MapFlyover.tsx · remotion.config.ts · out/check-beat2end.png, out/check-beat4.png, out/check-zip.png
08 · Results

What is true today.

The pipeline works end to end on one machine and has produced one complete example video. It has not been run since June 2026.

49 s
first full video, 1080×1920 at 30 fps
Source: ffprobe of out/windermere-butler-chain.mp4
108
spoken words, each with its own caption timing
Source: topics/windermere-butler-chain.script.txt and its captions file
4
outside services in one command: Claude, ElevenLabs, Mapbox, Pexels
Source: scripts/generateTopic.mjs, .env.example
5
beats in every video, timed from the voiceover
Source: src/Composition.tsx, src/Root.tsx
6 of 7
commits co-authored by Claude across both repos
Source: git log of both repos, 2 Nov 2026
2,020
lines of TypeScript and JavaScript in the renderer and scripts
Source: wc -l src/ scripts/, 2 Nov 2026
  • One command takes a brief to a vertical MP4, a thumbnail still and an upload metadata file.
  • The first video, about Windermere, rendered with two B-roll clips, word-by-word captions and the full map flyover. There is no music file in the repo, so it has no music bed.
  • The renderer has no automated tests; it was checked by rendering single frames. The earlier Python pipeline has 38 committed test files.
  • The repo holds no record that any video was published. This is a private pipeline, not a public product.
09 · Lessons

What this project taught me.

  1. A model writing from memory is not research. The new pipeline asks Claude for facts in one call with no live source and no fact-check, while the earlier pipeline had a second verification pass. For real-estate claims about taxes or prices, a person has to check every statistic before publishing.
  2. Let the voice set the length. Beats are fractions of the voiceover, so a rewritten script re-times the whole video with no manual edit.
  3. Make optional services skip, not fail. Missing footage or music still leaves a usable video.
  4. Two repos are not one pipeline until one calls the other. The earlier Python pipeline and the Remotion renderer were never wired together.
10 · Demo

No public demo

This is a private pipeline that runs on one machine, so there is no live app to visit. The homepage card plays a short clip from the first generated video.

Let's talk about
what you need built.

Open to AI roles: full-time, contract or consulting. I build AI products, internal tools and automations with AI coding agents.