DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to caption a video locally with WhisperX at no cost with Open Edit

Transcribe a video offline with WhisperX and get a transcript.json for captioning.

  • Top pick
  • Content
  • Intermediate
  • 45 minutes
  • From the README
  • Claude Code
  • Codex
  • Gemini CLI

Who it is forA solo creator or developer with a finished talking-head video who wants captions without paying a transcription service.

The problemCaptioning by hand is slow, and hosted transcription bills per use.

The outcomeA runs folder with a transcript.json for the video, produced locally.

What you need first

  • Node.js, so that npx can run @veedstudio/openedit-cli
  • A workspace folder for the project
  • FFmpeg, which install-ffmpeg can find or download
  • A VEED login for hosted transcription and the VEED editor handoff
  • A fal key (FAL_KEY) only for fal-billed models, background removal with --fal or --fast, and lipsync

Steps

  1. Run npx @veedstudio/openedit-cli init in an empty folder to set up the workspace. (inferred, check the README)
  2. Run npx @veedstudio/openedit-cli install-whisperx to install the local provider.
  3. Run npx @veedstudio/openedit-cli transcribe --provider whisperx video.mp4 to transcribe the video.
  4. Open the runs folder and check the transcript.json file for word timings.

Prompt for your agent

In the Open Edit repo at veedstudio/open-edit, use the @veedstudio/openedit-cli commands to transcribe <video path> locally with the whisperx provider. Expect a transcript.json under runs/ for that video. Verify that the file contains word-level timestamps before you continue.

Caveat. The README says WhisperX is installed into an isolated uv or pipx environment, so uv or pipx must be available on the machine first.

Share: 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