What breaks, from the people who built it
- "Ran into issues midway through a couple of them" rendering five clips at once; renders "take 2 to 10 minutes". (Blotato)
- "Glitchy face cam because several renders were running"; the localhost preview "shows 0:00/0:00". (Clixie)
- "Text rendering through FFmpeg's drawtext filter is unreliable"; first assembly "15+ minutes per chapter" until stream-copy brought it to 30 seconds. (Wondering About AI)
- Homebrew FFmpeg without libass ("No such filter: 'subtitles'"), a faster-whisper and PyAV crash, a libvpx dyld break. (laozhang)
- Motion design and colour grading rated "Not well". (Sprites)
Why it keeps breaking
Remotion renders React to video frame by frame on your machine; FFmpeg does the cutting; a separate model does the transcription; Claude writes the glue. Four moving parts, each with its own install, versions and limits, and any one of them stops the pipeline. Running two renders at once competes for the same CPU and the output tears. None of this is editing. It is the cost of owning a render farm of one.
"…which is why I make everyone start with push-ups—"
How RealTake does it instead
RealTake runs the same job as a product. Upload a raw video of yourself talking; the Director plans the whole edit, cuts the rambles with a reason on every cut, puts word-level captions on the frame, places b-roll and 200+ motion graphics clear of your face, adds sound, and renders in the cloud in minutes. Change anything in the Studio before it renders at no cost, then post or schedule it to LinkedIn, TikTok, Instagram and YouTube. Every feature is on every plan, you see the cost before anything renders, and a failed render is never charged.
Rendering runs in the background in the cloud; you can upload another video while one renders, and if you disconnect, the job resumes where it stopped.
Upload one raw video and see the finished edit.
Free plan: 5 watermarked videos a month. No credit card.
Claude Code + Remotion vs RealTake
| RealTake | Claude Code + Remotion | |
|---|---|---|
| Where it renders | In the cloud, in the background | On your machine, 2 to 10 minutes a pass |
| Two at once | Yes; upload the next while one renders | Reported glitching and breaking midway |
| On-screen text and captions | Word-level captions, titles and 200+ motion graphics placed clear of your face | drawtext "unreliable"; captions depend on libass being installed |
| If it fails | Never charged; the job resumes if you disconnect | You debug the stack |
| Install | Nothing | FFmpeg, Remotion, a caption model, their dependencies |
Do-it-yourself figures from our own tests and the published workflows linked on the page, read October 28, 2026.