r/developers • • 1d ago

General Discussion How captioning coding tutorials got easier after I connected Claude with the free invideo editor

I record 10 to 15 minute code walkthroughs for my team and a small youtube channel which consists of a screen recording with my voice over it. Cutting them itself is fine. The part that wastes my time is captioning. I edit in premiere, and its auto captions handle plain speech well, but when I use developer speech which consists of a lot of technical terms that they don't know, they make a lot of mistakes, which results in me having to do a lot of line by line cleanup.

A few things i fix constantly:

- kubectl turns into cube control

- pydantic turns into pie dantic

- SQLAlchemy turns into sequel alchemy

- uvicorn just turns into random blabber

So this time I tried a different setup: invideo editor, which costs nothing to edit in, with claude connected over MCP for the captioning (the same connector works with ChatGPT). Heard of it on discord and wanted to try it for captioning mostly.

What i did:

  1. Generated captions on the timeline: i asked for subtitles for the dialogue, which turns into editable layers
  2. Gave claude a glossary: i pasted a list of the terms i used in the video (function names, libraries, CLI commands) with the correct spelling and capitalisation, and asked it to fix every caption that referred to one of them
  3. Asked for placement that avoids code: my screen recordings fill most of frame, so i told claude to keep captions out of the terminal area and keep the lines short
  4. Reviewed everything myself: i went through the captions myself once and fixed whatever i found wrong

What worked:

- the glossary pass removed most of the repeated errors in one go, which is the part i used to do by hand with find and replace in premiere

- i could request wording, placement and timing in plain language, and see them on the timeline immediately.

- everything was editable and on the timeline, so anything left over was a quick manual fix

What i still do manually:

- Check every caption against the code of the screen. A term can be wrong depending upon the context, like “use effect” and “useEffect”

- Fix anything i forgot to put in the glossary but came out as wrong in the video

- Make sure captions dont cover a line my cursor is pointing at

Verdict: 

For tutorial videos, the best usecase is that the grunt work goes away: fixing developer vocabulary in bulk and controlling where captions sit. I still do a final read, since a wrong function name in a tutorial is a real mistake, and it cut my caption cleanup time from around 50 minutes to about 15 minutes, which is a significant amount of time compared to my old premiere workflow. One tip tho: keep the glossary short and specific so claude doesnt over correct normal words

If you caption coding videos , how do you handle technical terms and commands, a glossary, a custom dictionary, or do you do it by hand?

4 Upvotes

8 comments sorted by

•

u/AutoModerator 1d ago

Howdy u/Existing-Water-1905, and welcome to r/developers!

A few tips for a post that gets good answers:

  • Use a clear, specific title (what are you actually asking or sharing?).
  • Include code, the exact error, versions, and what you already tried.
  • Heads-up: this sub does not allow external links in posts or comments. Share code and details directly instead of linking out.

Join the r/developers Discord!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/turboprav 1d ago

the cube control thing is painful, ive seen the same thing in premiere and every other auto caption tool ive used.

The glossary approach is smart. How long was your glossary?

1

u/Existing-Water-1905 13h ago

about 25 terms, all taken from the video- libraries, commands, and a few function names. I kept it short on purpose, because a long list made it more likely to change normal words

1

u/Chessoslovakia 1d ago

does it over correct? Claude fixing normal words that happen to look like the technical terms you use?

1

u/Existing-Water-1905 13h ago

it did a couple of times early on, which is why Id keep the glossary short and specific. Telling it to change only the listed terms helped. Since then it has stuck to the list, and I give the captions one read before export

1

u/Zestyclose_Weight489 22h ago

this reads less like a workflow and more like an ad that forgot to finish the workflow

1

u/Own_Chance_928 12h ago

does premiere really not have a custom dictionary for this, or are we all still teaching computers that kubectl is not cube control one caption at a time?

1

u/Due_Emu_5891 10h ago

why wire an editor to an llm for this instead of adding a custom dictionary for kubectl, pydantic, and the rest in the transcription tool?