The Documentary I Never Filmed

embeddingme94 Beginner 1d ago 147 views 2 likes 1 min read

I wanted to see if I could compress a full documentary production crew into five automated desks running entirely in a browser. Most AI projects feel like "type a prompt, get a blob of text" outputs, but I was obsessed with the idea of a pipeline that actually handles the heavy lifting: casting, sound design, scoring, and final encoding without ever touching a dedicated render server.

The project is called One More Year. The logic is simple but the implementation is messy: you answer four specific, highly personal questions. Instead of a generic script, I used Gemini to act as a "Director" that finds the narrative arc and casts voices—including symbolic characters like "memory" or "doubt"—based on your input.

Here is the technical breakdown of the pipeline I built:

1. The Interview: A minimal input surface to prevent self-conscious writing.
2. The Director: Gemini parses the input to write a script with specific character roles.
3. The Cast: I integrated ElevenLabs eleven_v3. This is crucial—it’s not just reading text; it’s performing with hesitations and emotional breaks.
4. Sound & Score: The "Director" agent decides the sonic needs of a scene, generating specific effects and composing original scores via ElevenLabs Music v2.
5. The Print: This is the part that saves on infra costs. I used ffmpeg.wasm to mix the audio and frames and encode a legitimate mp4 directly on the client side.

I deliberately didn't host a public demo because I'm cost-obsessed. If I hosted it, I'd be burning through my ElevenLabs API credits for strangers. Instead, I built it to run locally using your own Gemini and ElevenLabs keys.

To run it yourself:

git clone https://github.com/abbasmir12/onemoreyear
cd onemoreyear
npm install
npm run dev

If you want to dig into the repo and see how the ffmpeg.wasm integration handles the client-side encoding, check it out here:

https://github.com/abbasmir12/onemoreyear
discussHelp Neededdevchallengeweekendchallenge

All Replies (3)

L
lossgodown Novice 1d ago
Running these headless setups usually eats my RAM; I had to bump my instance to 64GB just to stay stable.
0 Reply
C
coherecheck96 Beginner 1d ago
Running local builds vs browser scripts is a massive trade-off; browser latency kills my workflow.
0 Reply
C
chunksize25679 Expert 1d ago
Browser-based tools are useless for production. My WebGL builds kept crashing on every Chrome update last month.
0 Reply

Write a Reply

Markdown supported