Skip to the guide
oSplitHelp Open oSplit

The headcam program

A free program that puts the oSplit panel beside your GoPro video with ffmpeg, for computers whose browser cannot read the camera's video.

Most computers make the headcam video in the browser (Headcam video). The headcam program does the same job with ffmpeg, the free video tool, for when the browser cannot read the camera's video (HEVC on a computer without a graphics card that decodes it), or when you want a smaller file at the same quality.

#Download

Unzip it anywhere. It is one file, headcam.exe on Windows: nothing to install, no Node.js. The first time it offers to install ffmpeg for you.

#Use it

  1. In oSplit, in Headcam video, line the video up and press Render panel for the headcam program (or Use the headcam program). Two files are saved in the folder with your videos: GX0123.overlay.mp4 (the panel) and GX0123.headcam.json (the plan).
  2. Drag GX0123.headcam.json onto headcam.exe. It makes the YouTube video. Or double-click headcam.exe, drag the file into its window, and choose from the menu:
ChoiceWhat you get
1The YouTube video, 3840 × 2160, and the chapters for its description
2A sync check: three 20-second clips (start, middle, finish) at 1920 × 1080, made in a minute or two
3A short of one leg or a few (5, 4-6), 1080 × 1920
4Check this computer: ffmpeg, the graphics card, and how fast it is
5A smaller YouTube video, 2560 × 1440

After each job the menu comes back; press Enter on its own to close the window.

The files are saved next to the plan: GX0123-youtube.mp4, GX0123-chapters.txt, GX0123-short-leg5.mp4. A video is written as ….partial.mp4 and renamed only when it is finished, so a stopped run never leaves a broken file with the real name.

#Speed

The graphics card is used to read the camera's video and to write the new one when it can (NVIDIA, Intel or AMD); the program times it against the processor and uses whichever is faster. On a 2014 computer with a 2015 NVIDIA card, a 4K 60 fps video took about 2.5 × the race time; with the processor alone it is several times slower. Choose 4 to see your computer's numbers.

#From a terminal

headcam compose D:\races\2026-11-03            the YouTube video (the folder with the plan)
headcam compose D:\races\2026-11-03 --preview  the three sync-check clips
headcam compose D:\races\2026-11-03 --short 5  a short of leg 5 (or 4-6, or 3,7-8)
headcam doctor --bench D:\races\GX010123.MP4   how fast this computer is with your videos

Options for compose: --size 1440p, --quality standard (smaller, quicker), --range 12:30-15:00 (only that part), --encoder nvenc|qsv|amf|x264, --decode cpu|gpu, --source <folder> (the camera's videos are elsewhere), --out <folder>, --dry-run (shows the ffmpeg commands).

#Troubleshooting

"ffmpeg was not found". Let the program install it (on Windows it runs winget install Gyan.FFmpeg, part of Windows), or install it yourself: brew install ffmpeg on a Mac, sudo apt install ffmpeg on Linux.

"Driver does not support the required nvenc API version". The NVIDIA driver is older than this ffmpeg needs. Update the driver; if the card has no newer driver, install ffmpeg 8.0.1: winget uninstall Gyan.FFmpeg, then winget install Gyan.FFmpeg --version 8.0.1.

"This plan is version 2…": download the newest headcam program from this page.

"Camera video not found". The plan names the camera's files; keep them in the same folder as the plan, or give their folder with --source.

The map is a few seconds off the picture. Go back to oSplit, open the folder again (your settings come back) and correct it under Adjust the line-up, then render the panel again. The sync check (choice 2) shows it quickly.

It ran out of disk space. A 4K video is about 30 GB an hour. Delete the .partial.mp4 file, free some space and run it again.