Clippycap v0.2.0

✨ What's new since v0.1.0

Features

• Folder view in the sidebar. Browse your library by source-folder structure and filter the grid down to one folder (and its subfolders) with a click.
• Folder-scoped bulk operations. Pick a folder, select "all matching" (or just the visible cards), and tag / retag / delete the whole batch.
• Dual-mode bulk-tag editor. Two tabs:
  • Add / Remove (diff) — + adds a tag to clips that don't have it, − removes it; the rest of each clip's tags stay untouched.
  • Replace — overwrite each selected clip's tag set with exactly what you check.
• Native folder + file pickers wired into the desktop window. "+ Add source folder" and Settings → FFmpeg → use a specific path now open the real Windows Explorer dialog instead of a text input you had to type into.
• Sticky progress toasts for edits & bulk ops. Trimming / cutting / extracting and bulk tag changes now show a non-dismissing progress toast (Trimming… → Trimmed or the error), so you know it's working and what happened when it finished.

Fixes

• Trim / cut / extract no longer shift timestamped notes a couple frames earlier. libx264's default B-frame settings combined with -avoid_negative_ts make_zero to bake a leading mp4 edit-list empty-edit into every cut, which Chromium/WebView2 honored on seek. The encoder now uses -bf 0 plus a setts bitstream filter, so the first kept frame sits at PTS = 0 exactly and a note seeks back to the same content you marked.
• Timeline playhead now lines up with the yellow note marker. Clicking a note used to leave the white playhead a sliver to the right of the marker (a half-frame seek nudge we add for robustness against millisecond rounding bled into the visible position). The playhead now snaps to the displayed frame's exact PTS while paused.
• Installer's WebView2 detection no longer fires a spurious "could not install" popup. The check now looks at both the 32-bit (WOW6432Node) and 64-bit views of HKLM plus HKCU, so the in-box Edge runtime on Windows 10 is recognised — and even if the bootstrapper exits non-zero, the installer re-probes and only complains if WebView2 is genuinely still missing.
• Existing local.toml carries over cleanly across updates. If a future Clippycap version removes or renames a config key, your local.toml will no longer prevent the app from starting — the loader strips just the unknown keys (with a loud warning naming them) and continues; the rest of your overrides are preserved exactly.

Heads-up for existing v0.1.0 users

• Run Clippycap-Setup.exe — it does an in-place upgrade (same install dir, same %APPDATA%\Clippycap\). Your notes, tags, references, sources, and saved views are preserved.
• The default identity-hash strategy is now blake3-composite (size + head + tail; orders of magnitude faster to scan a large library). On first run after the update, a background IdentityUpgrader re-hashes existing assets onto the new format without touching asset.id — so every note, tag and reference (which reference the id, not the hash) stays attached to its clip. The upgrade is one-shot and resumes safely if interrupted.

Downloads

Both are standalone Windows 64-bit builds; no Python or other prerequisites:

• Clippycap-Setup.exe — installer (~104 MB). Bundles a static FFmpeg/FFprobe so trimming + thumbnails work fully offline out of the box. Per-user install (no admin / UAC), Start-menu shortcut, uninstaller. Offers to install the Edge WebView2 runtime if it's actually missing.
• Clippycap-Portable.exe — single self-contained exe (~20 MB). Nothing to install — download and run. FFmpeg isn't bundled (the app offers to download it on first run; you can decline and keep using the client-side thumbnail fallback).

User data — the SQLite library, thumbnails, tag images, logs, local.toml — lives at %APPDATA%\Clippycap\ and is shared between the two builds. Uninstalling never touches it.