Who it is forA developer or editor who already records or generates voiceover elsewhere and wants the animated visuals and subtitles added in code.
The problemExisting voiceover needs frame-accurate timing, shot layout and subtitles, which takes manual work without a template.
The outcomeA rendered MP4 that plays your audio with shots, subtitles and chapter bars timed to it, plus a preview cut for review.
What you need first
- Claude Code or Codex installed
- Node 18 or newer
- ffmpeg (brew install ffmpeg on macOS)
- Python 3 with edge-tts 7.2.8, numpy, pillow and scipy (kokoro and espeak-ng only for English narration)
- Several GB of free disk space (about 2 to 3 GB per the README)
Steps
git clone https://github.com/Vincentwei1021/anything2explainer.gittemplate/scripts/new_project.sh ~/work/my-video myslugcd ~/work/my-video- Put your finished audio at
public/assets/ /audio.wav, then fillsrc/common/timeline.tsandsubs.tsby hand, following the format documented at the top oftts_build.py. - Run
scripts/preview.sh 30to check the first 30 seconds, thenVER=v1 scripts/render.shfor the full render.
Prompt for your agent
In the anything2explainer repo, scaffold a new Remotion project at ~/work/<slug> with template/scripts/new_project.sh, add my finished audio file <path-to-audio> with a hand-filled timeline and subtitles, and render a 30-second preview. Verify that the preview plays with the audio and that subtitles line up with the spoken words.
Caveat. The README says the timeline and subtitle files must be filled in by hand, and the exact format is documented only in a comment at the top of tts_build.py, so read that before starting.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page