Video pipeline Personal workflow

CS2 Comms Story

Turns a match demo into a subtitled story video of both teams' voice comms.

13 Pipeline steps From extracting voice tracks to archiving the finished project.
15 to 20 GB Working files per demo Rebuilt from the demo on demand, then cleared.

What it makes

A finished video tells a match through both teams’ voice comms: what each side was saying, round by round, with the scoreboard as context and subtitles throughout. The first full production covered a seven overtime game on Dust2.

How it works

  1. 01 Extract Every player's voice from the demo
  2. 02 Transcribe Speech to text on the GPU, translated where needed
  3. 03 Context Each line tied to the round and the score
  4. 04 Story A chronological story of the match
  5. 05 Record Player views captured through HLAE
  6. 06 Edit Cut, subtitled and checked, with a thumbnail
From a demo file to a finished video

It runs as a personal workflow on one machine, driven by an agent skill that holds the editorial rules. The bulky working files (voice tracks, raw recordings and renders) come to 15 to 20 GB a demo, so they are deleted once a video is archived and rebuilt from the demo if they are ever needed.

More hobby projects

  • Integrated reMarkable TutorIn use
  • Caveman CodingFirst edition
  • Job HuntIn use
  • ChromoNetResearch
  • Counter-Strafe TrainerIn development
  • CS2 Comms StoryPersonal workflow
  • Preaim and PathingIn development
  • Counter-Strafe MonitorPlanned
  • VLC Time extension, modifiedUtility
  • Home
  • Products
  • Hobby projects
↑ ↓ moveEnter open