Original Summary

The problem: a helmet cam gives you two hours of footage, ten minutes of which are worth watching, and finding those ten minutes is so tedious that the footage just sits on a drive forever. The realisation: the camera already knows. Every recording carries the camera's own motion track. Lean angle, turn rate, braking, acceleration, thirty times a second, sitting in the file right next to the video. ApexCut reads that track, scores it, and hands you a timeline of the interesting parts. No video is decoded during a scan, so a 22 minute ride takes about a second. Then you edit what it picked and press one button for the movie. Things I did not expect to spend time on: Proving the sign conventions from real footage instead of from the spec, because positive yaw does not mean the same thing on both camera brands. A gesture so you can mark a moment while riding: two fingers held up at the camera. The hand tracking model I started with failed on gloves, so it came out again and a plain silhouette detector went in. On real rides it catches a held gesture reliably and misfires about once every twenty minutes at night, which is documented rather than hidden. Writing the whole UI without jargon. No bins, no render queue. "How picky?" instead of thresholds. Electron, Vue 3, TypeScript and ffmpeg. Free, MIT licensed, fully offline, Windows for now. Site and docs: https://darrellvs.github.io/apexcut/ Source: https://github.com/DarrellVS/apexcut Feedback very welcome, especially from anyone with a GoPro. I only own a DJI camera, so the GoPro side is written against the spec and GoPro's sample files and I cannot test it on real footage myself.   submitted by   /u/DarrellVS [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/13 21:33:41