Alvin-Zilverstand c0769dab0d
Build Windows Release / Rust tests (push) Successful in 6m34s
Build Windows Release / Windows installer (push) Successful in 16m42s
Merge branch 'master' of https://codealvin.xyz/Alvin-Zilverstand/clipforge-game-clipper
2026-11-16 10:33:17 +01:00
d
2026-11-16 10:30:06 +01:00
d
2026-11-16 10:30:06 +01:00
d
2026-11-16 10:30:06 +01:00
2026-09-09 10:21:29 +02:00
2026-09-11 16:22:47 +02:00
d
2026-11-16 10:30:06 +01:00
2026-09-09 10:21:29 +02:00
2026-09-09 10:21:29 +02:00
d
2026-11-16 10:30:06 +01:00
2026-09-09 10:21:29 +02:00

ClipForge

ClipForge is a Windows-first, local-first game clipping app inspired by tools like Medal and FTHR. It runs as a lightweight Tauri desktop app using the system WebView2, with Rust handling capture, replay clips, local storage, game events, hotkeys, and uploads.

Current State

  • Rolling replay capture writes short MP4 segments and manual clips extract from those segments.
  • Full-session recording concatenates the session segments into a saved MP4.
  • Capture prefers native Windows Graphics Capture with H.264 for detected game windows or the desktop, then falls back to FFmpeg Desktop Duplication (ddagrab) or gdigrab.
  • FFmpeg Media Foundation H.264 is used when available.
  • FFmpeg is bundled as a Tauri sidecar for installer builds, so users do not need a separate FFmpeg install.
  • SQLite stores the clip library; settings.json stores versioned local settings.
  • Global hotkeys are registered while the app runs: F8, Shift+F8, and Alt+F7.
  • League Live Client events and Valve GSI-style events feed the auto-clip pipeline.
  • Catbox, Litterbox, and custom multipart HTTP upload adapters are implemented; the UI can choose providers.
  • Native WASAPI system-audio and mic capture are wired into the native Windows Graphics Capture path; FFmpeg remains the fallback capture path.

Commands

pnpm install
pnpm run build
cargo test
cargo check --manifest-path src-tauri\Cargo.toml

For the desktop app:

pnpm run desktop:dev
pnpm run desktop:build

pnpm run desktop:build prepares the FFmpeg sidecar, builds the frontend, builds the Tauri app, and produces MSI/NSIS installers under src-tauri/target/release/bundle/.

Architecture

See architecture, implementation status, and product spec.

Desktop Installer

Installer filenames follow the current version and architecture. For version 0.1.1, they are expected under:

  • src-tauri/target/release/bundle/msi/ClipForge_0.1.1_x64_en-US.msi
  • src-tauri/target/release/bundle/nsis/ClipForge_0.1.1_x64-setup.exe

The NSIS setup EXE installs for the current Windows user by default and creates the normal Windows uninstaller entry/file during installation. The MSI can also be removed through Windows Apps/Programs and Features.

Gitea Releases

Gitea Actions builds Windows installer artifacts on pushes to master/main, pull requests, and manual runs. Any pushed file change, including newly added files, triggers a build. Pushing a tag like v0.1.1 also publishes the MSI and setup EXE to a Gitea release. The workflow requires a Windows Gitea runner registered with the windows:host label, with PowerShell 7, Node.js, Git, NSIS, and WiX Toolset 3 installed. Enable Actions for this repository and allow the job token code: read and releases: write permissions.

S
Description
No description provided
Readme MIT
56 MiB
0 Stars 1 Watchers 0 Forks
Languages
Rust 74.3%
TypeScript 22.5%
CSS 2.7%
PowerShell 0.4%